BG2 sealed handoff: first unchanged New Game transition
Key acquisition, Jaheira release and party/world consequences remain unverified. The sole fresh run reached the BG2 main menu and Single Player submenu. Its next reviewed image still showed that submenu after the New Game click. The worker immediately cancelled the owning supervisor and sent no later game protocol, input, capture, retry or quit. No second native attempt occurred. Historical Minsc/3000 XP and movement are not new progress.
Evidence: scratch/runs/20261110-bg2-sealed-handoff-key-rescue-0458/.
The required prior handoffs and repository rules were read. Before allocation,
the locked build and all 29 exact newly emitted caller/current installed Worker
controls passed, including ordinary keys, independent releases, exact/wrong ACKs,
sticky refusal and the launcher lease regression. All 645 original files matched
size and SHA-256, totaling 850,839,386 bytes. BGMain.exe remains
944db091d82c6144db8c9a21c085e4504bdc549fca8003c31e309646567bb98b.
Git base, relevant binary diff and new run-input/dependency patches preserve
source recovery. No source/media archive was made; media is referenced by path
and digest. Shared CPU/runtime, CRT, startup and renderer files were read only.
Sealed launch and first failure
UUID fea20ed6-9df4-4427-baa7-5d0212f285b5 bound the single new box
bx_ky3ka57g. The independent watchdog was observed armed before allocation
with immutable deadline 05:25:22.518442 UTC; initial API expiry was
05:25:22.195 UTC. The original browser deadline was 05:23:22.518 UTC.
seal-lease ran before the first staging operation and added the exact
83-byte lifecycle JSON pin. Bounded 1 MiB staging then verified and published
all 1,340 entries, including the complete original fixture and allocation
metadata. The earlier missing-lifecycle failure did not recur.
Actual Chrome was 151.0.7922.108 / V8 15.1.206.16, six guest Workers and the
retained Canvas2D game route. The recovered live module is
1b7319ff24f64d6c886803f23cb9ea88447967da4ba88fef0b177961007dc608,
matching the pinned primary module. Toolbar WebGL selection is not renderer
qualification. Each of the three screenshots was personally reviewed before
any dependent input. Startup showed the main menu; a native 700 ms click on
Single Player opened its submenu. A native 1,000 ms click on visible New Game,
followed by the requested 1,500 ms wait, returned an image of the same submenu.
Both numbered commands have exact successful ACKs, paired guest down/up log
entries and independent mouse-release receipts. This proves delivery through
the recorded input route, not successful entry into character creation.
The first failure is the unchanged expected screen. Late asset-cache activity after that capture does not prove either eventual character creation or a guest deadlock. No unsupported runtime cause, timing repair or gameplay fix is claimed. There was no later observation of the game screen.
Supported offline image-check repair
The automatic whole-canvas check accepted 7,408 changed pixels, all inside the
New Game button's rectangle (x84/y389, 179x65 in the full screenshot). The model
review correctly rejected the unchanged menu. This establishes a caller
acceptance gap: button artwork alone can satisfy changed > 0.
The title-only driver now accepts a validated transitionRegion: [x,y,w,h],
normalized to the game canvas and selected before input. Its existing
post-input comparison checks that region and records both normalized and actual
pixel bounds. For this observed menu, [0.43,0.05,0.5,0.85] excludes the button;
the actual retained image pair has zero changed pixels there. A future separately
authorized New Game command can require a change there. This is an image
predicate, not semantic recognition or a substitute for individual model review.
Commands without an explicit region retain their whole-canvas comparison.
The repair neither repeats input nor changes capture age, waits, clocks, tiers,
budgets, deadlines or runtime providers.
The complete repaired emitted execute body is tested offline against the actual PNG pair: the old full-canvas predicate accepts it; the explicit region rejects it, latches cancellation and permits zero later sends. Authored button-only and valid region-change controls balance that negative; malformed regions refuse before publication. All 36 focused controls pass. The nested offline fixture loads the exact emitted CommonJS bytes with repository dependency resolution, preserving the launched top-level files and their original pins. Offline lease fixtures are discarded after testing. This is no second browser/native run.
The final locked build passes, followed by all 36 controls against the current
installed Worker and compiled module (the same 1b7319ff... bytes). An interim
build stopped on another worker's unfinished ALU callback-census mismatch; its
owner withdrew that WIP before this successful build. No shared source was
edited by this worker. The evidence checker reports zero errors, missing files
or invalid records for this run; 23 unrelated containment errors remain global.
Recovery and shutdown
All 60 unique terminal artifacts, 8,444,148 bytes, were retrieved and verified by size/SHA-256 before the sole normal stop request. Four gzip streams passed decompression/CRC checks and all three PNGs passed full decode/CRC checks. The outer parent's actual wait returned 1 and stdout/stderr EOFs were separately recorded. Kernel custody records all 174 owned tasks reaped, no remaining or unreaped tasks, and complete lineage; those receipts are retained. The independent watchdog's parent actually waited for exit 0 with both EOFs.
The delegated stop is stop_8e547cf3f1cd0a52, completed at
05:03:38.992 UTC, forced false, error null. The delegate's observed final state
is archived, expiry null. Its receipt/state and wait records are retained;
the assigning root owns separate final API verification. No resume, delete,
local Chrome, nested worker, guest/save/configuration edit, artificial native
call, deadline extension or second box was used. Other boxes were untouched.
Next is a separately authorized fresh native attempt after the image predicate repair is published. It must establish ordinary character creation, then the weapons-room key and visible Jaheira release/consequence. No combat, audio, FPS, GL or full-playability claim follows from this run.