Q2 staged closure: browser CPU policy refuses the current module
The sole fresh fixture failed before admission. At 14:35:04.408Z the
owning browser startup rejected build/wine-assembly.wasm with
Quake II canonical PATHHASH. The unchanged
lib/quake2-browser-load-observer.js authenticates CPU
a320d4c85156644fd12b6134d66b11784f3100b9b135756206c087cdacd43295;
the explicitly authorized current CPU is
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18.
The caller's sticky terminal at14:36:06.467Z reports the resulting
original DLL load not parked. No ready/admission receipt, guest input,
capture, numbered ACK, cancellation proof, original attempt or retry followed.
Guard defeat and onward-door progress remain unverified.
New Q2-only tools/quake2-staged-closure-gameplay.cjs provides a standalone
preallocation validator. It first runs the explicit current preparer, then
evaluates the actual authenticated browser policy provider and requires its
canonical CPU identity to equal the authenticated staged CPU. Missing policy
or CPU, byte/size damage, and policy/module disagreement refuse. It never
replaces policy hashes, changes providers, starts a Worker or allocates a box.
The current closure intentionally fails this check. The existing preparer
and runtime providers remain unchanged; the browser policy incompatibility is
not repaired or waived.
The regression executes the real browser prepare with real canonical EXE
and current CPU bytes and WebCrypto. It reproduces the exact PATHHASH failure
before compilation or attachment, while the existing byte-closure preparer
still accepts those inputs. The new validator refuses before allocation.
An authored exact-policy positive and missing/damaged-provider negatives also
pass. These controls do not establish native writer coverage.
Before selection/allocation, independently checked Q31535's actual OWN paths against all731 current Q2 providers: intersection empty. Included Q3 launch client and input-wire observation bytes match retained1495 exactly. Published f017d680e explicitv2 validates the current primary and compatibility CPUs, all exact published provider authorities, actual generated caller references, and owning-load witness e65895936. No blanket repin, historical substitution, Q3/shared-provider edit or unrelated release gate was used. Q31535's release also arrived before allocation, but authorization used the owner's disjointness override. Exact predecessor bx_rup3afnj UUID fcb86e70-6cdf-4166-8a5c-c03951aa45fc was directly confirmed API ARCHIVED under completed unforced stop_4f9d8efe9188c04c, with retained124/124 physical drain.
Fresh immutable738-provider pins add only this run's setup inputs and preparer to the731-provider closure. All bytes were transferred and independently checked remotely. The actual staged-root seven-provider writer setup import and generated caller reference check passed before Chrome. Thus the1495 missing owning-load import is resolved. The two required flags were recorded: QUAKE2_NATIVE_WRITER_WITNESS=1 and QUAKE2_NATIVE_CUSTODY_VERSION=publishedf977ebf7c. A supplemental direct Node setup probe initially used the wrong cwd and refused the relative EXE read; it passed with the staged cwd. That corrected supplemental probe ran after launch and is not claimed as before-Chrome proof. A shell invocation continued after the supplemental failure; the required staged-root checker had already passed. Both command/result records are retained.
Box bx_tuwugvr3, UUID 9d26b631-36a4-4a44-810e-6bde1f6de795, was created with a finite25-minute lease and independently observable immutable UUID watchdog verified before creation. Initial expiry 14:58:52.886Z. Browser failure cleanup received close ACK, exit0 without signals, drained in1025ms. Kernel custody proves200 owned/200 actual reaps, no unresolved drain entries; ports40237/39031 closed, profile absent, no profile FD holders/input lock, runtime lock free. Actual nested parent waits retain separate stdout/stderr EOF. Caller-parent and supervisor receipts describe the same child. The Node command EOF is combined by the unchanged kernel owner; its separate EOF remains UNKNOWN. Browser drain is a distinct receipt, not inferred from reaps.
Fixture43 rows/41 unique contents and root45 rows/42 unique contents were compressed before transfer and independently SHA/size/gzip-CRC reread before delegated normal stop; zero invalid gzip artifacts. Proof commands were retained before wrappers. Stop stop_b9b9272e814d13bc completed unforced, error null, at 14:37:21.185Z; final exact-UUID API state ARCHIVED, archiveAfter null, final expiresAt NOT_RETURNED. Watchdog and lifecycle actually joined0 with separate EOF and released the runtime lock.
Other retained setup errors: the first local lifecycle wrapper incorrectly expected input readiness from the watchdog process; it was cancelled and fully joined before allocation, then replaced with the non-input wrapper. A cleanup cancel probe found no remote-child.json and sent no signal; the actual caller completed failure cleanup normally. None produced native cancellation proof.
Evidence: scratch/runs/20261109-quake2-staged-closure-gameplay-1575/.
Runtime Git base daa44c07c7c44d73d0b020758bdaccec495e81f7, exact relevant diff
and small owned-input binary patches provide recovery. No source-tree/media/
module evidence archive, main/local Chrome, agent, worker or public deployment.
Free/home remains above1.5GB. Fresh21 actual request contract cases, causal
browser-policy regression and required locked build pass. Earlier passing
primary/compatibility/cancellation/health controls were not unnecessarily
rerun. Native qualification remains false; all-writer, alias, peer/raw-host,
parse-generation, ABA and lifetime coverage remain UNKNOWN. Admission,
cancellation, signeddeath-1, health98, independent UP and sticky terminal
behavior are unchanged.
Next work requires a separately authorized exact published browser-policy
integration for the current CPU, with its actual prepare tested before a
new native attempt. Do not substitute the historical CPU or waive its hash.