Redline current CPU startup admission

The retained production startup caller and page admission selected historical a320d4c8… (2,185,596 bytes), while the explicit current publication preparer staged primary 3e491c0840bb7771328738a0d160b4bbaa3d7ab72074cbd38a7b41e5d7e8ec18 (2,186,068 bytes). This refused the authentic current module before guest entry.

redline-startup-3e491c08-v1 explicitly selects the primary CPU from published 5c8780318afbbe0e5a4e7c64190f2e0abde21cd0. The existing publication validator checks that commit's compiler/source closure, published provider ancestry, shipped CPU hashes and lengths. The new mode replaces only the declared admission pin and adds the Redline policy/adapter; unrelated drift still refuses. The historical pinset is never rewritten. No compat-module substitution occurs.

Prepare offline with a fresh task-owned destination:

node tools/redline-current-module.cjs --prepare FRESH_RUN \
  --publication-version redline-current-publication-daa44c07c-v1 \
  --startup-version redline-startup-3e491c08-v1

The selector is sealed into runtime metadata, the generated caller and its closure digest, outer launch arguments, retained startup adapter, and page install. Actual imports remain relative to the staged tree. Missing/changed providers or mismatching version selections refuse before outer spawn. The adapter composes the existing startup caller instead of introducing another admission algorithm. Omitted startup version retains the historical selection; old frozen preparation versions still refuse unexpected provider drift.

The shared admission edit was made only after Q31585's final published release 8b91cbbc0836843d541e66da29549eaf6b5b91ab at 14:59:47Z. Its exact 937-pin manifest included the old admission SHA afcb3bae…. Runtime release had separately reported UUID 3021654f-2102-4663-8572-3abf38268617 archived and physical drain. The candidate passed real current CPU compilation, owning-host admission and production preparer/generated-import controls in memory before that edit. Q2 files, CPU/WAT, host, guest-worker and custody implementations were untouched.

Evidence: scratch/runs/20261109-redline-current-startup-admission-1615/. It records exact Git base plus small owned patches, real shipped CPU identity, WebCrypto/native WebAssembly compilation and actual host init with inert Worker transport and guest entry. Historical caller refusal/current caller success, wrong version/hash/size, missing provider, changed owner/endpoint/module, duplicate compile/release, deadline, sticky failure, default parity and terminal no-input/no-capture controls are exercised. CLI and outer custody tests use DRIVER_PREFLIGHT=1, returning before server/browser creation. Independent finite watchdogs record actual child wait and separate stdout/stderr EOF. Completed own journals are losslessly compressed with SHA/size recovery recipes.

The 20-second admission ceiling, 18.5-second caller cap, immutable browser lifecycle deadline, first-failure behavior and input implementation remain as shipped. Successful offline admission is not native readiness. Browser wait/EOF, native input, cancellation completeness and gameplay remain UNKNOWN. No box, browser, local Chrome, native game attempt, worker or agent was created.