Baldur’s Gate II bounded staging and native movement, 2026-11-08

Bounded large-file staging completed, and this fresh original run demonstrated native movement around the starting cages to Jaheira: the party left its starting position, approached her cage, and opened her dialogue. This is new movement evidence. Travel beyond the cage room, acquisition of her key and her release remain unverified. Historical Minsc recruitment/3000 XP was not repeated or counted as a new deliverable.

Evidence is retained in scratch/runs/20261108-bg2-largefile-gameplay/ (ignored). The corridor and cage-rescue notes were read. All 645 originals passed local size/SHA-256 checks, totaling 850,839,386 bytes; BGMain.exe remains 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b. All 1,283 runtime/input pins, plus their manifest, passed remote verification before the sole launch. The complete staging receipt has 1,284 entries. Runtime inputs match the preceding corridor attempt outside the owned run helpers. Source recovery records Git 0ae814c024e607bca09b0865305d20fe072b2f5b, relevant tracked changes, untracked dependency patches, owned helper patches, and original media paths/hashes. No source/media archive was created.

The actual owned staging helper now uses bounded 1 MiB PUT bodies and reconstructs each large immutable file remotely. Every part and reconstructed file must match exact size and SHA-256. Publication uses os.replace only after verification; the final compact publication pass verifies the complete required closure before publishing its remaining members. Each part permits at most two PUT attempts, with a fresh URL and unique temporary path. A timeout requires a read-only remote observation: matching bytes may be accepted; unresolved verification cannot license another write. Late abandoned uploads cannot overwrite the accepted file. The socket and absolute PUT budget is 20 seconds plus size at 1 MiB/s, bounded to 30–180 seconds; actual chunk bodies use the 30-second minimum. Final part concurrency is four per large file, at most 32 PUTs across eight file workers.

Seven local transfer cases passed, including an 18.2 MB body, delayed reader, truncated delivery, timeout after complete delivery, and the actual helper’s reconstruction/hash/atomic-publication path. Truncated bytes were never accepted; the matching timeout case needed no retransmission. The predecessor’s qualified Space, ordinary keys, mouse, typing and numbered exact-ACK helpers were reused byte-for-byte. The scoped production driver passed its local final app-selection boundary with zero original launches. Initial negative-test assertions incorrectly expected only one concurrently submitted truncated part; corrected assertions count bounded distinct parts, and the retained final tests pass.

The fresh service showed slow large-body delivery in read-only observations of its hidden upload temporaries. Before any game input, the raw provisioning process was explicitly cancelled, and exact existing files were observed and reused. Serial chunk staging was also cancelled after measuring insufficient throughput; verified parts were then reused with bounded parallel uploads. These were immutable fixture operations within the same box, with no game-input replay. The initial six-minute staging budget was revised to a fixed nine-minute cap from box creation, inside the unchanged 22-minute browser deadline and 25-minute independent watchdog. Final parallel provisioning observed 596 matching files, staged the remaining 687, and completed full publication at approximately 00:26:08 UTC. A compact remote manifest avoided transporting the full publication plan as a large command argument. No required media was skipped.

One UUID-idempotent box, bx_dc6x3n6m, was created at 00:19:26 UTC after local transfer tests and the 5 GB disk check. The detached watchdog was armed beforehand; the original box expiry was 00:59:26.421 UTC. The sole original launcher started at 00:26:16.874 UTC. Actual runtime is Chrome 151.0.7922.108, V8 15.1.206.16, six guest Workers, process 1000/endpoint 1/slot 0, and Win98Renderer/Canvas2D with no render-worker endpoint. The recovered live guest module is f9650607181301b5d2a9990420f437bd9f1ca10d40ac73067339f07499d53121. The toolbar’s WebGL selection is not the game’s renderer identity.

Normal character creation produced male Human Fighter a, Lawful Good, with the first roll 13/11/14/17/11/9 unchanged, two points each in Axe, Long Sword and Two Handed Sword, and default portrait/appearance/sound. The right proficiency arrow was initially misread as allocation; the observed unchanged count led to the correct left control. The opening scene and Imoen’s dialogue completed normally. Her weapons-room hint was reviewed. Space produced actual red PAUSED and UNPAUSED messages, and the protagonist portrait was selected before a fresh destination. That first ground click did not establish displacement. The lower-left clock was then mistakenly identified as Select All; its new PAUSED message was immediately recognized and corrected with Space. A fresh ordinary click on Jaheira’s visible cage then caused locomotion around the cages and opened her dialogue. Reviewed resume, jaheira-approach and jaheira-near captures distinguish the starting position, movement and arrival/dialogue. Her initial explanation advanced, but no key acquisition or release is claimed. No generic emulator failure or emulator fix was established.

All 77 published commands have exact successful ACKs, with 58 independently released native mouse actions and four independently released key holds. There were zero UNKNOWN game inputs and zero replays. The last capture records cleared physical keys. The driver closed Chrome normally at its immutable deadline, 00:41:16.748 UTC, exit 0/no signal. A subsequent capture request was refused at the existing child exited check before ID/command publication; it was not replayed. Two premature local image reads during asynchronous retrieval are observer errors only and caused no game action.

All 849 terminal artifacts (48,508,781 bytes), including unique captures/logs and the live module, were individually retrieved and SHA-verified before normal stop was requested at 00:41:46.846 UTC. Stop stop_5fe2a6f152e40125 completed without force at 00:41:48.633 UTC. Final state is archived, expiry cleared. Terminal pins passed; runtime PIDs were absent, both ports closed and the browser profile removed. Cancelled local provisioners, the local production fixture and the watchdog exited; the watchdog observed normal stop. Local disk remained above 5 GB. No extra box, resume/delete, SSH bypass, public deployment, guest/save/configuration edit or private-handler action occurred.

Validation covers bounded staging, exact original/runtime hashes, qualified native controls, actual pause transitions, reviewed movement to Jaheira, exact ACKs, artifact recovery and shutdown. This is a documentation-only commit; tested staging helpers and their recovery patches remain in the owned ignored run, and no tracked emulator/tool code changed. The scoped evidence check passes; the global checker retains seven unrelated pre-existing containment errors. Next: a separately assigned fresh normal run can pursue Imoen’s west/north weapons-room hint, obtain the native cage key and free Jaheira. Do not resume this archived box. No combat, FPS, audio-quality, GL or full-playability claim is made.