Q2 current witness: packaging terminal before admission

The one authorized current Q2 fixture stopped before readiness or admission. At 2026-11-09T14:09:17.992Z, the actual composed caller recorded its first terminal: Cannot find module './quake2-owning-load-witness.cjs', required by tools/quake2-frame-writer-witness.cjs. The versioned preparer omitted this transitive dependency. No guest input, screenshot, numbered ACK, cancellation checkpoint or original attempt followed. Guard defeat and onward-door progress remain unverified; earlier pickup/route evidence remains distinct.

The preparer is now repaired and tested offline as explicit version quake2-1495-published-5c8780318-writer-e5eff70be-f977ebf7c-v2. It authenticates the complete retained1265 manifest by SHA af301be22ff45b1595eae654e5406f712152ef5ec80b524d3179c8f49d0b7553. Every historical provider must match except fourteen enumerated published source/module changes. Four additional witness providers are authenticated against their exact published commits, including the missing owning-load adapter from e65895936. There is no historical module/provider substitution, blanket repin or unexplained-drift allowance. All WAT/compiler inputs match published 5c8780318; primary 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18 and compatibility ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf retain their exact published identities.

The new validator imports the actual caller's writer dependency chain in memory using only declared providers. Local checkout files cannot conceal an unstaged require or binary read. The real page-source constructor is compiled but never evaluated or armed. Removing the adapter reproduces the native missing-import failure; including it passes. Unknown versions, damaged historical manifest, unexpected WAT, both damaged modules, host/custody/ordinary-provider changes, both new witness-provider changes and an undeclared EXE read refuse. The declared-provider check also passes from outside the checkout working directory. The old actual startup fingerprint refuses the changed compatibility module; the new731-provider validation passes. Historical manifests stay unchanged.

Both current CPUs pass the existing actual-composed-caller1465 tests, including real Worker publication, admission/arm lifecycle, signed health -1, loss98, UNKNOWN, independent UP and sticky first failure. Those authored offline controls do not establish native game execution. Twenty-one unchanged actual generated request controls pass. The actual generated launch also passed a no-Chrome preflight with explicit QUAKE2_NATIVE_WRITER_WITNESS=1 and QUAKE2_NATIVE_CUSTODY_VERSION=publishedf977ebf7c, a content barrier and actual separate stdout/stderr EOF at its three nested parent layers. That preflight exited before the missing runtime require; it was insufficient to establish the staged transitive closure. The new regression addresses that omission. The final focused tests and required locked build pass after the repair.

Before Q3's release, work was restricted to new paths and in-memory preparation. Existing provider edits, module selection, fresh pins and allocation waited for Q31475's final published RELEASE STOP at13:59:18Z, 6d966f9d1d6cf8e2f853cf216844944ca006e46e, plus physical drain and direct API confirmation of exact predecessor bx_5bnxexae, UUID 7ec80f03-dd7d-47d5-b90b-a1415f8d3f82, archived under completed unforced stop_54e758ada497a4ee. Its initial expiry was14:15:28.321Z; final expiry was not returned. Q3 current-module/startup/prelaunch providers were untouched. No shared caller, custody, host, WAT, passive reader or witness provider changed.

Initial preparer version v1 and its tests were published as 89c118b07 after focused tests and the locked build. The sole runtime used that exact Git base and a small owned-input patch, with an immutable736-provider pinset. Both required flags appear in the recovered actual compiled-caller receipt. The owning observer's arm/admission was never reached; before-admission UNAVAILABLE remains explicit in the unchanged caller contract. No native numeric writer receipt or cancellation proof is asserted. No fresh runtime pinset, fixture, original, input or capture was produced after the terminal. Version v2 is an offline packaging repair only; historical1305 proof cannot qualify this closure.

One observable independent immutable UUID25-minute watchdog was prearmed and checked before allocation. New box bx_rup3afnj, UUID fcb86e70-6cdf-4166-8a5c-c03951aa45fc, had initial expiry 2026-11-09T14:32:42.819Z. Before delegated normal stop, fixture38 artifact rows /36 unique contents and root40 rows /37 unique contents were recovered, compressed before transfer and independently SHA/size/gzip-CRC reread. Proof commands were retained before transfer wrappers; no raw artifact was renamed. No invalid source gzip was reported. Valid empty gzip members are distinct from an empty .gz, which the recovery code explicitly labels INVALID.

Browser cleanup ACKed, exited0 without signals and drained in14189ms. This is failure cleanup, not an ordinary fixture quit or cancellation qualification. Three nested parent receipts retain actual wait1 with separate stdout/stderr EOF; the supervisor and caller-parent receipts describe the same child and are not independent extra waits. The local caller also actually waited1 with both EOFs. The unchanged custody owner merges the Node command's stdout/stderr into one pipe: its command EOF is combined, and separate EOF for that layer is UNKNOWN. Custody records124 owned processes and124 actual reaps, command EOF, complete drain and zero remaining, unreaped, unresolved lineage/ptrace/resume entries. Ports34081/44917 closed, the profile was absent, no profile FD holders or input writer lock remained, and the runtime lock was free. Kernel reaps do not substitute for browser EOF.

Normal stop stop_4f9d8efe9188c04c completed unforced, error null, at 2026-11-09T14:10:25.105Z. Final exact-UUID API state is ARCHIVED, archiveAfter null, expiresAt NOT_RETURNED. The watchdog and lifecycle actually joined0 with separate EOF and released the local runtime lock. Native lifetime is revoked; all-writers, aliases, peer/raw-host writes, parse generation, frame ABA and lifetime coverage remain UNKNOWN; nativeQualification remains false. Repeated-copy equality was never promoted to atomic/source proof.

Evidence: scratch/runs/20261109-quake2-current-witness-guard-progress-1495/. Initial Git base ca04c99b4e18831e44279ae3e33964032691047f, actual runtime base 89c118b07a3ed65ae4d656398f140d9d5184bdd8, small binary patches and owned input patches provide recovery. Git is the source archive. No source-tree archive, media/module evidence copy, local Chrome, public deployment, agent or Codex worker was created; free/home stayed above1.5GB.

Offline setup errors are retained: the first archive-API helper import lacked its admission search path; an old-refusal assertion expected host drift before the earlier compatibility-module mismatch; an invocation assertion expected a literal path where the generated caller uses root; an unnecessary rerun of the already-passing contract test refused its existing output directory. These occurred outside native execution. The actual native missing dependency is separate and ended the sole runtime attempt without retry.

Next prerequisite is a newly authorized current Q2 fixture/cancellation test using the repaired closure, followed by an original only if that fixture passes. This single task stops after publishing the tested repair and exact terminal.