Enigma API single-frame startup: first storage rejection

No guest started; no PNG was produced. The fresh pre-guest resource gate rejected projected task storage 67,547,136 > 67,108,864 bytes, excess 438,272 bytes, at 2026-10-26T04:54:45Z. resource-ready.json and the original stage.log retain the first failure. No unchanged retry, build, acquisition, semantic repair, second guest, packed-original or gameplay acceptance occurred. Scene, menu and Lua behavior remain unknown.

Read-limit incidents are retained separately: initial combined recipe inspection returned11,071 code bytes, and the adapter's first155 lines comprised9,965 bytes, each exceeding the8,192-byte code-read limit. No retroactive compliance is claimed. These earlier operator inspection incidents are distinct from the first actual execution-admission rejection below.

All 2659 manifest entries / 37,476,538 bytes were streamed directly from standing pinned sources to bx_7qwjxps7, then remotely rehashed successfully (cmd_b4yaosl0vtlp). Ordinary-user UID1000 preflight passed (cmd_2vbtmlwmytlv): actual runner dependency preamble, installed pngjs7.0.0 on Node v24.22.1, 28 font files, real codec/raster resolution and two cheap rejecting controls. The canonical parser and supported tree mount enumerated and verified all 2460 intended VFS files; no comma-bearing filenames were present. Eight providers retain their original dependency order. These are preflight results, not guest execution or actual-frame fit evidence.

Complete accepted supervisor/capture composition and helper siblings passed (cmd_hwzwztorpcsn): FTQ followed by the unchanged original capture, ENIGMA_TERMINAL_CAPTURE_INSTALL=1, lossless capture and named single-frame, 2MiB per-frame/cumulative artifact and maxFrames1, separate 131072-byte combined stdout/stderr guard, strategy3 then0 level9 and exact RGBA checks. The supervisor was transformed from the full pinned original; its main/termination logic was not replaced. Deployment-only box/deadline labels are recorded. Existing exact revision acceptance was reused; the six suites were not rerun.

The intended run retained --no-build, --quiet-fs, 640x480 fixed screen, 512MiB arena/heap, original trace/count/input settings, max10000000/55s and the sole PNG schedule at batch30000. The conditional heavy-flock launch recipe was never executed. Selected kernel limit/composition was verified statically against accepted code; no actual guest-child RLIMIT or execution status exists.

Immutable source donor: 44e344fdb26daab9a07210656597902ba27cb5f7. Staged historical module: SHA256 8fac39936b6df2418ad86cab118cef19a65a727f649fbc14c412b37818904686, 1,879,746 bytes, source b41a7c5f4b752d1f0bdab1141a11d4fed4dc6f9a, ABI291/layout9a3bc9149d58209c. Runner is revision d8cd8c54c8d63c107696f1e4ef7a1e229dcadc1e, SHA256 4d7b9587676db38fcf3314807acb2b2a42b5f09d2c98fcf3dccb8a6cde9e1809. Neither module nor guest was executed in this task. Full helper, original capture, supervisor and manifest hashes are in adjacent identity/dispatch receipts.

Failed-gate charges: local3,559,424; remote45,228,032; session/launcher905,216; positive SQLite highwater909,312; session/SQLite future2,097,152; checkout/Git future1,216,512; capture/publication4,194,304; transfer overlap1,048,576; reserve8,388,608 bytes. The remote manifest/helpers and full session/positive database growth are charged. Standing donors/executables are separately identified and not traversed as task copies. Local memory2,282,020,864 minus536,870,912 projected extra client passed the805,306,368 lightweight floor. Both host disk floors passed; allocation alone rejected. No fresh under-lock guest admission occurred. All prior charges and historical source, kernel EFBIG and capture failures remain retained FAILs.

Failure-only publication has its own bounded projection, removing unused future guest/PNG work without altering any incurred charges or the failed gate. Cleanup API cmd_xznrhvzdita1 found no owned guest Node process, guest directory or terminal receipt; no guest group required signaling/reaping. The local board watcher was TERM-reaped (143). No runtime SSH, resume or lifecycle operation ran. Box API info reports idle, health ok, reachable/running, expiry 2026-10-26T06:06:24.385Z. Leave it running; coordinator owns05:50UTC shutdown.

Evidence and separately retained original-recovery recipe: enigma-api-single-frame-startup-20261026/. The original failed projection is not acceptance, and publication does not authorize another guest attempt. No main merge.