Baldur’s Gate II equipment attempt: launch harness blocker, 2026-11-07
No new equipment, container, rescue or encounter consequence was reached. The single launch attempt stopped before Chromium or the original guest started: the copied driver requires deadline - start < 30 * 60000, but this run supplied a browser deadline 32 minutes after box allocation. This is an avoidable run setup error, not an emulator or BG2 defect. Historical gameplay acceptance and the Minsc recruitment evidence at 6e4578f03 remain valid.
Evidence is in scratch/runs/20261107-bg2-equipment-encounter/ (ignored). Source identity was main 9a2a976e8549f55283ca80fe6e43888063baf679, with relevant tracked changes and new-file patches retained separately. No source/media archive was made. All 645 registered original files, totaling 850,839,386 bytes, matched the retained inventory. BGMain.exe SHA-256 is 944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b. The 1,283-file staged closure matched at launch and terminal inspection. Its staged Wasm was e41511fe861363fbe1639d80f20cbcdd7240f46937c93a801eaa256ca094c467; no live original module, renderer or scheduler identity exists for this attempt.
Before allocation, the generated actual-Chromium fixture passed trusted balanced controls, nine owner/module replacement refusals, stale/slow capture refusal, partial/UNKNOWN/late-ack closure and independent release checks. Its labeled generated canvas was reviewed. These controls launched no original and are not BG2 gameplay evidence. The original attempt made no viewport change because it failed before browser creation.
One UUID-idempotent box, bx_jxr76nhw, was created at 09:36:05 UTC with expiry 10:16:05 UTC. Launch PID 5811 exited on the deadline assertion at approximately 09:36:40. The subsequent readiness observation returned no transport outcome; it was not replayed. A separate terminal inspection recovered the exact assertion log and established that the launcher was absent, no Chromium/profile process existed, no runtime ports were opened, the profile and writer lock were absent, and no original input had been dispatched or held. Fourteen unique remote artifacts (609,107 bytes) were recovered and SHA-256 verified before the explicitly delegated normal, nonforced stop request at 09:37:43 UTC. The final box-state receipt is retained with the run.
Only this note is committed. No emulator semantics were changed, and no FPS, audio, parity or new gameplay claim is made. The next authorized fresh attempt should validate the deadline invariant locally before allocation and select a browser cap below 30 minutes, reserving the remainder of the 40-minute window for retrieval and shutdown. It must still follow freshly reviewed creation/dialogue screens and then try ordinary equipment/container interaction.