Donuts published controls: fresh wave and ordinary Quit, 18 November 2026
One newly authorized registered dx_donuts original displayed LEVEL001,
accepted 21 personally reviewed finite gameplay gestures, and progressed from
one remaining fragment to a fresh wave of three red rings. The complete frames
fresh28.png, fresh32.png, fresh33.png and quitreview.png preserve that
change. LEVEL002 is inferred from the replacement wave; its numbered card was
not captured or personally read. This is stronger gameplay progress than the
previous run, but does not supply direct visual proof of the LEVEL002 numeral.
No particular shot, thrust or turn is credited with clearing the last fragment:
score and fragments also changed between gestures and during respawn.
Evidence: scratch/runs/20261118-donuts-published-control-level1-clear/.
The run reused the successful immutable launch recipe, published95997 controller,
canonical module eb2395e1c115980dd78dbb646a26f755a4119a2a1e086942e715240e07c34bc6,
and sealed source37118 (containing95997). The original EXE and 37 accompanying
files remained unchanged, with presentCap60 and normal guest Worker. Exact
source/module loads match the sealed inventory across main and both Workers.
Native renderer preflight and all preparation preceded the fixed 600-second
clock. The earlier eight compiled-native boundary cases, locked build and
personal workflow proof were reused without qualification reruns.
Each new intention followed manual review of its actual whole frame. Seven expired local reviews produced NOT_SENT; fresh captures then supported new intentions while the same scope remained healthy. Finite holds stayed within 40–1000 ms. Native consumption retained five-second gameplay freshness, confirmation500ms, independent UP1750ms and operation3000ms. The fixed180-second Quit reserve was unchanged. No macro, timestamp adjustment, score/level edit, deadline extension, rebind or replay was used. One duplicate review-file refusal occurred before Enter delivery; a new actual capture was used instead. A black title capture was described as black, with finite Enter following the actual previously observed title's documented Begin Play route.
Ordinary Escape consumed through native owner USER return and the exact native process exited0 with actual wait, both EOFs and no host cancellation. Final UP is OWNER_EXITED / unacknowledged, never an ACK. No endpoint request or capture followed terminal closure. The native watchdog and containment owner also actually exited0; the invoking launch tool actually waited0. All26 known owned native/watchdog/release PIDs were nonlive, the loopback listener was absent and owned frozen descriptors were closed. The independent disk watchdog sampled a minimum2,222,231,552 free bytes, above the1.5GB floor; no RAM gate was used.
Shared source/controllers were read-only. The only helper change was run-local:
exit the command wrapper after its awaited controller operation to avoid idle
HTTP keepalive delaying return. The controller still awaited native receipts and
independent release itself. Actual DirectDraw/raster output supplies no GL
backend proof. No boxes, workers, Python, Wine, deployment, source archives or
media copies were created. Box ID/state/expiry/stop receipt are respectively
null/NOT_CREATED/null/null. Selected named whole PNGs, exact Git/relevant patches,
module, media hashes and actual waits remain; result.json is published last.