Enigma authentic single-frame startup: blocked before guest
Historical source last updated, 2026-10-24. Runtime and implementation claims below describe that dated source; see current app notes and source for subsequent changes.
No guest was launched and no PNG exists. The first launch-compatibility failure is the unchanged accepted supervisor's RLIMIT_FSIZE=(131072,131072). It applies to all Node-created regular files, including the actual intercepted fs.writeFileSync PNG, rather than just output.log. The accepted named single-frame encoder permits2097152bytes, cumulative2097152/max1. The previous authentic batch30000 frame exhausted both strategies3 then0 at131072; its exact larger size and pixels remain unknown. A different deterministic startup is not presumed to have the same pixels, but the launch cannot support its full accepted capture contract.
A bounded generic-byte, non-guest kernel probe with that exact hard/soft limit wrote only131072 of131073 requested bytes; the next write returned errno27 EFBIG. Fixture removed after measurement and child waited/reaped. The actual guest was stopped at compatibility admission, rather than knowingly invoking a writer whose accepted profile exceeds its inherited hard file limit. No supervisor/guard semantics were repaired or weakened. The accepted supervisor's terminal validator also requires ERR_ASSERTION, whereas a writer EFBIG preserves its native error identity; no claim is made about a guest failure path that was never executed.
Planned environment explicitly ENIGMA_CAPTURE_PROFILE=single-frame, ENIGMA_LOSSLESS_CAPTURE=1, ENIGMA_TERMINAL_CAPTURE_INSTALL=1 and actual ROOT/CAPTURE_PATH/TERMINAL_RECEIPT retained in next-env.json.gz; FTQ then original capture, --quiet-fs, first and only PNG30000 at640x480, max10000000/55s. No capture-directed early termination change. The actual filename-bearing mount argv passed the unchanged canonical parser before checkout: supported vfs-tree, zero vfs-mount, eight dependency-ordered providers,2460 intended files including comma-bearing names in the standing full2659-entry manifest. Remote full closure rehash, ordinary-user probe and real-dependency preflight were NOT reached because staging was halted at the compatibility discovery. No claim of runtime readiness.
All artifacts/recipes are adjacent, sealed by artifact-seals.json. Originals/providers/assets remain standing read-only inputs identified in manifest.json.gz; no copied full local assets. Scene, menu, Lua and gameplay remain UNKNOWN; this is neither packed-original nor gameplay acceptance. ops/result.json is published last outside Git after push verification.