Baldur’s Gate II guarded cage-key attempt, 2026-11-08
Key acquisition and Jaheira’s release remain unverified. The uppercase naming blocker was avoided successfully, and this fresh original run demonstrated native upper-corridor movement, door opening, entry into an adjoining portal room, and the native inventory/Ground interface. The weapons container was not located within the fixed browser window. No new causal emulator blocker was established; this is an incomplete navigation attempt, not completion of the requested objective. Historical Minsc recruitment and earlier cage dialogue are not counted as new progress.
Evidence is retained in scratch/runs/20261108-bg2-guarded-cage-key/ (ignored). CLAUDE.md, the large-file gameplay, cage-rescue and native-cage-key notes, and shipped README.TXT were reviewed. The shipped help documents hover tooltips, I inventory, G return to game, portrait dragging for party order, and chests/bookshelves/boxes as containers. Before allocation, the actual future request.py ran through its numbered client, consumer, owner admission and keyboard helper in Chromium. Exact uppercase A produced trusted paired down/up events, an empty held-key set and the matching successful ACK. Lowercase a failed before a request record or remote call. See type-qualified/uppercase-path.json and type-admission-regression.json. The generated labeled canvas was personally reviewed and is not game evidence. Existing qualified transfer, Space, portrait, click and drag controls were reused; no transfer project was repeated.
All 645 unchanged originals matched exact sizes and SHA-256, totaling 850,839,386 bytes. BGMain.exe remains 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b; the registered manifest lists the other 644 files. Released 1 MiB chunk staging verified reconstruction and atomic publication for all 1,284 entries. Runtime pins outside this run’s helpers match the predecessor exactly. Source recovery records Git 3652383517d1d64a71d89391da30ce5e92924229, relevant-source.patch, new-files.patch, owned-inputs-final.patch and individual original-media path/hash references in fixture-identity.json. No source/media archive was created.
Fresh captures were personally reviewed before dependent actions. Ordinary creation selected male Human Fighter, Lawful Good, unchanged first roll 15/13/6/16/16/10, two proficiency points each in Axe, Long Sword and Two Handed Sword, and default portrait/colors/sound. Uppercase A was accepted by the game, which displays the name as a. The opening scene and Imoen conversation completed. review/imoen-party.png records her weapons-room hint: west and a bit north, off the upper corner. pause-check, portrait and unpaused captures establish actual red PAUSED/UNPAUSED and explicit protagonist portrait selection. The lower-left clock was not used as Select All.
The first westward ground destination produced no displacement. Native map inspection and a different visible upper-corridor destination then caused ordinary pathfinding around the cage platform; upper-corridor and upper-arrival distinguish the positions. Arrow-key camera panning exposed the upper corner. doorway shows a native cyan door outline; subsequent captures show the opened door and passage through its floor threshold. Several points on wall/fixture pixels produced a forbidden cursor and no further movement; later floor/object interaction moved the protagonist into the adjoining portal room. The room’s identity does not establish the weapons-room route. inventory-before shows the native inventory with empty carried slots and empty Ground panel. portal-inspect, portal-response and portal-near show the protagonist inside the room beside its portal, without a key, loot panel, transition or release consequence. No portal-key requirement was inferred from the absence of a response. The unresolved task is locating the actual weapons container and completing its native pickup interaction. One premature local image read preceded asynchronous retrieval completion; the existing fetch was allowed to finish, with no input replay.
One UUID-idempotent box, bx_yeawsj48, was created at 01:04:36 UTC after the detached deadline watchdog was observed armed and /home exceeded 5 GB free. Original expiry was 01:44:36.099 UTC. The immutable browser deadline was 01:26:24.482 UTC; the independent watchdog deadline was three minutes later. The sole original launcher started at 01:05:40.105 UTC. Actual runtime: Chrome 151.0.7922.108, V8 15.1.206.16, six guest Workers, process 1000/endpoint 1/slot 0, Win98Renderer/Canvas2D and no render-worker endpoint. The recovered live module is f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121 (2,182,500 bytes). Toolbar WebGL selection does not qualify GL coverage.
All 96 published commands have exact successful ACKs, with 55 independently released mouse actions and ten independently released key holds; UNKNOWN and replay counts are zero. Before close, passive inspection found no held keys and an empty input queue. Chrome closed normally at 01:25:25.668 UTC, exit 0/no signal, before its cap. The first terminal check raced the driver’s process exit and failed its process-absence assertion. A subsequent read-only observation confirmed both recorded PIDs absent; a fresh terminal collection then passed. No game input was retried. All 1,021 terminal artifacts (56,392,956 bytes), including unique logs/captures and the live module, were individually retrieved and SHA-verified before normal stop was requested at 01:26:29.858 UTC. Terminal runtime pins matched; both runtime ports closed and the profile was removed. Stop stop_cbd2800336f620bf completed without force at 01:26:32.164 UTC. Final state is archived, expiry cleared. The watchdog observed normal stop and exited; the local board watcher was stopped.
Validation covers the actual uppercase request chain and lowercase zero-effect negative, original/runtime hashes, native pause and navigation captures, empty inventory/Ground, exact ACKs, artifact recovery and resource cleanup. This is documentation only; no tracked emulator/tool code changed and no code build was required. The scoped evidence schema/reference check passes; the global checker retains seven unrelated containment errors. No extra box, resume/delete, guest/save/configuration/clock edit, private handler, fabricated restore, source archive or public deployment occurred. A separately authorized fresh run must resolve the weapons-room/container route before claiming key acquisition or Jaheira release. Do not reopen this archived stream. Combat, FPS, audio, GL and full playability remain separate.