lane W2: VM housekeeping notes for the multiplayer recipe (SOTSUI2 left registered, SOTSB staged not registered, -ExecutionPolicy Bypass gotcha)

findings/subsystems/multiplayer-tier0-verified.md

@@ -240,7 +240,18 @@ At 1024x768, with the game at the main menu:
 - Clicking a *specific* instance needs a helper that resolves the window by **PID**
   (`Get-Process -Id`), not `Select -First 1` — the existing `C:\SOTS\ui\click_helper.ps1` picks
   whichever instance it finds first. Lane W2 left `C:\SOTS\w2\ui.ps1` (takes a PID, or `-1` for "do
-  not foreground anything", which is how the firewall dialog gets clicked).
+  not foreground anything", which is how the firewall dialog gets clicked); it reads the PID from
+  `C:\SOTS\w2\pid.txt` and the commands from `C:\SOTS\w2\cmd.txt`, and is run by the **SOTSUI2**
+  scheduled task, which is registered and left in place.
+- **The second-instance launcher is staged but NOT registered.** `C:\SOTS\w2\sotsb.xml` and
+  `C:\SOTS\w2\argsB.txt` are on disk; re-register with
+  `schtasks /Create /TN SOTSB /XML C:\SOTS\w2\sotsb.xml /F` and put the arguments in `argsB.txt`.
+  It was deliberately left unregistered so a stray run cannot start a second game under a later
+  lane.
+- **PowerShell over SSH needs `-ExecutionPolicy Bypass`** even for `-EncodedCommand`, or any `& …
+  .ps1` inside it dies with `running scripts is disabled on this system` — and, because the failure
+  is inside the encoded block, it looks like the script ran and did nothing. This cost one wasted
+  launch here.
 
 ## 11. Corrections filed