Q3 repaired initialization admitted; startup image deadline remains blocked

Evidence: scratch/runs/20261110-q3-repaired-initialization-arena-0250/.

This task uses published initialization repair 29fff6c1f and published CRT authority e7e0312bd. Shared startup, CRT, Nox and LBreakout providers are read-only. The accepted native fixture is reused by its unchanged SHA-256; there is no native fixture repeat.

The locked build passed. Current focused controls execute the whole generated caller through production preflight with zero process effects, reproduce the old eager-adapter initialization failure, and pass the repaired initialization. The actual emitted Worker transport and production host initialization pass with both real compiled modules and the installed instance checked. Synthetic natural CALL/entry/RET, unarmed zero callbacks, seven startup refusals, six chain refusals, seven command/capture boundary cases, and six terminal controls pass. These are offline controls and do not establish original-game consumption.

A supplemental legacy delivery test refuses a historical startup provider pin before its inert controller becomes ready. Its failure is preserved in input-delivery-fresh.log; shared startup files were not changed to satisfy it.

The sealed runtime has 950 providers. Five independent local manifest rereads pass. Source identity is recorded by Git SHA and relevant binary diffs, with owned new run inputs recorded as patches; no source archive is created.

Runtime Git identity was befbafc5b; the manifest SHA-256 is 44f23d3c73536cdf16f0ddadf8a9ae0e1832e95b5304bd28a04facca54b17259. Both remote prelaunch barriers passed with checkOnly:true, spawn:false.

The single original run passed the repaired initialization and admitted the actual observation Worker instance. Native admission recorded canonical Wasm 4f2c69a1528e01a9ab5127201d5e8a222da2a35236377a1351f444f55fa5a7d9 (2,186,099 bytes) and observation Wasm b731c8d3c3a31ce0ba6d5619f07f04b213969ded54209dc078ee4ea9a358e350 (2,186,193 bytes). Chrome was 151.0.7922.108, V8 15.1.206.16.

The first concrete failure was original image unavailable at the unchanged 50-second independent image-observer deadline, returned at 2026-11-10T02:56:16.746Z. The observer immediately invoked owning cancellation. The local controller's later transport EOF is a consequence, not the first failure. There were 39 startup readiness observations and 280 traced CDP requests, with zero input requests and zero screenshot requests. The last retained natural guest slice was sequence 1931 at EIP 0x443898, with no trap. No complete owning renderer readiness or startup capture was published before cancellation. This does not establish a guest hang or identify its cause.

All 170 owned processes were actually reaped, with no remaining or unreaped process. Generated parent, prelaunch child, runtime parent and local controller have actual failed waits and separate stdout/stderr EOF. There was no later protocol, input, capture, retry, quit, clock/state write or deadline extension. No native fixture repeat, source archive, evidence media copy, local Chrome, nested worker or operation on another box occurred.

Read-only recovery inventoried 55 regular artifact references and retrieved 48 unique files, 1,118,161 bytes. Independent SHA/size rereads and a second remote inventory matched before stop. All nonempty gzip streams validate; zero PNGs exist. The zero-byte execution-boundary.jsonl.gz has no finalized member and is preserved exactly; finalized-gzip status is explicitly false. The inherited stop helper initially refused that audit result before making any stop request. Its local-only correction permits the precisely audited empty container without changing its bytes or claiming gzip success.

Box bx_tc9bkdf5, UUID f36453ac-a0f3-45be-85af-0e970ff3698e, had initial API expiry 2026-11-10T03:17:44.119Z. The independent immutable 25-minute watchdog deadline was 03:17:44.858123Z, observed armed before allocation. Sole delegated unforced stop stop_976d2cb9fb819771 completed at 02:56:58.406Z. Final state is archived, expiry null. Watchdog and allocation parent have actual exit-zero waits with separate stdout/stderr EOF.

Arena and authentic input/Win32/Key_Event/UI consumption remain unobserved. The concrete blocker is missing startup renderer readiness and its image within the existing observer bound. Offline trace inspection does not justify a causal source repair; shared startup remains read-only. Next work should diagnose that readiness path offline before any separately authorized native attempt. This single-task worker releases its files and stops.