GLTron software follow-up: disk closure before input

The single original reached the textured software main menu, but its disk guard permanently closed the scope at 2026-11-20T00:26:28.191Z after observing 1,519,476,736 free bytes. The subsequent host fullscreen click was refused locally before a command was written. No guest key-down, normal Space pause, manual turn, round outcome or ordinary Quit is proved. No original replay or later endpoint request followed closure. Evidence: scratch/runs/20261120-gltron-software-manual-turns-native-quit-20261120/result.json.

The served graph remains f6962ba5b1cf2829a66f5cc4d80b293c30719b37, with module SHA-256 a6002d5dbcfeb534a0eadd223da616e525aa1542dad2bde381fe54e00ee862f8. The worker verified all graph pins, independently recompiled that exact module, and verified all 92 media pins. Foreign shared-library changes, the headful-display WIP and the unproved readiness candidate were not adopted. The run uses the prior sealed operator, with a new raw-directory value and an exact recovery of its diagnostic-only module. The candidate startup expression remains unused. Independently executing child module bytes and roles remain unknown.

The personally inspected whole frame original/wholehost/consent-001.png shows the colored GLTron main menu and ordinary host fullscreen button. The actual original startup observations identify its software GL bridge with glRenderer=null and a native publication receipt. These observations establish startup only. The independently prearmed Mouse1 release fired at its original fallback deadline, before closure, with physical state zero; no DOWN was issued. That release is neither a guest binding proof nor a turn consequence.

The old authored native GL fixture file was unavailable. Its recorded Git recipe regenerated the exact 25,600-byte binary with SHA-256 7457bf52fe3a09c5a09afb28d1e1fc4f5cf176f6eab00a7c369ec3b2c4eb027d. The first fixture attempt ended before browser startup with ENOENT and retained actual waits. The second showed a white display despite seven native draws, with zero initialized-publication receipts, and closed at the same disk event. It provides no fresh qualification. The unchanged controls were explicitly reused from the prior admitted run under the owner's instruction; qualification.json records that historical provenance and does not classify either fresh fixture attempt as passing.

Native supervision, independent finite disk monitors, actual child waits and EOF receipts are retained. Owned browsers, private displays and profiles were cleaned up; host cleanup is not ordinary game Quit. The task monitor recorded a minimum of 815,222,784 free bytes, below the 1.5 GB floor, before its successful final join. The closure was not a full-duration capacity success. The shared disk writer is unidentified. No production code changed, so no repair, new focused native test result or locked build is claimed. No workers, Python, Wine, deployment or box lifecycle operation was used. Box ID, expiry and stop receipt are null; state is NOT_CREATED.