The actual Q2 composed consumer now supports QUAKE2_NATIVE_WRITER_WITNESS=1. Its retained bound.admit validates the reviewed capture and current owner before the wrapper installs pageSource using receipt.live.identity. The wrapper supplies writerWitnessGlobal to the existing passive reader. Initial captures before reviewed admission have UNAVAILABLE witness evidence under the opt-in. With no opt-in the previous absence of witness evidence remains.

Setup happens outside the six synchronous copies. Repeated admission reuses the same identity and arm; a second installation refuses the occupied slot. Page setup reserves its slot before awaiting the actual host arm, checks ownership again afterward, and closes an acquired binding on setup failure. Closing the consumer closes only its token's slot, waits for pending setup to settle and disarm, and prevents subsequent wrapper reads. The generated transport permits only that exact cleanup expression after terminal failure; ordinary evaluations remain refused. Cleanup failure records UNKNOWN and still runs browser cleanup. The first failure remains sticky. No reader acceptance predicate, guest read, six-copy ordering, health policy, retry, or independent keyUp rule changed.

The custody default still requires historical SHA 05b7fe42... and refuses the current source. A separate explicit setting, QUAKE2_NATIVE_CUSTODY_VERSION=publishedf977ebf7c, selects only published 3448afd4c5ec4ea691c584a6cfde3a61b72f5c9143458189c1035f374c4c6240. Unknown versions and unexplained byte drift refuse. Selection changes provider validation/reference metadata only; it adds no generated runtime behavior and does not replace any historical source or manifest. The 46 actual custody controls also pass on those published bytes. This is an offline version path, not native qualification or permission to reuse an old native proof.

Evidence is in scratch/runs/20261109-quake2-native-witness-install-1465/. The exact initial Git base is recorded there. Candidate transforms and the new tests ran in memory while existing providers stayed frozen. Existing source edits began only after Q3 1445's final published 1b106094bc6f2c421cb7a6c86c20b37510e0a082 RELEASE STOP at 13:30:27Z and the subsequent ownership announcement.

The same worker tested the complete generated consumer with the retained 1205 health transform, actual retained admission/capture/progress code, production host arm method, actual Node Worker, and current primary and compatibility CPU modules. CDP target envelopes, screenshot bytes, review, guest state and interleavings are explicitly authored offline controls. No native adapter receipt or browser execution is asserted. Absent-install old FAIL and explicit actual-composed new PASS are retained. Both CPUs execute the original publication REP and retain its 60 completed stores at the existing copy boundaries.

Controls cover setup failure, stale identity before dispatch, owner replacement during setup, occupied/pending slot refusal, pending cancellation, a foreign lifetime's teardown refusal, repeated admission and idempotent close. The generated health sink receives loss 98, signed death -1 and UNKNOWN, with both ACK and failed independent UP. First failure stays sticky and terminal ticker and ordinary evaluation perform zero later guest reads. OFF/ON acceptance and the 13,068 guest reads retain exact order for each paired schedule. The existing writer, reader-boundary and damage controls pass. Existing real Worker transport core controls run in memory with their historical-custody health-fixture section excluded; the new generated-consumer tests cover health using the explicit current version. The required locked build passes.

All-writers, aliases, peer/raw-host writers, parse generation, frame ABA and lifetime coverage remain UNKNOWN; nativeQualification remains false. No Box, browser, local Chrome, native game, media/module copy, worker fleet, host, WAT, shared client or custody source was created or edited. Box ID/state/expiry/stop receipt are NOT_CREATED / N/A; no Box watchdog was needed. Free /home space remained above 1.5 GB. Next work requires separately authorized current-closure native testing; this task establishes the actual caller lifecycle offline.