ReVolt normal loading in unadmitted menu observations — 2026-11-18
The observer/capture integration is repaired and published in 8c4052149 and 0f00d8c01. A materially changed original reached the personally configured single-player race (PLAYER, RC Bandit, Toys in the Hood 1), with lap 1/3 and a stationary 0 mph car. Manual acceleration, steering, resulting course consequence and ordinary Quit remain unverified. The exact remaining blocker was the unchanged five-second gameplay review limit: three distinct newly reviewed Up1000ms intents arrived at ages 8,830, 5,985 and 5,756 ms, all before arm or DOWN. No expired action was replayed and no freshness deadline was extended.
Evidence: scratch/runs/20261118-revolt-menu-loading-candidate-driving/. The prior published-atomic note/result/recovery and startup helper were read; previous UNKNOWN scopes were never contacted.
tools/revolt-capture-integration.cjs connects the real native/browser operator to the production loading observer beyond initial startup. A candidate remains unadmitted until its whole-frame capture and both surrounding owner/visibility observations pass. Proven automatic game-data loading discards the candidate and permits natural observation inside the original finite deadline. Internal identity/display-proof samples use the same rule. A normal loading obstruction discovered by an input check returns local NOT_SENT; the old intent and review are consumed, and another action requires another whole-frame review and a new intent. Transport/query exceptions, wrong/error dialogs, owner replacement and actual UNKNOWN remain failures. Every possibly sent DOWN retains the existing independent matching release and closure machinery.
The loading classifier additionally checks output visibility while excluding only the one recognized wait subtree from the passive obstruction scan. It does not alter the DOM or hide the dialog; another painted obstruction alongside the wait is refused. The controller must be genuinely waiting, progress visible, action buttons hidden and automatic-continuation text present.
The first changed original exposed a missed integration point: read-only inspect still used strict input identity and closed UNKNOWN at 1795008968056 during normal loading, with zero DOWN. That scope stayed closed, with zero later requests. The second published fix makes diagnostics explicitly unadmitted observations and validates the second live-owner snapshot before input. Only then was a new original created. The earlier failure is retained, not reclassified as success.
Focused tests passed: real Chrome with production GameWait controller/DOM transitions, loading before and during whole-image capture, discard/review behavior, passive loading diagnostics, second-live-sample refusal, mixed foreign/error obstruction, owner change, deadline expiry, true UNKNOWN propagation and no later request after closure; existing startup readiness, atomic operator (two tests), and game-wait tests; exact real-operator adaptation/syntax. Both required locked builds passed. A focused native guest/browser integration verified old loading intent NOT_SENT before arm/DOWN, natural capture waiting, a fresh whole frame and a new trusted Down100ms with independent UP0/release wait. The fixture's unchanged blue image does not establish guest gameplay effect. No broad qualification campaign or runtime module compilation was repeated.
The final original used coherent published graph 0f00d8c0122baa038a8814381c6e5ebea18b09b3, the published atomic operator, current UTC/tmpfs browser handling, retained module a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8 (compiler source f6962ba5b1cf2829a66f5cc4d80b293c30719b37) and all 463 verified media pins. The module's HTTP response and 203 Git graph HTTP responses matched their pins; executing child module/roles remain UNKNOWN. Six personally selected finite Enter gestures, each with independent UP0, visibly traversed manual race setup and reached the course. No gameplay DOWN was sent. Selected named whole-frame screenshots retain front menu, setup summary, course arrival and the final stationary review; redundant images were removed with hashes recorded.
The final scope closed through explicit host cleanup at 1795009498111. This is not guest Quit. All three task scopes had zero requests after closure. There are 27 retained actual waits with both EOF receipts, 100 recorded runtime PIDs absent, three native supervisions reporting no leaks, and removed owned browser tmpfs/display-auth artifacts. Inner final launcher/supervisor/browser/display/watchdog waits completed successfully, but the final invoking tool returned 143 and its separate outer wait receipt is missing: that outer boundary remains UNKNOWN. The original's watchdog sampled minimum free disk was 1,509,179,392 bytes; sampled observations do not establish continuous lifetime compliance. No RAM gate or foreign cleanup was used.
Recovery records exact Git identities, relevant binary diffs, owned new-file patches, unique inputs, original helper pins and existing module/media recovery paths. Closed own logs were gzip-compressed only after verified byte-for-byte round trips. No source-tree archives, media copies, workers, sandboxes, Wine reference runs, deployment or foreign helper/WIP/hold changes were made. Box ID null; state NOT_CREATED; expiry null; stop receipt null. The worker releases ownership and stops after publishing result.json last.