ReVolt loading readiness and atomic operator publication — 2026-11-18

Manual acceleration/steering, visible driving/checkpoint consequence and ordinary Quit remain unverified. Two distinct bounded scopes closed permanently UNKNOWN; neither was reopened. Evidence is scratch/runs/20261118-revolt-loading-readiness-manual-driving/, with selected whole images, offline-audit.json, actualwaits/, nativeexit/, recovery/, and result.json written last.

Both scopes actually executed published tools/revolt-startup-readiness.cjs through the predecessor's sealed startup adapter. This was runtime startup observation, not merely an archived repair. The first scope encountered automatic intro2.bmp/intro3.bmp waits, discarded its first capture candidate when loading raced it, then admitted an unobstructed fresh candidate. The second scope also completed startup admission. Actual Chrome arguments include the published UTC switch from 8fd08ea3b; no BetterChromium network-probe workaround or deadline extension was added. Strict action visibility, live owner checks, final-wire ordering, independent release and physical UP0 remained unchanged.

The first scope reached the Options menu and highlighted Controller Settings through ordinary keyboard navigation. At 13:02:26.669 UTC its consumer read a command file before publication completed and JSON parsing failed. The affected Enter was not delivered. The final file is valid JSON; the precise bytes of the failing read were not retained, so empty versus partial JSON at that boundary is UNKNOWN. There were 154 requests and six menu DOWNs, each with matching independent neutral release; zero requests followed closure. No bindings, manual race or driving were observed.

tools/revolt-operator-command.cjs, published as 5e4e89fc9, replaces that writer with the existing atomic-command-publication.js publisher: write/fsync/close a private temporary file, then exclusively link the complete immutable record into the watched name. Permanent UNKNOWN refuses further publication. Six focused tests pass, including the legacy empty-file reproduction, paused atomic writer, concurrent publishers, duplicate refusal and operator closure handling. The required locked build passes with actual exit 0 and both pipe EOF receipts. The author committed and immediately strictly pulled/pushed the fix, then exercised it in a new bounded scope; no inherited one-scope restriction prevented that materially changed acceptance.

The new scope actually used the published operator for eight complete command records. Two menu DOWNs have matching independent UP0 receipts. A later Enter operation expired its 30-second review before release arm and was locally NOT_SENT; no freshness limit was waived. The next whole frame showed ReVolt loading after idle navigation, not a manually selected race or evidence of driving. At 13:08:43.430 UTC the shared disk boundary closed LOW with 1,498,927,104 bytes free. There were 87 requests and zero after closure. No unchanged retry, later endpoint request or ordinary Quit followed. The separate watchdog's sampled minimum, 1,500,442,624 bytes, does not override that lower connection-boundary observation.

The served browser JS graph is exactly Git 9871a43a7610c98bdea9713a3f3432a3dd1254ce. The reused served module remains SHA-256 a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8, 2,418,710 bytes, with verified compiler-source recovery f6962ba5b1cf2829a66f5cc4d80b293c30719b37. The code-fix build was not served. Actual executing child module/roles remain UNKNOWN; optional child Runtime/Debugger queries were omitted. Existing qualifications, final-wire/release ordering and all 463 media pins were reused; all pins still match. Git manifests and relevant binary diffs distinguish the served graph from shared foreign WIP.

The two browser scopes retain 22 actual nested wait/EOF receipts; all 72 recorded assigned PIDs are absent, both supervisors report no leak, and owned profile/display/auth paths are removed. The required build and board-child waits are separate. The first outer tool returned 143 without an outer EOF receipt; the second returned 1. Direct-driver separate EOF remains UNKNOWN because native supervision inherited its pipes. Browser exits 0 are host cleanup, not native guest Quit. Full-task disk compliance is false. Only owned outputs were reduced: selected PNG recompression verifies identical decoded pixels; closed logs are compressed, and duplicate encoded image payloads are replaced with decoded hashes/lengths. Raw protocol reconstruction is not claimed for those omissions.

No workers, agents, boxes, Python, Wine, deployment, forced focus, guest polling/clock, config/save/state/media changes, solver or autoplay shortcut were used. Foreign WIP, shared helper ownership and held inputs were untouched. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Ownership is released after publication and evidence sealing; this worker stops.