Enigma quiet-filesystem diagnostic startup (2026-10-24)
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.
Exactly one authentic-unpacked startup got past the prior ordinary-filesystem output guard. Its first recorded fault was the unchanged PNG capture guard: capture byte limit at batch 30000. No PNG was written. The same attempt subsequently terminated at batch 44896 with host SyntaxError: Invalid regular expression: /^+index_user\.txt$/i: Nothing to repeat, at VirtualFS.findFirstFile (runner/lib/filesystem.js:1475), through fs_find_first_file:3116. This is a host filesystem exception, not an established guest missing API or fatal Lua-library request.
The pinned implementation translates dots, stars and question marks into a regular expression but leaves the leading literal + unescaped. The retained exact source excerpt and binding support that cause. EIP was 0x00b21bfa, stack return 0x00b21c0f. No semantic repair was made.
Observation and limits
The runner caught the PNG rejection and kept executing in this same attempt before the asynchronous supervisor detected a fault. Consequently this run does not satisfy immediate stop after capture rejection. The later filesystem crash is retained as subsequent terminal evidence, not substituted for the earlier capture failure. No second guest was launched, no guard was increased and no failed image was published. The inherited supervisor reads bounded output chunks on a timer; its first-observable-fault reason does not identify a particular matching log line. The preserved log establishes ordering.
Output was 56835 bytes, below the unchanged 131072-byte output guard. Ordinary [FS] read records are absent; other diagnostics remain visible, including FindFirst/FindNext records, the PNG rejection and full exception stack. The separate original capture preload remains byte-exact. The API cap remains 16 records, exhausted by early system/SDL-image/JPEG requests and the already loaded libpng provider. No exact Lua dynamic-loader entry/request/cache branch, safe string observation or counter totals were established. Four supported counters were armed, but the exception bypassed their final totals. API-only tracing remains the accepted narrower fallback. Lua/configuration/graphics/level-index file lookups and SDL window creation are observed; menu rendering and gameplay are unestablished.
Exact configuration and admission
Accepted main/donor 979042c93eec78095d0e4ee078d4efb25a55a5ff and all 32 accepted blobs were rehashed. Provider readiness/527 bindings and the accepted missing-SDL rejection were reused by sealed identity, without repeating completed logger or binding tests. All eight explicit providers remain: MSVCRT, zlib1, libpng12-0, SDL, SDL_image, SDL_mixer, libfreetype-6, SDL_ttf; authentic SDL_getenv export RVA37536 remains accepted. Optional native libraries were neither fabricated nor acquired.
guest-args.json, next-env.json, exact-config.json and command.json retain the exact accepted next-command structure: quiet-FS adapter require, separate original capture require, restored pinned canonical runner and filesystem under ENIGMA_RUNNER_ROOT, same providers/tree/input/counters/clock/batching. The full original packed tree was untouched; this was explicitly an unpacked diagnostic overlay. The complete streamed closure has 2659 files / 37476538 logical bytes. Actual canonical parser/tree enumeration revalidated all 2460 intended mappings/hashes (no comma-bearing names in this tree). The zero-byte data/enigma_conf.lua is present. No broad local asset-tree copy was created.
Module SHA256 8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686, source b41a7c5f4b752d1f0bdab1141a11d4fed4dc6f9a, ABI291/layout 9a3bc9149d58209c. Runner SHA256 4d7b9587676db38fcf3314807acb2b2a42b5f09d2c98fcf3dccb8a6cde9e1809; filesystem SHA256 4c255570c74512262849420c74fe73704fcfe006dc09fb963272c66c9ea0b27e. Unpacked EXE6287872B SHA256 5885e29ac9c1bdfe7f36e0d7fba76a56b74bc99558e1e6debf8425febe35fa45. Original asset manifest 74a65c35b0742c00f0a53f4590fe1c888715e6b59acae8f0349d1d98c1dbb574. The reused twenty input/output pins and full manifest preserve remaining identities.