XP11: whole suite on net40 — Console + vPOD run on XP SP3 through Win11

The Launcher's XP11 port (8730b9b) now extends to everything: one net40
flavor across Console, vPOD, Contract, and SecureConfig (Newtonsoft.Json
everywhere; the net48/System.Text.Json legs and their #if splits are gone
since nothing consumed them).

Console (net40, single TFM like the Launcher):
- The ~31 BinaryFormatter bitmap blobs in the .resx files became raw
  embedded files under assets/icons/ (extracted byte-faithfully via a
  serialization surrogate — the animated square_throbber.gif survives),
  loaded by Properties.Resources.EmbeddedBitmap/EmbeddedIcon. Reason:
  System.Resources.Extensions' DeserializingResourceReader is net461+
  and cannot load on net40. Strings stay in the .resx.
- IReadOnlyList -> IList in AppRegistry (net45+ interface).

vPOD (net40, single TFM):
- Zip extraction now shares the Launcher's MiniZip.cs (linked source), so
  the diff-test install round-trip exercises it against ZipArchive zips.
- RPC args as JTokens; LaunchApps.json persistence via Newtonsoft;
  Thread.VolatileRead instead of Volatile.Read.

Contract/SecureConfig: net40-only; Client/** (PodManagerConnection) now
ships in the one build. The Launcher package gains
TeslaSecureConfiguration.dll as a dependency of the client half.

Tests: the net48 xunit host loads the net40 assemblies (both CLR4), so
the suite exercises exactly what ships — 106/106 green. Also verified
live: net40 console provisioned, managed, and ran a full RP mission
against net40 vPOD (beacon/passphrase/RSA, 53290 RPC, egg load,
Run/Stop Mission).

Version: 4.11.4.3 across Launcher, Console, and vPOD (vPOD joins the
suite version line; was 1.0.0). Ship the dotNetFx40 redistributable in
Launcher/assets for XP-era pods.

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

Console/README.md

@@ -39,13 +39,14 @@ The console references these assemblies. Most are vendored as binaries under
 Two of these are no longer vendored binaries — they are built from source and
 shared across the suite:
 
-- `TeslaConsoleLaunchLib` ← `../Contract/Tesla.Contract.csproj`, a net48 project: the
-  single source of truth for the Console↔Launcher RPC contract (wire types, the
+- `TeslaConsoleLaunchLib` ← `../Contract/Tesla.Contract.csproj` (net40, like the
+  whole suite since XP11): the single source of truth for the
+  Console↔Launcher RPC contract (wire types, the
   `PodManagerConnection` client, and the framed-JSON `PodRpc` protocol), shared with the
-  Launcher Service. The assembly keeps the
+  Launcher. The assembly keeps the
   `TeslaConsoleLaunchLib` name so the original-exe baseline still resolves in the
   differential tests; the wire no longer embeds assembly names (see RPC note below).
-- `TeslaSecureConfiguration` ← `../SecureConfig/Tesla.SecureConfig.csproj` (net48),
+- `TeslaSecureConfiguration` ← `../SecureConfig/Tesla.SecureConfig.csproj` (net40),
   the first-boot provisioning protocol (UDP beacons, OFB crypto, RSA key exchange).
 
 The original `TeslaSecureConfiguration.dll` is retained under `lib/` as the baseline
@@ -55,14 +56,16 @@ decompiled to source the same way if full-source builds are needed.
 
 ### Console ↔ Launcher RPC (no BinaryFormatter)
 
-The pod-management channel (TCP 53290) runs **length-prefixed System.Text.Json**
+The pod-management channel (TCP 53290) runs **length-prefixed JSON**
 frames over the existing OFB-encrypted stream — see `Contract/PodRpcProtocol.cs`,
-shared verbatim by both ends. This replaced the original `BinaryFormatter` +
+shared verbatim by both ends (Newtonsoft.Json — net40 has no System.Text.Json).
+This replaced the original `BinaryFormatter` +
 serialized-`MethodBase` scheme (a remote-code-execution sink, and what had pinned the
-Launcher to an old runtime); dispatch is now by method-name string. The Launcher
-Service/Agent target **net48**, same as the Console. Note the Console still uses
-`BinaryFormatter` for *local* disk persistence (`Site` config, mission results) — that
-is local file I/O on net48, not the network surface, and is intentionally left alone.
+Launcher to an old runtime); dispatch is now by method-name string. The Launcher and
+the Console both target **net40** (XP11: XP SP3 through Windows 11). Note the Console
+still uses `BinaryFormatter` for *local* disk persistence (`Site` config, mission
+results) — that is local file I/O, not the network surface, and is intentionally
+left alone.
 
 ## Layout
 
@@ -72,8 +75,10 @@ and still build and run.
 ```
 TeslaConsole/
   *.cs, TeslaConsole.*/    decompiled source (by namespace)
-  *.resx, app.ico          embedded resources + icon
-  TeslaConsole.csproj      net48 project
+  *.resx, app.ico          string resources + icon
+  assets/icons/            UI images (raw originals, embedded as manifest resources —
+                           the resx BinaryFormatter blobs cannot build for net40)
+  TeslaConsole.csproj      net40 project (XP11: runs on XP SP3 through Windows 11)
   RedPlanet/               runtime content (RPConfig.xml, RPStrings.xml) — copied to output
   images/                  source art (pod art / maps / vehicles) — reference only
   installer_banner.bmp     installer artwork — reference only
@@ -84,14 +89,14 @@ TeslaConsole/
 ## Building
 
 Requirements: .NET SDK (6.0+) — the `Microsoft.NETFramework.ReferenceAssemblies`
-NuGet package supplies the net48 reference assemblies, so a standalone Framework
+NuGet package supplies the net40 reference assemblies, so a standalone Framework
 targeting pack is **not** required.
 
 ```
 dotnet build TeslaConsole.csproj -c Release
 ```
 
-Output: `bin/Release/net48/TeslaConsole.exe` (with `RedPlanet/` and all
+Output: `bin/Release/net40/TeslaConsole.exe` (with `RedPlanet/` and all
 dependency DLLs copied alongside it).
 
 ## Runtime content