Baldur’s Gate II validated equipment attempt, 2026-11-07
Run evidence: scratch/runs/20261107-bg2-validated-equipment/ (ignored). This attempt first executed the generated driver locally with its exact proposed absolute browser deadline, before allocating any box. The driver verified 1,283 pins and passed its strict deadline guard with 1,498,668 ms remaining (<1,800,000 ms); no browser or original started during preflight. The deadline was fixed at 10:05:56.188 UTC, 25 minutes from preflight proposal. Staging is separate from live startup.
All 645 registered original files matched the retained inventory, totaling 850,839,386 bytes. BGMain.exe SHA-256 is 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b. The exact source commit is 47dbb7af4f7fc57c8b936c94e65985c6d240a212; relevant tracked changes and new-file patches are retained. Git is the source archive; no source/media archive was created.
Generated actual-Chromium fixtures passed trusted balanced native controls, nine owner/module replacement refusals, stale/slow capture refusal, partial/UNKNOWN/late-ack closure, and independent release. The labeled generated canvas was reviewed; it is not gameplay evidence.
One fresh UUID-idempotent box bx_utwttp9u was created at 09:41:04 UTC with expiry 10:21:04 UTC. The single launcher began at 09:41:42 UTC after staging; the production original route was launched at 09:41:48 UTC and its first live capture is 09:42:03 UTC. The 25-minute proposal left 24 minutes 13 seconds at driver start after staging. Native CDP preserves the 1024×768 viewport. The actual application owner is process 1000, endpoint 1, page Win98Renderer/Canvas2D, with six guest Worker slots and no D3D render-worker owner. The recovered live module SHA-256 is e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467 (2,182,493 bytes), matching the pinned build. Chromium reports Chrome/151.0.7922.71. Live scheduler slice and six guest Worker observations are retained with each capture.
Ordinary character creation was followed through freshly reviewed screens: male human Fighter, lawful good, rolled attributes 9/11/14/15/16/15, two proficiency points each in long sword, short sword and two-handed sword, default appearance/sound, name a. The opening completed normally and Imoen joined. Her dialogue explicitly pointed west-west-north to the weapons room. The hero baseline inventory showed empty equipment and backpack, zero gold, AC 10 and health 51/54 (review/inventory-before.png). Ordinary floor clicks moved the hero out of the cage and west; bounded native arrow keys scrolled the camera without resizing.
The new visible consequence is the equipment table opening its container panel, showing armor, shields and weapons (review/table-open.png, review/table-access.png). Item interactions visibly selected a sword on the cursor, but subsequent reviewed clicks into the backpack grid and sack did not establish storage: the hero inventory remained empty (review/inventory-check.png). The apparent disappearance of a sword from one earlier panel was not durable proof of acquisition; the reopened panel still showed the weapons. This is the first concrete interaction blocker, not an established emulator defect. No guest edits, cheats, callback/clock changes or held-input retries were used. No acquired item, Jaheira key/rescue, or first encounter is claimed. Minsc recruitment at 6e4578f03 and earlier gameplay acceptance remain valid.
The launcher received ordinary completion at 09:58:59 UTC; Chromium exited code 0 with no signal. Final live observation showed no held keys and an empty queue. Terminal verification found both runtime PIDs absent, both ports closed, the profile removed and writer lock absent; all 1,283 runtime pins still matched. All 817 unique remote artifacts (47,516,415 bytes), including captures, logs and live module, were recovered and individually SHA-256 verified before the delegated nonforced box stop request at 09:59:51 UTC. The final stopped-state receipt is retained. Local free disk remained above 1.5 GB.
Only this note is committed. No emulator semantics were changed; no FPS, audio or parity claim is made. Next: qualify an ordinary container-to-inventory transfer (including native drag/drop if required) against a generated positive-path control before another original launch, then attempt the key/rescue and first encounter. Historical gameplay acceptance is unchanged.