Recoil selected provider generation, 2026-11-08

Run: scratch/runs/20261108-recoil-generation-ready/.

tools/native-runtime-generation.py constructs an explicit selected generation from an immutable historical manifest. Every replacement identifies the complete old row and exact current physical bytes. It refuses a changed historical manifest, changed current bytes, duplicate paths, historical-provider substitution, and changes to the protected original provider prefix. The normal production provisioner and content barriers consume the result; there is no alternate provision or runtime branch.

The predecessor 947-row manifest and its complete historical 916-row prefix remain unchanged in their original recovery paths. All original 851 provider rows remain verbatim in the new selection, including the original game source/media providers. The selected checker changes explicitly from 99cd56de… to current 43f27bb4…; its old/new rows and historical manifest SHA-256 are recorded in selectedGeneration. Only the declared 29 small run-specific helpers are relocated. No source tree or media archive is created.

Initial validation resolves every selected provider through the actual tools/native-runtime-provision.py normal entry. All 976 providers pass; 977 callback uploads join before verification. This is a local preallocation provider check, not a remote publication claim. A separate production integration test executes actual content publication, checks queue and parent barriers, rejects a same-size provider mutation before parent consumption, and joins all uploads on a causal transfer failure without publication.

Eight focused generation tests, eight existing provisioning tests, eleven existing startup-barrier tests, and the locked full build pass. All 2,371 accepted evidence references (705,157,488 bytes) independently hash-match in place, including the accepted clock/watchdog live tests and 19 lifecycle / 46 gate / 28 owner / 41 HTTP / 197 kernel-task evidence. Unchanged Chrome fixtures are not rerun.

The inherited Recoil launcher still referenced the old private recoil-software-utf8/local-supervisor.py. The selected helper integration replaces that active launch path with the shared kernel supervisor around the outer custodian, retains Recoil's queue/admission fences and sticky UNKNOWN/no replay, and uses the published bounded browser endpoint helper. Historical supervisor bytes remain as recovery providers. Kernel tools are owned and repaired by the separate Darkstone worker and are not edited here. No new runtime may use unpublished kernel bytes.

The integrated selection has 979 providers and 29 relocated helpers. It consumes exact published kernel repair 551b7bdc8762a915fc35e67b245867845ae55da0 and the unchanged endpoint helper from b3377657b. All current tool bytes match that published Git generation. The actual hermetic preloader and decoder pass without fixture mode or a Chrome fixture rerun.

On newly allocated bx_a83xxze6, the observable independent 25-minute normal-stop watchdog is armed before create. The UUID is durably recorded before the only create request; the box ID and actual expiry are recorded before runtime. lifecycle.json freezes browser deadline 16:26:34.233Z and outer stop deadline 16:28:04.233Z, earlier than initial expiry 2026-11-08T16:29:04.424Z. Remote bootstrap validates and joins the five exact custodian/kernel/reaper inputs before fork. The shared kernel supervisor arms before the lock-holding orphan-adopting custodian. The local heavy runtime lock is never acquired: the heavy runtime is remote.

Actual normal provisioning succeeds: 980 uploads join, then the ordinary production barrier content-verifies all 979 selected providers and publishes staging-verified.json. actual-content-publication.json independently records the matching receipt before queue creation. The actual queue rechecks it; the actual parent rechecks content and validates the full startup contract before atomic request consumption. startup-admission.json reports 979 exact providers. The independent driver/Chrome watchdog is prearmed and binds exact live identities. There is one runtime launch attempt, without replay.

The Software gate is still not original-validated. The first new runtime failure occurs before the original page is navigated, during the first independent clock census. The producer uses its existing two-second execFile timeout. Actual journal custody identifies census process 6781, parent driver 5958; thread 6812, start15111, TGID6781, is autoattached and parked awaiting lineage. The thread's EXIT message proves SIGTERM termination; the existing producer timeout is the inferred sender, which the journal does not record. Its parent's peeked clone stop is superseded at consume by an exit stop; the thread subsequently reaches kernel EXIT with message15. At sequence1075, published551b7bdc8 refuses unlinked non-SIGKILL exit, 6812, 15. This is a new actual SIGTERM case, distinct from the kernel worker's accepted SIGKILL reproduction. The analysis distinguishes observed kernel rows from causal inference; no missing parent lineage is invented. first-new-causal-failure.json retains the exact rows and source/journal hashes. Kernel tools are not edited here and no runtime is replayed.

The kernel exception initiates SIGKILL/EXITKILL failure retirement. Its retained kernel-drain.json has exitNULL, 127 owned tasks, 88 remaining at the failure snapshot, incomplete kernel fork lineage and explicit unresolved rows. This is not successful normal runtime drain. A later independent audit finds all 128 recorded task/supervisor PID/start identities absent, both ports34565/42573 closed, runtime lock free, writer absent, and no unrelated process cmdline/FD references to this runtime. Exact audit observer ancestry is disclosed. Only after that audit is the owned residual Chrome profile removed. No command/input was issued and no guest page, loadFiles, native Resume, Software arm, qualified M, or movement was reached. No health, active-game time, rendererWASM, audio or FPS claim is made; startup time is separate from active time, which was not entered. CLONE_UNTRACED/nonleader-exec and unresolved-lineage limits remain explicit.

All 33 unique remote outputs, 10,393,062 bytes, are individually retrieved and independently reopened/hash-verified before stop. The second inventory references unchanged previously retrieved files instead of duplicating logs or media. The outer watchdog's delegated normal API stop succeeds: box ARCHIVED, current expiryNULL, stop receipt stop_8ab30cb50615e3ba, completed 2026-11-08T16:06:14.336Z, forcedFALSE, errorNULL. Both local lifecycle roles exit0, their exact PID/start identities and supervisor are absent, and the supervisor has no children remaining. The remote pair watchdog was killed by the failed kernel supervisor; its bound identities/config/events are retained without claiming an early terminal pair receipt.

The task completes substantive generation integration and actual provisioning/barrier proof, with the new runtime refusal preserved. Next is a separately assigned causal repair for legitimate SIGTERM exit retirement under kernel custody, followed by one freshly authorized original attempt. Keep the selected checker/helper generation and shared supervisor/endpoint integration; do not revert to the immutable historical pins. Personally review CURRENT Resume before any native click, qualify actual Software before/after with complete uncached responses/refusals and current owner/PNG/epoch/clock/changed-timer/lifecycle fences, then review ordinary M before bounded movement. Full27, parity, audio and FPS remain open.

Recovery records exact Git SHA plus only relevant owned binary diff and small owned patches. Original decoder/compositor providers remain 204938B / f468ffce84da0f517df009682c111bbcb955b67f8b5a122350abbe5abc49e1d8 and 227919B / cb21daaf7c0ce2b2cf80436c192bda4ed78930b1b07eaf21a20eb9adb7ce7b51. Historical manifests, accepted media paths/hashes and accepted evidence remain in place. No source/media archive, peer WIP, old-box resume/delete, public deployment or subworker is used. Initial setup-only missing shim/parser-shape/unsupported-help failures are retained separately and have zero runtime effects.