Move RIO hardware + firmware archive to the TeslaRel410 repo

The physical RIO board docs (photos, schematics, GAL decode) and the
board firmware (dumps, disassembly, make_patch.py, RIO 4.3 + FastRIO
images, analysis, testlogs) describe hardware shared across all Tesla
cockpits with a lifecycle independent of this Windows app — a
native-game-only cabinet runs the firmware and never touches RIOjoy.
They now live in TeslaRel410/restoration/{rio-hardware,rio-firmware}
with full history preserved (git subtree).

Kept here: docs/PROTOCOL.md (this app's interface contract) and the
RioSerialMonitor bench harness (--mash/--e0test, C# on RioJoy.Core).
README + code comments now point at the TeslaRel410 archive.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

tools/RioSerialMonitor/Program.cs

@@ -12,10 +12,10 @@ using RioJoy.Core.Serial;
 // Firmware wedge-patch validation (RIO_TAP mash test, see MashTest.cs):
 //     dotnet run --project tools/RioSerialMonitor -- --mash [port] [seconds]
 //         [--label baseline|patched] [--no-lamps] [--wedge seconds] [--baud rate]
-// --baud: 31250 for the retuned firmware variant (rio-firmware --baud31250).
+// --baud: 31250 for the retuned FastRIO firmware (TeslaRel410 restoration/rio-firmware, make_patch.py --baud31250).
 // Exit: 0 = ran, 2 = could not open the port (mash: 1 = wedge detected).
 
-// E0-threshold firmware verification (rio-firmware --e0thresh images, see E0Test.cs):
+// E0-threshold firmware verification (TeslaRel410 restoration/rio-firmware --e0thresh images, see E0Test.cs):
 //     dotnet run --project tools/RioSerialMonitor -- --e0test [port] [--baud rate] [--events n]
 if (args.Contains("--e0test"))
     return await RioSerialMonitor.E0Test.RunAsync(args);