Shadow Man defaults saved and Spielen enabled; ordinary exit reaches NULL

Historical source last updated, 2026-10-23. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.

The bounded report (historical artifact: ../../scratch/runs/20261023-shadow-man-settings-observer-repair-runtime/REPORT.md) records one actual47.40s Configuration/defaultsOK session on prepared bx_fn7pn7yg. OK wrote a genuine50-byte Grafix.Cfg (SHA2560407969d4bf39f2287f8d99bd37feac1212e6492f41038a817f77f39ef79d42d) and produced a new launcher with Spielen actually enabled. Three genuine images were visually reviewed. Ordinary Beenden then reached [eip-zero] guest called through NULL at batch2578996. External watchdog reaped PG54631, OS-9, no guest ExitProcess. Stop at first blocker: reopening/persistence, Play dispatch, game launch and input remain UNTESTED. The partial479-file save-vfs export is incomplete.

Runtime source58e90870, docs successor mainbb9c496e, canonical1879387B module ccd5b0a8e4fcb84d06bf539c8a4af28b377472072f3422750122048e9339f553 was actually consumed/instantiated under no-default-build guard. All2083 originals, 224 staged entries and the one2045-file clone/registry remained unchanged/readonly at handback. ONE existing896MiB tmpfs/ONE existing clone only; no restore/build. Both ABANDONED callbacks retain their limits. No parity/gameplay qualification.