Baldur’s Gate II Jaheira/corridor attempt, 2026-11-08

No new native objective consequence or corridor locomotion was demonstrated. Staging failed before Chromium or BG2 launched: the retained individual-file upload transport raised URLError: <urlopen error The write operation timed out> while writing a large original file. Its delivery outcome was unknown, so provisioning was not replayed and no launcher was submitted. This is a staging transport blocker, not a demonstrated emulator defect. Accepted Minsc recruitment/3000 XP remains historical evidence, not a new deliverable.

Evidence: scratch/runs/20261108-bg2-jaheira-corridor/ (ignored). The cage-rescue, container-transfer and equipment notes were read. No exported native save was found in the rescue handoff. All 645 retained originals passed local size/SHA-256 verification, totaling 850,839,386 bytes; BGMain.exe remains 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b. The original manifest was reused. Recovery records source commit c7da83223fd559cb85bf92538102c792f94c1ff9, relevant tracked/new-file patches, owned helper patches, media references and 1,283 current runtime/input pins. Sixteen runtime/source differences from the prior rescue were recorded explicitly. No source/media archive was made.

Local preparation found that the predecessor's ordinary-key validator accepted Space, but its separately held-key helper did not. An initial generated Chromium control exposed that omission before allocation. The owned run copy added VK 32 with DOM key and code Space, retaining independently armed release. The corrected generated control passed the actual numbered request/publish/consume/admission/native-delivery/exact-ACK path, trusted Space down/up, empty physical keys and a clear renderer key bitmap. Existing combo/click/drag positives, independent release, nine replacement refusals, stale/slow capture and partial/UNKNOWN/late/wrong ACK controls also passed. The labeled generated canvas was reviewed and is not game evidence. The production driver separately reached its final app-selection boundary locally with zero original launches. Its exact proposed 22-minute absolute browser cap passed the strict less-than-30-minute invariant before allocation.

One UUID-idempotent box bx_vq596w6n was created at 00:08:30 UTC, with original expiry 00:48:30.319 UTC. A detached observable watchdog was armed before creation, with a 25-minute deadline and retrieval/hash-verification followed by delegated normal stop. Local free disk stayed above 8 GB, exceeding the requested 5 GB floor. Provisioning acknowledged 596 files before the upload failure; terminal inspection found 589 staged source/media files matching their pins plus seven already-retained run helpers. The complete pin manifest had not reached the box. No original directory, launch-parent record, Chrome or Node runtime existed there.

The first terminal observer incorrectly assumed the manifest had staged; a second observer matched node inside the unrelated avahi daemon's descriptive name. Both exact observer failures are retained. The corrected read-only observer matched executable basenames and recovered the partial staging hashes and absence-of-runtime evidence; no transfer or game command was replayed. All 11 terminal run artifacts (171,935 bytes), including unique observer JSON, were retrieved individually and SHA-256 verified before normal stop was requested at 00:12:39.215 UTC. Stop stop_25e640c55a6466ce completed without force at 00:12:40.432 UTC; final state is archived, expiry cleared. The watchdog observed normal stop and exited. Local fixture PIDs and ports were absent/closed; the failed initial control's leftover temporary profile was removed after verifying its PIDs were gone.

Validation is limited to local native input controls, driver/deadline preflight, original hashes, staged-file hashes, retrieval and shutdown. No game input, private handler, guest/save/configuration edit, emulator source change, extra box, resume/delete or public deployment occurred. The intended native game route remains Canvas2D; this attempt provides no GL, combat, FPS, audio or full-playability coverage. This documentation-only change requires no code build. Next: diagnose bounded large-file staging delivery locally, then obtain a separately authorized fresh attempt using the qualified Space helper, actual pause-state/portrait review and a fresh destination before ordinary movement and Jaheira's key/cage interaction.