Q3 settled source: exact control reuse refused before allocation

The first terminal is PREALLOCATION_EXACT_CONTROL_CLOSURE_CHANGED. No original NEXT/world runtime ran. There are no current run pins, selected modules, allocation, watchdog, guest input, capture, ACK, relative counts or retry. NEXT selection and world progress remain NOT_VERIFIED.

Both required final published RELEASE STOPs were observed before any settled source check: Q21425 5c8780318afbbe0e5a4e7c64190f2e0abde21cd0 and Redline1435 f977ebf7c28977d7d95eb404f43db2209d163dde. Both are ancestors of main and origin/main. Existing source providers were clean. Board instructions constrain new workers1455/1465 to new tests and in-memory candidates, with existing-provider mutations waiting for this worker's final release. No concurrent provider drift was encountered or worked around.

The authenticated1305 fixture/cancellation evidence remains intact: seven referenced artifacts pass SHA-256, size and gzip CRC checks. Four of the five required control files match. tools/native_kernel_custody.py changed from 31987 bytes / 05b7fe42cf7ac09df5f12f0ea073ea066892efb598b64b05fae19a3492c9f32c to34396 bytes / 3448afd4c5ec4ea691c584a6cfde3a61b72f5c9143458189c1035f374c4c6240. The new bytes match published Git source. The actual Q3 composition's compose() also rejects with Q3 provider changed: tools/native_kernel_custody.py. The expected rejection was actually waited with separate stdout/stderr EOF; no browser, server or guest was started by this check.

The owner requires exact unchanged control closure for1305 reuse and excludes qualification repetition. The coordinator's13:27 board message authorizes a narrow current module/preparer/caller migration, but conditions fixture reuse on that same unchanged closure. A versioned hash update would not satisfy it. Consequently no preparer, composition pin, production source or module was changed, and no historical custody/module was substituted. A future task needs explicit scope for proof of the changed control closure before native progress.

Read-only API verification after both releases confirms predecessor bx_rfgz429k, UUID 5adf5b34-c76e-447d-b734-996cfe43bfd0, ARCHIVED with completed unforced normal stop_c6f706024295cebc, ended 2026-11-09T13:03:19.518Z. Physical drain is referenced from1395's release. Initial expiry was 2026-11-09T13:24:02.050Z; final archiveAfter null, expiresAt NOT_RETURNED. Historical unresolved lineage, kernel completeness and browser EOF failures remain unresolved. No lifecycle mutation was issued. New box ID/state/expiry/stop receipt and watchdog/join are NOT_APPLICABLE.

Evidence: scratch/runs/20261109-q3-settled-source-relative-progress-1445/. Exact Git base 339870e5644c6d07be78b583456290ef596cc28b, empty relevant uncommitted source patch, small published custody delta and owned new-input patches provide recovery; no source-tree, media or module copies were made. The first evidence script completed release, reuse and actual composition checks before an offline helper import failed for missing admission search path. A separate read-only predecessor script supplied that helper directory; no composition, runtime, capture or input was retried. Focused settled-source refusal checks and the locked build are retained. Final SHA/size/gzip-CRC reread covers local evidence; free/home remains above1.5GB.

Only this note is committed. No shared-client/custody/host/WAT/Q2/Redline/ HeroesII/CLAUDE edits, local Chrome, agents, workers or public deployment. SingleTaskSTOP after publication.