Q3 current-source migration; native fixture stopped before readiness

The versioned Q3 preparer/composition migration passes its offline controls and the locked build. The one changed-control native fixture did not reach its cancellation checkpoint within the existing 60-second observation bound. That first terminal barred the original attempt. NEXT/world, guest consumption and native cancellation qualification remain NOT_VERIFIED. No native retry, input, capture, relative counts or original Q3 launch followed.

Both required final published RELEASE STOPs were observed before module selection, preparation, provider edits or allocation: Redline1455 12c6c01e90d4d894462e286488dc3267cadee368 and Q21465 e5eff70bef07e208bf3d4436edc6655d3eabc4ae. Completion was checked after ten minutes. Both and the required CPU/custody/menu commits were verified ancestors of HEAD and origin/main. Their successors held existing providers frozen. Neither1455's collector nor1465's Q2 tools is a dependency in this Q3 manifest.

tools/q3-current-module.cjs declares q3-1475-published-5c8780318-f977ebf7c-v1. It authenticates the complete retained 1415 manifest by SHA-256 a6be3bee6fbf1c218a3982d8e991a44838abddc0a0b80c8bd4f45c3d6effe1dc. Every historical provider must match except fourteen enumerated changes: eight exact published CPU-mirror source/host files and two build modules from 5c8780318afbbe0e5a4e7c64190f2e0abde21cd0, exact diagnostic custody from f977ebf7c28977d7d95eb404f43db2209d163dde, and the three owned Q3 migration providers (startup, composition, prelaunch). All published WAT and compiler inputs are checked against the declared CPU commit, including inputs outside the historical runtime manifest. Both published commits must be ancestors of HEAD and origin/main. Unexpected source, module or provider bytes refuse before destination creation; there is no discovered-drift allowance or blanket repin.

The locked build reproduced primary2186068 bytes / 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18 and compatibility2188714 bytes / ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf. Historical manifests remain unchanged. Validated HTTP identities are updated from matching file identities. Only the retired1415 run input is omitted; small owned Python runtime inputs are explicitly added. The fresh931-provider manifest is read-only and sealed before allocation. No media or module was copied into local evidence.

Q3 startup now substitutes that exact primary identity into its existing Q3-specific admission composition. The shared admission source retains its historical identity and every ownership/release/deadline check. Q3 composition pins the new startup source and exact published custody SHA 3448afd4c5ec4ea691c584a6cfde3a61b72f5c9143458189c1035f374c4c6240. Prelaunch requires the new preparer/identity provider in its content barrier. Generated caller/control source is byte-identical across the composition pin migration. Immutable deadlines, independent UP, numbered ACK, first-terminal handling, physical-reader assertions and actual wait/EOF controls remain. The original-only invocation preloads published bae02f6a1 relative menu helper after native composition with Q3_MENU_POINTER_CONTROL=1; it was never launched.

Offline tests prove old1395 preparer FAIL, old Q3 composition FAIL, new PASS and thirteen preparation refusal controls: historical corruption, old/unexpected source, both corrupted modules, changed host/custody/migration/ordinary input providers, unknown options and foreign run inputs. Successful preparation rereads every file/HTTP identity, seal and immutable historical manifest. Full actual Q3 startup tests pass for original and generated fixture, including owner/module/flags/identity races, cancellation, late arm and deadline refusal. Dependency controls, joined-fixture command loop, cancellation checkpoint, physical controls, prelaunch (including missing current-module provider), retained numbered caller and pointer controls pass. No local Chrome ran.

The published pointer test initially refused its historical host.js pin, as expected after the CPU-mirror host change. Its same assertions pass when only that test's host pin is supplied by the complete current-source validator in memory; every other historical assertion stays intact. This neither edits historical evidence nor substitutes a historical module. An earlier physical test setup lacked the small owned physical_gate.py input; its failure is retained, and the corrected offline setup passes. These were not native retries.

Immediately before allocation, API inspection verified predecessor bx_rfgz429k, UUID 5adf5b34-c76e-447d-b734-996cfe43bfd0, archived with completed unforced stop_c6f706024295cebc; the board records physical drain. Its historical unresolved lineage/EOF is unchanged. The new run used the sole runtime lock and an independent observable25-minute immutable UUID watchdog, with process start identity, fresh heartbeat and plan hash checked before create.

New box bx_5bnxexae, UUID 7ec80f03-dd7d-47d5-b90b-a1415f8d3f82, was created at13:50:29Z; initial API expiry was2026-11-09T14:15:28.321Z. Provisioning and both remote no-spawn barriers passed for931 providers. One actual generated-fixture invocation used the existing cancellation checkpoint; no second fixture ran. The checkpoint observer returned the first terminal at13:52:17.497Z: cancellation checkpoint not reached. No endpoint, admission, physical positive, capture or ACK had been published. The browser's recorded readiness budget was still open; this is a checkpoint-observation failure, not proof of a browser readiness timeout or its cause. Owning caller cancellation then recorded terminal UNKNOWN, and no later input/capture/ACK was allowed.

Read-only cleanup evidence contains actual generated-parent, prelaunch-child, runtime-parent and local-caller waits with separate stdout/stderr EOF. The custody receipt records28 owned processes and28 actual reaps,600 journal events, complete:true, kernelForkLineageComplete:true, and no unresolved lineage, ptrace, resume, remaining or unreaped entries. ChromePID7507/start37095 has an actual kernel SIGKILL reap; browser-level wait and stream EOF receipts are missing/UNKNOWN. That kernel reap does not establish browser-level EOF or fixture success. Terminal-browser records endpoint unavailable. Chrome logs are valid empty gzip members; the execution-boundary file is zero bytes and explicitly INVALID as gzip. No missing diagnostic bytes are reconstructed.

The physical drain check passed: recorded identities absent, port40983 closed, profile absent, no runtime FD holders or writer locks, and runtime lock drained. Untraced-clone flags, nonleader completeness, native lifetime, allwriters and edictABA retain their existing UNKNOWN/REVOKED limits. Historical1305 proof is not reused to qualify this changed closure.

Collection retained39 regular files /35 unique artifacts, with compression before transfer and recorded proof commands before any evidence transformation. SHA/size and gzip CRC were independently reread; the empty invalid gzip is preserved as explicitly invalid source bytes inside a valid transfer wrapper. Collection is not browser EOF. Unique evidence was verified before delegated normal stop stop_54e758ada497a4ee, completed unforced at 2026-11-09T13:53:20.194Z. Final exact-UUID API state is ARCHIVED, archiveAfter null, expiresAt NOT_RETURNED. Watchdog and lifecycle actually joined with code0 and separate EOF; the sole runtime lock was released.

Evidence: scratch/runs/20261109-q3-changed-control-native-progress-1475/. Exact initial Git base ca04c99b4e18831e44279ae3e33964032691047f, small relevant binary patches and owned new-file/run-input patches provide recovery. Git is the source archive. Free/home stayed above1.5GB. No host/WAT/shared-client/ Q2/Redline/HeroesII/CLAUDE edit, agent, worker or public deployment occurred.

Next: investigate the bounded native checkpoint/readiness observation from the retained evidence before any newly authorized native attempt. This task makes no cancellation-qualification or original-game success claim and stops after publishing its tested owned change.