Q3 repaired original caller: early gameplay verification, 1816

This task uses published scheduling repair 2b945315a without editing the generated original caller. Evidence belongs to scratch/runs/20261109-q3-repaired-early-gameplay-1816/. Git plus gitbase.txt, relevant-uncommitted.patch and small explicit run inputs retain source provenance; no source-tree or media archive is used.

Offline preparation independently verified all 942 providers. The manifest SHA-256 is bab68a8cd2ad8696886d000bed817d48276a25af71798ce60686fe42aa3a5e3a; the generated caller SHA-256 is 25acfe27a8160d4a8b396f71636e41ae4d172b3cb7e8b011cb283ce8ae7764f1. The locked build passed. Primary module remains 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18, and compat remains ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf. Every sealed provider was independently reread after the build.

Fresh actual generated-original tests passed the entire launch function, real owning Session and retained command branch, including coalesced commands, fragmented UTF-8, EOF with pending input and sticky terminal failure. Both actual generated prelaunch/custody/staged consumer checks, generated owning-caller integration, 27 foreign-closure refusal controls and seven arena scheduling cases passed. Their independent offline watchdog waits and separate stream EOF are retained; they are not native cleanup evidence. The first arena test call incorrectly used a positional output argument; its failure is retained, and the correct environment-based invocation passed.

The actual retained transport still admits at exactly the 55-second ACK plus 30-second cleanup boundary and refuses one millisecond later before publishing a command. early-actions.json contains unsubmitted ordinary fire for 300 ms then W for 500 ms, each with zero extra settle. Each requires its own successful ACK and hash-verified current screenshot review. Ammo, alive HUD and visible consequence must be assessed before admitting movement. Death or first failure ends the test; a death camera cannot establish useful movement.

Both predecessor final releases were observed before allocation. Nox box bx_2as4ut9t was independently verified archived with completed, unforced stop_baf1f82b2a185e8f; Return Fire 1758 created no box. Historical missing joins remain failed and were not used as new prerequisites. The temporary shared disk-floor shortfall was recorded before allocation; coordinator lossless cleanup restored headroom before the runtime began.

Native observations and terminal blocker

One box, bx_hpghx7b2, was allocated after its independent immutable 25-minute watchdog was armed and observed live. UUID is 7c8cdb25-1e5b-489e-81ed-dba884260e18; initial archiveAfter was 2026-11-09T18:48:55.576Z. The watchdog deadline was 2026-11-09T18:48:56.343088Z; neither deadline was extended. expiresAt was not returned. All 942 uploads and both actual remote prelaunch check-only paths passed before Chrome.

The single native fixture passed the production-worker/module ownership, negative controls, owning WebGL draw/presentation, physical held-key/release and successful ACK0 gates. Planned owning cancellation passed the separate generated parent, prelaunch and runtime waits and stdout/stderr EOF. Kernel custody reaped 167/167 identities; physical drain passed. Its positive image was retrieved, hash-verified and visually reviewed before the conditional original launched. This fixture is not Q3 gameplay evidence.

The original reused its actual startup image for the first menu review, avoiding an extra capture command. Every successful current image was retrieved and SHA-verified after readiness or the corresponding successful ACK, then visually reviewed before the next command. ACK0 click and ACK1 Enter left the main menu visible; neither establishes its intended guest consequence. ACK2 bounded relative mouse movement and click opened CHOOSE LEVEL with Q3DM1: ARENA GATE selected. These are menu-control observations, not useful gameplay movement.

The next ordinary FIGHT click, command number 3, dispatched a successful mouse press and independently timed successful release. Its screenshot continuation failed at 2026-11-09T18:29:43.286Z with command work deadline; never resend. native-analysis.json independently audits the retrieved trace: the complete pre-screenshot ownership read took 12,413 ms, including renderer-owner Runtime.evaluate request 402 taking 11,973 ms. Screenshot request 408 was then still pending 6,911 ms into its wait when the unchanged command work limit expired. Page, guest-instance and render-owner screenshot probes returned in 5–9 ms; those replies do not establish compositor entry or screenshot completion.

This is a new in-command capture blocker, distinct from the earlier original caller's reproduced read-ahead defect and the historical prequeue admission refusal. The trace localizes the exhausted work budget but does not establish why the renderer evaluation or screenshot was slow. No speculative renderer or transport repair, deadline extension, ownership-check removal or new runtime attempt was made. The published caller repair itself was exercised unchanged.

First failure was terminal. There is no ACK3, failed-command image, command 4, later input/capture/retry, W command or fire command. No original arena world, ammo, alive gameplay HUD, firing consequence or useful movement was reviewed in this run. The objective therefore remains unverified, with this concrete capture-stage blocker preserved for source-backed diagnosis.

Recovery and shutdown

All 80 fixture and 98 original unique-per-session compressed artifacts were retrieved and independently reread before exactly one delegated normal-stop request. There are 170 distinct compressed hashes across the two sets. The offline audit checks stored SHA/size, original SHA/size and gzip CRC, the actual command/ACK sequence, mouse release, failure trace and absence of later work. No source or media archive was made.

Original kernel custody reaped 323/323 identities. Separate generated-parent, prelaunch and runtime waits and stream EOF were retained. Physical inspection passed: both ports closed, profile absent, no runtime FD holders and locks drained. The local interactive controller actually waited exit 1 with separate stdout/stderr EOF, unforced. Kernel root exit -9 and launch transport -9 remain recorded; normal browser completion is UNKNOWN despite a Browser.close ACK.

The box is ARCHIVED, completed unforced stop stop_be8291f1bda93533, ended 2026-11-09T18:30:17.097Z. Final archiveAfter is null. The watchdog observed the normal-stop confirmation and was actually waited with exit 0 and separate stdout/stderr EOF. No task box remains billing idle. There is no production-code change in this task; the publication records tested preparation, reviewed menu progress, the new native blocker and verified shutdown.