docs: remove lab-mode references and picotool build vendoring

Lab-mode is gone from the bridge (bc12331) and the firmware
(af7c430). Public docs catch up:

- README.md: drop the "Remote Sessions (Optional)" section
- wiki/Lab-Mode.md: delete
- wiki/_Sidebar.md: drop the "Lab Mode" entry
- wiki/Home.md: drop the "Lab Mode" bullet from the page index
- build.ps1: drop the picotool.exe fetch+vendor block. picotool
  shipped with the release ZIP only because lab-mode's remote
  force_bootsel relied on it; with that path gone, builds no
  longer download or stage picotool.

The remote-Parsec-player wording in wiki/Home.md is preserved --
that's the core product description, separate from lab-mode.

Author: RealWhyKnot

README.md

@@ -58,28 +58,6 @@ Useful commands:
 .\couchlink.exe bundle
 ```
 
-## Remote Sessions (Optional)
-
-If you want someone you trust to look at the bridge remotely without sending them files back and forth, open a debug tunnel:
-
-```powershell
-.\couchlink.exe tunnel start
-```
-
-The bridge mints a session on `couchlink.whyknot.dev` and prints a one-line view URL. Share that URL only with someone you trust -- it lets them run a small allowlisted set of commands against this bridge:
-
-- `couchlink` subcommands (doctor / bundle / configure-wifi / flash / logs / test)
-- `cmake` and `ninja` for firmware rebuilds
-- `dir` / `ls` / `type` / `cat` for log inspection
-
-There is no general shell. File reads are limited to a fixed set of log / config files with passwords and tokens redacted. Every command the other person runs and every line of output is mirrored to your own bridge console, so you can watch what they are doing in real time.
-
-To revoke access, restart the bridge (or run `.\couchlink.exe tunnel disable`). The URL goes dead immediately. Sessions also auto-expire after 24 hours of bridge idle.
-
-The other person's setup is just a PowerShell one-liner; full instructions for them are at <https://couchlink.whyknot.dev/USAGE.md>.
-
-See the wiki's [Remote Sessions](https://github.com/RealWhyKnot/ParsecCouchLink/wiki/Remote-Sessions) page for the full safety model and the operator-side flow.
-
 ## Reporting bugs
 
 If something went wrong, the fastest path is:

build.ps1

@@ -84,43 +84,6 @@ if (-not (Test-Path -LiteralPath $FirmwarePicow)) {
 Copy-Item -LiteralPath $FirmwarePico2w -Destination (Join-Path $StageDir "couchlink-pico2w.uf2") -Force
 Copy-Item -LiteralPath $FirmwarePicow  -Destination (Join-Path $StageDir "couchlink-picow.uf2")  -Force
 
-# picotool ships alongside the bridge so lab-mode's `force_bootsel`
-# fallback can drop a wedged Pico into BOOTSEL drive mode without a
-# physical button press. We vendor the official pre-built binary from
-# raspberrypi/pico-sdk-tools and cache it under tools/picotool/ so
-# subsequent builds don't re-download.
-$PicotoolVersion = "2.2.0-3"
-$PicotoolAssetName = "picotool-2.2.0-a4-x64-win.zip"
-$PicotoolUrl = "https://github.com/raspberrypi/pico-sdk-tools/releases/download/v$PicotoolVersion/$PicotoolAssetName"
-$PicotoolCacheDir = Join-Path $RepoRoot "tools\picotool"
-$PicotoolExe = Join-Path $PicotoolCacheDir "picotool.exe"
-if (-not (Test-Path -LiteralPath $PicotoolExe)) {
-    Write-Host ""
-    Write-Host "Fetching picotool $PicotoolVersion from raspberrypi/pico-sdk-tools..." -ForegroundColor Cyan
-    New-Item -ItemType Directory -Force -Path $PicotoolCacheDir | Out-Null
-    $PicotoolZip = Join-Path $PicotoolCacheDir $PicotoolAssetName
-    try {
-        # TLS 1.2 + UseBasicParsing for Windows PowerShell 5.1.
-        [Net.ServicePointManager]::SecurityProtocol = `
-            [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
-        Invoke-WebRequest -Uri $PicotoolUrl -OutFile $PicotoolZip -UseBasicParsing
-    } catch {
-        throw "Failed to download picotool from $PicotoolUrl : $_"
-    }
-    Expand-Archive -LiteralPath $PicotoolZip -DestinationPath $PicotoolCacheDir -Force
-    Remove-Item -LiteralPath $PicotoolZip -Force
-    if (-not (Test-Path -LiteralPath $PicotoolExe)) {
-        # Some sdk-tools releases nest picotool.exe inside a versioned
-        # subfolder; find it and lift it up.
-        $found = Get-ChildItem -LiteralPath $PicotoolCacheDir -Recurse -File -Filter picotool.exe | Select-Object -First 1
-        if ($null -eq $found) {
-            throw "picotool.exe not found in extracted archive at $PicotoolCacheDir"
-        }
-        Copy-Item -LiteralPath $found.FullName -Destination $PicotoolExe -Force
-    }
-}
-Copy-Item -LiteralPath $PicotoolExe -Destination (Join-Path $StageDir "picotool.exe") -Force
-
 $ScriptFiles = @(
     "setup.ps1",
     "doctor.ps1",

wiki/Home.md

@@ -26,7 +26,6 @@ Console player 2
 - [[Quick Start]] - install from a release zip and run the setup script.
 - [[Setup and Flashing]] - what the script does and how to recover a Pico.
 - [[Troubleshooting]] - what to run when setup or discovery fails.
-- [[Lab Mode]] - opt-in remote-flash session for collaborative testing.
 - [[Reporting-Bugs]] - how to make a bundle and what to include in an issue.
 - [[Build]] - build the release zip from source.
 - [[Protocol]] - short runtime and setup protocol reference.

wiki/Lab-Mode.md

@@ -2,7 +2,6 @@
 - [Quick Start](Quick-Start)
 - [Setup and Flashing](Setup-and-Flashing)
 - [Troubleshooting](Troubleshooting)
-- [Lab Mode](Lab-Mode)
 - [Build](Build)
 - [Protocol](Protocol)
 - [Changelog](Changelog)