Enigma bounded single-frame profile: implementation and resource blocker

Implemented on immutable base 2545fba6c8234031bc8fbdcb5273491cbc4461ca. Explicit ENIGMA_CAPTURE_PROFILE=single-frame requires the existing ENIGMA_LOSSLESS_CAPTURE=1 and terminal adapter install. Only default and single-frame names are accepted; arbitrary numbers, objects, unknown/prototype names, empty and padded environment values reject. Default retains single131072/cumulative393216/max3. Single-frame is single2097152/cumulative2097152/max1. Dimensions remain800x600/480000 pixels, input at most2097152, RGBA8 and exact decode/re-encode byte comparison, two level9 strategies3 then0 maximum.

The actual Module._compile transformation of the unchanged pinned capture source injects the named encoder selection and both writer checks. Encoder size failure preserves the AssertionError and adds only at most two numeric candidate lengths to bounded durable rejection metadata. Rejected PNG buffers are not attached to this diagnostic. The first terminal failure latches identity; artifactAccepted remains false and later writes cannot proceed. Supervisor accepts only the relevant allowlisted assertion messages for the new profile and keeps strict legacy behavior; EIO and unrelated assertions fail validation instead of being classified as ordinary byte-limit receipts.

The real standing pinned pngjs and pinned raster canvas produce a high-entropy640x480 RGBA8 PNG1229723B, varying alpha included, pixelSHA256 74b2c7a51f2225f3bc2b52ffa997cedcc5d6815238aac182f0451a655512ab6f. The new profile accepts an output above131072 with exact pixels/dimensions; default rejects after actual strategies3,0. Tests execute actual preload install, Module._compile and fs writer. They cover second-frame rejection, cumulative state injection at prior2097152, dimension/malformed/CRC/data corruption, pixel change, EIO identity, durable artifactAcceptedfalse and no later write. Removing profile flow, frame check, cumulative check or pixel validation makes the same acceptance assertions reject the mutants. Cumulative-only overflow is unreachable from zero under max1 and the per-frame cap, so its existing exact check is exercised with explicit prior-state injection.

All five focused suites passed under Node heap256/CPU60/wall60 and fresh memory admission. After the final supervisor allowlist adjustment, terminal and complete supervisor suites passed again; the latter runs the final new profile suite and feeds its actual default/frame/cumulative receipts into the full historical transformed supervisor try/finally through EOF, unchanged stop function, exit1 and shell AND dependent absent. Historical unrelated outcomes and the old transformation oracle remain checked. No full build, guest, native instantiation, box operation, acquisition, deploy or merge occurred. No assigned box; coordinator owns lifecycle.

Historical guest 7526174ea2c6edb0180e4977a07680efa6def158 exhausted strategies3,0 at batch30000 with no pixels retained. That evidence did NOT pass, and prior synthetic fit never proved authentic fit. Its charges/rejection receipts remain in its immutable branch and /tmp/enigma-recovered-lossless-startup-oct24; this task did not reset or edit them. Authentic fit under the new profile remains UNKNOWN and no second runtime is authorized here.

Publication is BLOCKED by this worker's actual resource breach. The initial resource projection passed, but git read-tree REV followed by git checkout-index -a materialized9971 unintended files438716226B outside the explicit NONCONE selection. Detection measured440418438B task-owned files, exceeding67108864. This mistake was not a guard allowance change: dependent work/publication stopped at detection. All unintended owned copies were removed, leaving about1.7MiB; git sparse-checkout reapply repaired skip-worktree bookkeeping. Root/donors remained read-only. The original failure and cleanup receipts are retained. Future recovery should use sparse-aware git read-tree -mu REV, never checkout-index -a; independent coordinator resolution and fresh admission are required before further dependent execution/publication. No retry of denied operation occurred. Git also reports a pre-existing deep alternate-store chain warning; no donor objects were edited or repacked.

A first test-launch ENOENT was due to an absent task TMPDIR; its output was retained, the directory created, and the affected tests passed. No substantive assertion failure was suppressed. Evidence adjacent includes this initial failure, passing receipts, resource admission, first actual resource rejection and cleanup. Local WIP is preserved for recovery; there is NO remote backup from this worker and NO main merge. Completion/independent acceptance belongs to a fresh coordinator-assigned worker.