Baldur’s Gate II native cage rescue, 2026-11-07
Evidence: scratch/runs/20261107-bg2-cage-rescue/ (ignored). Minsc’s rescue completed: ordinary dialogue caused him to break the bars, accept the invitation to travel together, and join the party. Reviewed review/cages-before.png shows two portraits and both prisoners caged. review/minsc-break.png records his statement that the bars bend and Minsc and Boo are free; review/minsc-free-dialogue.png records his recognition that the taunts made him angry enough to break free. review/party-after.png shows the third Minsc portrait, his green world selection circle, and “The Party Has Gained Experience: 3000.” review/minsc-selected.png and later captures retain the new party member. Jaheira remains caged.
The predecessor note and retained driver/evidence from 7e8549b8e were read before work. No archived box was resumed. This attempt used ordinary character creation: male human Fighter, lawful good, first rolled attributes 15/15/8/17/10/12 unchanged, two proficiency points each in Axe, Long Sword and Two-Handed Sword, default appearance/sound, name a. Every action followed a fresh reviewed screen. The introductory scene and Imoen conversation completed, followed by Jaheira’s initial conversation and Minsc’s rescue dialogue. No inventory experiment, cheat, guest-memory/configuration/save/clock edit or coordinate replay was used.
Before allocation, actual Chromium exercised the staged transport’s successful key, combo, click and balanced drag, exact ACK matching, and independent release despite delayed mouse-down acknowledgement. Nine owner/module replacement cases, stale/slow captures, partial delivery, UNKNOWN, late ACK and wrong ACK failed for their intended reasons; missing imports were excluded as acceptable negative results. The labeled generated canvas was personally reviewed and is not game evidence. The actual production driver reached its final app-selection boundary locally without launching an original. The exact proposed immutable browser deadline, 1794049624270 (11:07:04.270 UTC), passed locally with 1,499,050 ms remaining, strictly below 30 minutes.
All 645 retained originals matched size and SHA-256, totaling 850,839,386 bytes; BGMain.exe SHA-256 remains 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b. Source recovery uses Git commit fa63787b0f5e80bcbeedc5e8ea07337d36369f41, relevant-source.patch, new-files.patch, owned-inputs.patch and runtime-pins.json. There are 1,283 pinned runtime/input files. The three non-run differences from the predecessor are explicitly retained in predecessor-runtime-differences.json; old runtime identity was not assumed. No source/media archive was made.
One UUID-idempotent box, bx_buprf8a3, was allocated at 10:42:27 UTC after local /home exceeded 2 GB free. Its original expiry was 11:22:27 UTC, and normal shutdown was explicitly delegated. Staging finished before the single launcher started at 10:43:18.993 UTC. Actual runtime: Chrome 151.0.7922.71, V8 15.1.206.10, fixed 1024×768 viewport, registered baldurs_gate2_demo, guest process 1000, endpoint 1/slot 0, six guest Workers. The owning guest target is 76B2C9C6279813DB11B310A8A555DD98; recovered live module SHA-256 is e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467 (2,182,493 bytes). Passive owner inspection identifies Win98Renderer/Canvas2D and no D3D render-worker endpoint. The toolbar’s WebGL selection is not the game renderer identity.
Corridor locomotion after recruitment was not established: Minsc stayed by the cage after movement clicks. An attempted pause check used a literal space instead of the supported Space key name and was rejected by validation before command publication, with no guest input, retry or ambiguous ACK. This limits the movement claim; it does not undo the reviewed recruitment and XP consequence. No emulator defect, combat, FPS, audio or parity claim is made, and no emulator source was changed.
Chrome closed normally at 11:03:28.884 UTC (exit 0, no signal), before its cap. Before box stop, all 1,107 terminal artifacts (59,449,847 bytes; 902 unique digests), including unique logs/captures and the live module, were retrieved individually and SHA-verified. All 1,283 terminal pins matched. All 102 published commands had exact successful ACKs; writer lock, unresolved commands and transport-failure markers were absent. Passive inspection found no held keys and an empty input queue; the final mouse receipt records independent release. All 14 recorded runtime PIDs were absent, both ports closed and the Chrome profile removed. Normal nonforced stop was requested at 11:04:35.605 UTC after retrieval verification; archived state and cleared expiry are retained in the final lifecycle evidence.
Validation: native Chromium controls and reason-specific negatives, exact staged production-driver/deadline preflight, original/runtime hashes, reviewed before/after party and XP consequence, terminal retrieval and cleanup. This is documentation only; no code build was required. The requested rescue is complete. Any later corridor/combat or Jaheira rescue work needs a separately assigned fresh runtime; do not resume this archived box.