BG2 Jaheira key: launcher metadata failure and bounded caller repair
The native key pickup and Jaheira release remain unverified. The sole fresh
box stopped at the launcher handoff: launch.py required lifecycle.json, but
the staged manifest omitted that allocation-generated file. The recovered
FileNotFoundError precedes kernel supervision, Chrome, BG2, screenshots and
game input. This was this worker's staging error, not an emulator defect.
Historical Minsc recruitment/3000 XP and movement are not new progress.
Evidence is in scratch/runs/20261110-bg2-jaheira-key-rescue-0442/. The required
large-file, jailer-table and native-cage-key notes, CLAUDE.md, and the earlier
container-transfer/cage-rescue notes were read. All 645 originals matched size
and SHA-256: 850,839,386 bytes; BGMain.exe remains
944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b.
No game media or source archive was copied into evidence. Recovery uses the
recorded Git SHA, relevant binary diff and owned/new dependency patches. The
original as-staged manifest and patches remain unchanged; the later repair has
a separate patch.
Title-only repair
tools/bg2-current-driver.cjs composes the retained BG2 caller and controls by
exact seams, and verifies the six historical input hashes. It validates the
uppercase name before publication, makes every refusal terminal, and latches
failure before cancelling the owning supervisor. All subsequent protocol sends,
including release, screenshot and Browser.close, reject locally. Ordinary
successful holds still use independent releases. After an expected transition,
both the screenshot digest and actual game-canvas pixel difference are checked.
The retained 120-second capture-age limit is unchanged. Shared runtime, CRT,
startup, renderer and CPU sources were read only.
The allocation handoff repair is seal-lease RUN. After allocation and before
the first staging operation, it checks the original watchdog digest, matching
UUID/box/delegation, and the browser deadline exactly two minutes before the
immutable watchdog deadline. It adds the exact lifecycle.json size/hash to the
existing source pin set. It refuses expired leases, altered metadata, duplicate
sealing and sealing after staging starts; it neither allocates nor changes any
deadline. The next separately authorized attempt must run:
node tools/bg2-current-driver.cjs seal-lease scratch/runs/NEW_RUN
Then use the existing bounded chunk provisioner and its complete-closure verification/publication. Do not run that command against this terminated run, resume its box, or reuse its expired lifecycle metadata.
The focused offline suite executes the exact emitted browser execute/send bodies, the actual serialized owner chain against the current module installed through the production Worker assignment, ordinary key/type/mouse helpers, independent releases under blocked sampling and delayed down acknowledgement, exact/wrong ACK controls and sticky refusal. Its launcher control first reproduces the exact missing-JSON error with zero dispatches, then publishes the repaired tiny pin closure and executes the same Python launcher with a custody spy. That control verifies its original deadlines without starting a browser or native guest. Metadata corruption and late/duplicate seals are negatives. It is offline evidence, not native gameplay or a qualified browser run.
Attempt and shutdown
One UUID 43e7c51a-e1df-4cd5-82b3-bab3670c0f78 leased box bx_jfsgs6ts at
04:45:45 UTC. An observable independent watchdog was armed before allocation,
with immutable deadline 05:10:45.172243 UTC; the initial API expiry was
05:10:44.594 UTC. /home had over 3 GB free. No local Chrome was used.
The released 1 MiB bounded chunk staging completed and verified all 1,339
publication entries (1,338 source/runtime/input pins plus manifest). This
includes the complete original media fixture; none was skipped. It did not
include the missing allocation metadata. No failed corridor upload was reused.
The sole launch request failed at 04:46:47 UTC. Its monitor immediately sent owning OS cancellation; the outer caller also issued its cancellation on observing the failed request. Neither operation used browser/game protocol. There were zero game inputs, captures, quit commands, native launches, retries, deadline extensions or second boxes. No screenshot was available to review.
All 16 unique terminal artifacts, 1,346,741 bytes, were retrieved and
independently size/SHA-256 checked before normal stop was requested. Both gzip
streams passed decompression/CRC validation; no PNG or executing module existed.
The outer parent's actual wait returned 1, with separately observed stdout and
stderr EOFs. Kernel custody was never entered, so no kernel-reap receipt is
claimed. The independent watchdog's parent actually waited for exit 0 and both
EOFs. Final stop stop_69b0d6aa26cf0b8e completed at 04:47:32.849 UTC,
forced false, error null. The final box state is archived, expiry null.
The locked build and all 29 focused offline controls pass. The staged primary module
was 4f2c69a1528e01a9ab5127201d5e8a222da2a35236377a1351f444f55fa5a7d9;
the final offline controls used current compiled module
1b7319ff24f64d6c886803f23cb9ea88447967da4ba88fef0b177961007dc608.
Other workers' intervening shared-source changes are retained in the separate
postrepair relevant diff; this worker did not edit those files. The exact final
offline module is retained as an individual test artifact.
No live game module, renderer or browser version was observed. There is no
claim of key acquisition, rescue, world consequence, combat, FPS, audio, GL or
full playability. Next is a separately authorized fresh attempt with the sealed
allocation handoff, then individually reviewed native weapons-room, inventory
and cage-release interactions. This worker stops after publishing the repair.