Recoil independent launch clock and watchdog, 2026-11-08

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

The missing independent process/clock producer and launch watchdog are implemented and wired into the owned native driver and launcher. Live local Node/Chrome tests pass under the existing kernel custodian. No original Recoil, Resume click, M, movement or new box ran. The Software gate remains not original-validated.

tools/native-clock-process-proof.cjs starts a separate Node census for every verification, with a fresh challenge, producer byte hash, and a parent/child wall-clock bracket checked against monotonic elapsed time. It independently reads current Node/Chrome PID/start, executable, Linux boot, network/PID/mount/time namespaces, exact Chrome profile and its actual DevToolsActivePort endpoint. It resolves both the Node HTTP and Chrome loopback listeners to FDs owned by those exact processes, then repeats the process census. Complete successful proofs and refusals are retained durably. The child starts without inherited Node preload options.

This host's actual Chrome rewrites its command line into one space-separated process title. The first two tests retained the exact-argv rejection. The producer now accepts exactly one complete whitespace-delimited fixed argument, with no whitespace allowed in the expected argument. Profile suffixes or substring matches cannot qualify. The raw process title remains evidence.

The owned browser-position.cjs verifies the independent watchdog and census before creating its diagnostic chain and before Software installation. Its actual compound callback runs the independent verifier before and after each Software probe, including the compound's argument-free after-Resume calls. Retirement during that extra work, any expired source/copy/pixel timestamp, or the conservative immutable maximum five-second transition closes with sticky UNKNOWN/no replay. The existing gate still performs the actual browser Date.now bracket, six complete uncached source responses/refusals, colocated owner/PNG checks, changed-timer living pair, allSettled drain and lifecycle fences through final save. Native independent releases, hardware gate, and kernel supervisor source are unchanged.

tools/native-deadline-watchdog.cjs produces an exclusive lifecycle plan from the explicit newly allocated box ID, creation time and expiry. The final cap is the earlier of allocation plus 25 minutes and expiry; browser shutdown is 90 seconds earlier. Replanning or extending those times is refused. The launcher requires this plan and prearms a detached watchdog before its sole kernel-supervised runtime spawn. The driver requires observable PID/start and fresh fsynced heartbeats before Chrome startup, binds exact live driver/Chrome identities before CDP attachment, and requires the same watchdog at every clock check.

The independent watchdog freezes its configuration and target identities. Either wall time or monotonic elapsed time reaching the original deadline triggers exact PID/start SIGTERM, with SIGKILL fallback; rewriting a deadline or binding cannot extend it. Successful early termination requires both bound processes absent and their profile removed. Its terminal receipt explicitly covers only this pair/profile. Kernel descendant/adoption drain, endpoints, ports, writers, held input, evidence retrieval and hash verification, and the outer normal box-stop watchdog remain separate required custody checks. No box shutdown or exhaustive custody is inferred from a watchdog terminal file.

Validation used actual local Chrome on about:blank, with the local heavy-runtime lock and unchanged kernel custodian:

The initial combined watchdog test exposed a real existing kernel-supervisor waitid/waitpid nonterminal peek/consume mismatch during the second Chrome startup. It is retained in watchdog-kernel/custody.ndjson and watchdog-test.log, and was reported on the messageboard to the worker owning the promoted kernel module. The failed supervisor recorded 96 remaining tasks at its exit; a later independent PID/start audit found all recorded tasks absent. Successful individual controls have empty kernel drain receipts. No original is attempted with that unresolved supervisor failure. The old kernel source was not modified or replaced here.

The selected manifest preserves all 916 inherited rows verbatim, including the 886 prefix and original 851 providers, and appends 29 successor physical helpers plus two production modules: 947 rows total. Original decoder/compositor identities remain 204938 bytes / f468ffce84da0f517df009682c111bbcb955b67f8b5a122350abbe5abc49e1d8 and 227919 bytes / cb21daaf7c0ce2b2cf80436c192bda4ed78930b1b07eaf21a20eb9adb7ce7b51.

Provisioning is not ready. The actual mandatory production provisioner calls the current nested checker, then refuses the inherited tools/runtime_helper_closure.py provider: its pinned hash is 99cd56de…, while the current required checker is 43f27bb4…. The refusal occurs with zero uploads, zero publication and zero remote effects. No old checker bytes were silently substituted and no preserved row was rewritten. The first local preflight also had a missing local shim path; that setup failure is retained separately. The original 916-pin/917-mock-upload acceptance remains historical evidence, not a claim about this 947-row generation. Queue and parent content barriers are unchanged and not remotely exercised.

Next: explicitly reconcile the historical checker provider with the current selected generation while preserving original providers; integrate and qualify the kernel worker's repair; then prearm the outer box watchdog and make at most one original attempt. Personally review CURRENT Resume before clicking, qualify Software before/after, review ordinary M's consequence, and only then attempt bounded movement toward power control. Loading/MENU/active time and health/time limits remain separate. Full27, parity, audio and FPS remain open.

Recovery records exact Git SHA, relevant binary diff, small owned new-file/helper patches and existing media/provider hashes. No source/media archive or peer WIP is included. New box ID/state/expiry/stop receipt: N/A — none created. Old boxes were untouched. Local test profiles are removed after exact owned-PID absence; no input was held by these about:blank checks.