SSH pairing overlap proof

This is a manual command-path proof, not a web scenario or desktop GUI test.
The remote pairing shell payloads were generated directly by buildRemotePairingScript
from base b1050d344962e1adfbe3309f880ae13c0fa98aad and
head 27016a8b7b2f8d3bbb40891e3563ba3c19374647.
old.sh comes from tag v0.1.8. State key is the same synthetic value on each side.
Only releaseBaseUrl points to the local, byte-for-byte release mirror.

The real SSH server listens on loopback. Each run has a fresh HOME. The driver
uses bwrap to resolve /bin/sh to Bash 5.2 in a private mount namespace; the host
/bin/sh remains dash. This matches the reported shell condition. The preliminary
dash run passed on both revisions and is not counted as the Bash proof.

Download the actual upstream archives into this directory:
https://github.com/pingdotgg/t3code/releases/download/v0.1.8/t3-0.1.8-linux-x64.tar.gz
  save as old.tar.gz
https://github.com/pingdotgg/t3code/releases/download/v0.1.10-nightly.20261112.4564/t3-0.1.10-nightly.20261112.4564-linux-x64.tar.gz
  save as new.tar.gz

Place old.sh, base.sh, head.sh, driver.py and record.cjs beside those archives.
Run: node record.cjs <checkout-with-installed-dependencies>
Prerequisites: Linux, Bash, curl, tar, OpenSSH server/client, sudo without password,
bwrap, Python 3, Node, and the checkout's Playwright Chromium.
The driver executes unchanged generated remote payloads through real SSH.
A threaded HTTP mirror holds A's archive response until B finishes pairing.
The archives are real releases, not fake executables. SHA256SUMS is constructed
from the downloaded archive bytes; real runner verification and extraction run.
No credentials are retained in evidence; only credential presence is recorded.
The videos record a live transcript viewer fed directly by the running driver,
not the desktop UI. Both captures use 1280x900, identical theme and driver.
