Docs: bring READMEs in line with current state (net48, JSON wire)

- Root README: launcher is .NET Framework 4.8 (was .NET 6/x86); RPC is framed
  JSON (was BinaryFormatter); added Contract/ + SecureConfig/; dropped the
  now-resolved "known duplication" warning; corrected the lib/*.dll note
  (TeslaConsoleLaunchLib/TeslaSecureConfiguration are source-built, kept only as
  test baselines); added a short history section.
- Console README: Contract is net48-only; Launcher targets net48.
- Launcher README: net48 framework-dependent (was net8/x64 self-contained);
  needs .NET Framework 4.8 (built into Windows), no bundled runtime.
- DiffTests README: original 4.11.3.37076 vs recovered 4.11.4.x (no longer share
  identity); noted version-insensitive comparison + the new protocol/crypto guards.
- Removed Launcher/assets/MEMORY.md (stale leftover dev-notes, superseded by the
  README and now-moot post-BinaryFormatter).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Console/tests/TeslaConsole.DiffTests/README.md

@@ -6,12 +6,14 @@ source in this repo) behaves identically to the **original** reference binary in
 
 ## How it works
 
-Both files carry the *exact same* assembly identity
-(`TeslaConsole, Version=4.11.3.37076`), so the .NET loader will not hold both in
-one AppDomain. The suite therefore loads each assembly into its **own child
-AppDomain** (`DifferentialFixture`) and drives it through a `MarshalByRefObject`
-proxy (`Invoker`). This is why the project targets **net48** — AppDomains are a
-.NET Framework feature.
+The suite loads each assembly into its **own child AppDomain**
+(`DifferentialFixture`) and drives it through a `MarshalByRefObject` proxy
+(`Invoker`). This is why the project targets **net48** — AppDomains are a .NET
+Framework feature. The **original** is the `4.11.3.37076` baseline; the **recovered**
+build is the modernized `4.11.4.x` line (same `TeslaConsole` assembly name, an
+intentionally newer version). Because the two versions differ, the public-member
+comparison strips `Version=` stamps before diffing — it compares type/member *names*,
+not assembly versions.
 
 Each child domain is given a probe directory (the recovered build's output, which
 ships every dependency DLL) so the original — which is distributed without its
@@ -39,6 +41,16 @@ proprietary dependencies — still resolves its references for metadata inspecti
    A negative-control test (`Harness_Distinguishes_Different_Outputs`) proves the
    harness can actually see a difference, so a green run is never vacuous.
 
+The project also carries two **byte-compatibility guards** — not original-vs-recovered
+comparisons, but checks that the modernized protocol/crypto stays compatible with the
+original binaries:
+
+- `PodRpcProtocolTests` — round-trips the framed-JSON RPC ([`Contract/PodRpcProtocol.cs`](../../../Contract/PodRpcProtocol.cs))
+  in-process: every request/response shape encodes and decodes back to the same values.
+- `SecureConfigCompatTests` — asserts the source-built `OFBCryptoStream` produces
+  byte-identical ciphertext to the original `TeslaSecureConfiguration.dll`, so the pod
+  provisioning handshake stays wire-compatible.
+
 ## Running
 
 ```