Q2 current-policy caller repair and queued native fixture
Evidence: scratch/runs/20261109-quake2-current-policy-guard-door-1645/.
The actual production preparation and full consumer preflight now accept the published current browser policy through the real caller. No native fixture or original gameplay attempt ran: the required Redline1635 release is absent. Guard defeat and onward-door progress remain unverified.
The initial production CLI accepted all 735 providers with module
quake2-1495-published-5c8780318-writer-e5eff70be-f977ebf7c-v2-browser-1605-v1
and policy quake2-current-primary-3e491c08-v1. Deeper caller preflight found
two prerequisites that preparation alone did not exercise:
quake2-native-launch-client.pyunconditionally selected the historical composition, conflicting with the required current-policy preload.- The input-wire install gate accepted only that historical environment.
Implementation d0ecba843c8bb7fd6a1fc5eac1c727c28fb37923 adds the exact
explicit browser-policy route to the actual remote parent and wire install
gate, rejects mixed preloads and wrong policies, and updates the composition's
exact tested caller digest. Default caller selection is preserved.
e469112762c9a0f6a4d33045a860d4d582dcb4d6 binds only those three repaired
providers to that published authority in the explicit browser preparer.
Historical module validation still refuses changed providers. Both commits
were pulled and pushed successfully on main.
The CPU identities remain primary
3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18
and staged compatibility
ecb45716b1ee7fc5218b1670dd270b19c7664ee30d000b3360a12786a1c21eaf.
Browser selection remains primary only. Canonical EXE, owning Worker, slot0,
native writes, physical admission, source lifetime and deadlines are unchanged.
There is no historical CPU substitution, broad repin or hash waiver.
Before editing, the actual Q2 manifest had no intersection with Q3's owned 1625 paths. The exact active Redline1635 903-provider manifest also contains none of the four repaired production provider paths. Q3's later 1655 ownership is disjoint. No foreign source or runtime was changed or frozen. The five owned code/test paths were released after publication; only this run and note remained owned while preparing the handoff.
Validation passed: the real production CLI; full declared writer import closure including owning-load witness; actual composed consumer with policy, health, native-fixture launch and wire hooks, stopping before Chrome; real Node remote-parent selection regression; existing launcher/lifetime suites; 21 composed command/input/close cases; 21 actual request-budget cases; the wire suite's production provider controls and eight old/new protocol pairs; canonical EXE/current CPU WebCrypto and identical-object handoff controls; staged Git-free preload, wrong-version, damaged-provider and forged-repin controls; required locked builds.
The regression retains the old remote parent's exact mixed-preload failure and the current preflight success. Earlier runs exercised the actual kernel supervisor and waits. While Redline held the shared runtime lock, the complete caller-plus-wire regression used an explicit test-only outer-parent seam: the actual selected Node argv, preload and consumer ran and were waited with both pipe EOFs; that test makes no kernel custody claim. The full staged fixture preflight also passes with all 741 provisional providers. These are offline checks, not native endpoint or writer qualification.
Retained failed controls include initial missing test arguments, an authored baseline missing its current-policy preload, the reproduced wire-gate failure, and a kernel regression refused by Redline's shared lock. None counts as a pass. Empty/malformed artifacts never count as EOF or execution proof.
At 15:33:18 UTC, direct exact-UUID API inspection reported predecessor
bx_ncb2wqug, UUID 846740ce-e8a4-4e30-946a-249f07f89376, state idle,
archiveAfter=2026-11-09T15:43:11.205Z, stop=null, stoppedAt=null.
Its final published release and independently verified physical-drain receipt
were absent. This is the concrete allocation blocker, not a native failure.
The predecessor remains owned by its assigned worker and was not stopped.
This task's BoxID/state NOT_CREATED, UUID/expiry/stop receipt N/A. No final runtime pinset, lease plan or watchdog allocation was made; the immutable-UUID watchdog and staging inputs are prepared for a future run. Original launch still requires every existing fixture and cancellation gate; none was promoted from offline tests. No local Chrome, agent, worker or public deployment was launched.
Evidence recovery uses the exact Git base, a 12,738-byte owned code patch with successful reverse check, relevant uncommitted diff, and compressed small run-input patch. No source-tree, media or module archive was created. Completed owned evidence was losslessly compressed only after independent SHA/size and gzip checks, with recovery recipes retained. Free /home stayed above 1.5 GB throughout this task's observations.
nativeQualification=false; all-writers, aliases, peer/raw-host parse and ABA
remain UNKNOWN. Historical separate Node-command EOF remains UNKNOWN; the
earlier combined TRUE is a separate observation.
Next: after Redline1635's exact UUID is API ARCHIVED, physically drained and
finally published RELEASE STOP, reread those receipts, prepare fresh final
pins through quake2-staged-closure-gameplay.cjs, arm and observe an independent
25-minute UUID deadline before allocating one box, and run the authorized
bounded fixture. Preserve first-failure terminal behavior and retrieve/hash
verify unique compressed evidence before delegated normal shutdown. Original
guard/door gameplay is conditional on all existing gates actually passing.