Q3 current checkpoint native progress, 1585
Run: scratch/runs/20261109-q3-current-checkpoint-native-progress-1585/.
The published 29c7a9f725011270dc3e62562a758aef36eaa299 preparer and explicit
q3-checkpoint-b993419a5-v1 generated actual 1475 caller reached native
fixture/cancellation success and original relative-pointer menu progress.
World movement and firing remain UNVERIFIED. The single original attempt
stopped at its first command work deadline; there was no retry or waiver.
Fresh controls and transfer
Before runtime transfer, the production integration test freshly passed its nine executable prelaunch cases and six generated owning-caller cases. Its independent observable watchdog joined, with actual waits and separate EOF. The real run control and then the entire generated caller were imported with process/network effects refused; nine local Python source references were recorded, including deferred imports resolved from bytecode cache paths.
The new tools/q3-current-checkpoint-native-progress.test.py executes the
production Node composition, fixture composition, actual bound-input compile
hook, and original diagnostic/pointer preloads. A read guard admits only
pinset members with matching SHA and size. It observed 27 providers and
freshly refused each of 54 missing/stale substitutions at the actual read
boundary. It blocks child-process effects. The same positive check passed
against the actual remote staged closure before Chrome. A first test-authoring
assertion incorrectly expected a diagnostic filename in the composed consumer;
that failed iteration is retained, and the assertion now checks the real
startup module seam. Native attempts were not involved in that correction.
Fresh client, startup and complete fixture controls passed, as did
flock /tmp/wine-build.lock bash tools/build.sh. No production provider needed
editing; the committed change is the new regression and this note. Shared Q2,
custody, CPU, WAT, host, Redline, observer/client/stream and startup providers
were unchanged.
Q21575's genuine final publication/release at 14:41:13Z was verified before
fresh runtime pins or allocation. Its exact box bx_tuwugvr3, UUID
9d26b631-36a4-4a44-810e-6bde1f6de795, was freshly API-verified ARCHIVED with
completed unforced stop stop_b9b9272e814d13bc. Retained physical proof showed
200/200 reaps, closed ports, no profile/writers, a free lock and separate waits.
The release detector matches the actual board actor and status tokens; quoted
release text in an OWN line cannot open it.
Native evidence
The new immutable 25-minute UUID watchdog was observable and heartbeating
before allocation. Both actual remote runtime preflights imported their
dependencies before spawn. Native startup authenticated actual owning Worker
bytecode 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18
(2,186,068 bytes), live ownership and flags. Compatibility module references
remain ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf.
The changed fixture passed nine negative controls, actual WebGL positive presentation, screenshot/raw response, action ACK0, and the physical Enter held-high/released-zero receipt from the owning renderer reader. Its actual checkpoint published at 14:44:59.662Z within the unchanged 60-second observation and 70-second transport bounds. The planned owning cancellation passed all three distinct remote parent waits with separate stdout/stderr EOF; kernel custody reaped 168/168 identities. Independent physical inspection found both ports closed and no profile, runtime FD holders, input writer lock or runtime lock holder. Browser normal-close EOF remains UNKNOWN; kernel reaping does not establish it. The caller's expected local launch termination is not a normal gameplay completion receipt.
The single conditional original attempt obtained six reviewed native captures and five successful action ACKs. The cursor visibly moved by explicit relative counts; Enter opened CHOOSE LEVEL with Q3DM1 selected. A relative-count click on FIGHT advanced to DIFFICULTY. These are actual screenshot/action responses, not guest-state writes or fixture screenshots promoted to original gameplay.
The next FIGHT command, start-arena, pressed/released the native mouse and
waited its requested 10 seconds. Its first browser failure at
14:52:44.520Z was command work deadline; never resend (command 5, 30-second
work budget). Screenshot request 522 had been submitted and its send
returned at 14:52:31.156Z. It had no raw response before the terminal deadline,
13.36 seconds later. This is not a 20-second CDP deadline or browser EOF claim.
The screenshot's pre-request page, guest-instance, renderer-owner and producer
replies exist; they do not prove screenshot completion or world playability.
The action has no successful ACK. No later guest input, capture or retry ran.
Historical1475 cause and browser EOF remain UNKNOWN.
Original cleanup recorded all three distinct remote parent waits with separate EOF, 350/350 actual kernel reaps, ports 36053/33359 closed, profile retirement and no writers/lock holders. Copies of parent receipts are not extra waits. The original controller joined; normal browser-close EOF remains UNKNOWN.
Evidence integrity and shutdown
The 1535 review was independently repeated: all 2,485 SHA/size entries match,
1,209 gzip streams pass CRC, and exactly five are INVALID. The two
observer-{baseline,final}/wait-gzip-damage/output/bad.json.gz files are damaged
negative fixtures. These three are INVALID_EMPTY_GZIP, never evidence:
integration-1/damaged/prepared/prelaunch-command.log.gzintegration-1/partial/prepared/prelaunch-command.log.gzproduction-direct-final/partial/prepared/prelaunch-command.log.gz
The new cancellation run also produced an EMPTY/INVALID source
cancellation/prepared/execution-boundary.jsonl.gz. Its zero bytes are preserved
inside a verified gzip recovery envelope and explicitly excluded from proof.
The separately valid durable checkpoint journals, screenshot-response trace,
physical receipts and cancellation controls supply their own evidence. The
original retrieval has no invalid source gzip. No empty evidence was promoted.
Before normal shutdown, all 78 unique cancellation artifacts and 115 unique original artifacts were retrieved, independently SHA/size checked and gzip decoded through CRC. Existing media and modules are referenced by path/hash, not duplicated. Exact Git bases plus small owned patches provide source recovery; no source archives were made. Finished owned duplicate journals were losslessly compressed with SHA/size recipes. Released1535 identical valid-gzip duplicates were hardlinked without changing any path bytes or touching INVALID files; the mappings preserve recovery and saved about 6.5 MB. Disk headroom remained thin; a brief sub-threshold observation triggered that recovery.
Final box: bx_fgp2sh86 / ARCHIVED, UUID
3021654f-2102-4663-8572-3abf38268617. Initial expiry:
2026-11-09T15:08:20.819Z; final archiveAfter:null, expiresAt:NOT_RETURNED.
Delegated normal stop stop_5169faa2b0691980 completed unforced with no
error at 14:54:10.143Z after evidence verification. The independent watchdog
actually joined with status 0 and separate stdout/stderr EOF; its lifecycle
parent also joined. No new agents, workers, public deployment or Heroes II work.
Next: inspect the retained screenshot522/command-budget evidence offline to identify a causal repair that preserves existing deadlines. A new native run needs separate authorization; this worker stops with movement/firing unverified.