ReVolt first-driving attempt and startup observation repair — 2026-11-18

Actual driving and ordinary Quit remain unverified. The sole original closed UNKNOWN during startup, before any command or DOWN. Unlike the preceding successful manual-menu run, this attempt identified the obstructing element: the ordinary wa-launch wa-game-wait dialog was loading intro2.bmp. The earlier unnamed DIV's historical identity remains unknown; this new observation does not retrospectively identify it.

Evidence: scratch/runs/20261118-revolt-manual-race-first-driving-consequence/, with RECOVERY.md and result.json sealed last. The predecessor's result/recovery were read. No predecessor scope was reopened, and this original was never replayed or contacted after closure.

The first startup visibility observation passed. A whole frame then showed black output and ordinary launch logs. Before the next startup capture, the strict identity reader encountered a painted DIV with class wa-launch wa-game-wait, role dialog, data-wine-page-dialog=1, a visible progress bar, hidden Retry/Quit buttons, and “Loading will continue automatically.” Its status was intro2.bmp — 1.0 MB of 2.0 MB. lib/game-wait.js creates this dialog for ordinary lazy game-data waits, reveals it after 500 ms, and hides it automatically after the episode ends. There is no evidence of a stuck game fetch or production visibility defect.

The operator erroneously treated this normal startup transition as an unexpected obstruction. Closure occurred at 12:44:01.919 UTC; UNKNOWN followed at .920. All 42 ordinary requests precede both boundaries. Zero navigation/driving DOWNs, command files, manual race entry, binding inspection, speed/course/checkpoint consequence or ordinary Quit occurred. Browser exit during host cleanup is not native guest Quit. The earlier whole screenshot does not itself show the later dialog.

tools/revolt-startup-readiness.cjs repairs passive startup candidate selection. Only a visible production game-data wait with its live controller in waiting state, expected DOM marker/class/role, progress bar, automatic continuation text and no visible action buttons can wait. An obscured candidate is discarded, and a new candidate must pass the same owner and unobstructed-output checks before admission. Download errors, foreign obstructions, owner replacement, transport failure and the original finite deadline still refuse. Input admission, live identity, current-pixel validation, independent release/physical UP0 and driving freshness are unchanged. No dialog is hidden, removed, clicked or restyled by the helper.

The run-local startup-adapter.cjs wires the helper into the two initial startup captures and the pre-admission observation loop; later action captures retain strict identity. Its exact replacement sites and generated syntax pass. This adapter was prepared after the original had closed and was not executed against that original. The helper is tested, but a repaired original startup and gameplay acceptance remain unverified because the permanent UNKNOWN boundary forbids another original in this task.

Focused native tests pass for recognized waits, a mid-capture wait, discarded candidates, actual error propagation, error/foreign obstruction rejection, owner replacement and finite expiry. A separate supervised Chrome DOM fixture uses the production GameWait controller/view: normal delayed reveal, automatic hide, a wait appearing during a capture candidate, and rejection of a failed fetch all pass. This fixture uses authored page-owner snapshots; it is not a guest/native ReVolt run or full admission-reader browser qualification. Chrome exits 0 with actual pipe EOF receipts and no supervisor leaks. The canonical locked build and exact test results are retained in the run; its rebuilt shared-tree module was not served to the original.

The first locked build ended with outer tool status 143 during WAT compilation; its incomplete log is retained and it is not a pass. A separate finite supervised retry records the actual build exit and both pipe EOF flags. The evidence distinguishes this build supervision from both the original browser and the authored DOM fixture.

The original served the coherent published JS graph 1c56d4135c03ee060c25cabcea031810f4f5f8dc and existing a600 module (a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8, 2,418,710 bytes), whose verified compiler-source recovery is f6962ba5b1cf2829a66f5cc4d80b293c30719b37. All 463 media pins match before and after. No module/media/source-tree copy was made. Actual executing wasm and child roles remain UNKNOWN; optional child Runtime/Debugger was omitted. Git-backed memory loading excludes shared foreign WIP, recorded as binary diffs. Published tmpfs/component helpers were reused; shared common/LMarbles files were left to their owner.

Prelaunch disk breached the required floor while other owners' activity continued. Before creating any scope, the inherited extra 20 MB reserve was removed to follow the owner's sole resource rule, actual free disk strictly above 1.5 GB. A subsequent floor crossing during helper preparation refused locally before disk initialization, supervision or browser creation; its waits are retained separately. Natural recovery admitted exactly one original. Runtime watchdog minimum was 1,512,230,912 bytes; it closed for the DOM assertion, not disk. Full-task disk compliance is not claimed. The separate shared-writer sampler was not duplicated or changed, and no foreign cleanup or RAM gate was used.

Actual original supervision, enclosing launcher/invoker, browser, display and watchdog waits have pipe EOF receipts; recorded owned PIDs are absent and profiles/display/auth are removed. Direct-driver separate EOF remains UNKNOWN because its pipes were inherited by native supervision. Recovery records exact Git, relevant binary diffs, owned input patches, selected whole images, verified lossless compressed logs and actual waits. No agents, workers, boxes, Python, Wine, deployment, foreign WIP or held inputs were used or changed. Box ID null, state NOT_CREATED, expiry null, stop receipt null. Ownership is released and this worker stops after publication and sealing.

The locked build retry completed with exit 0 and both pipe EOF receipts. The separate lifetime sampler's outer tool ended 143 without its summary or board-child wait receipt. Both recorded PIDs are absent; their individual waits/EOF and the lifetime minimum remain UNKNOWN. A later finite board watcher cannot reconstruct that missing interval.