Enigma single-frame profile: independent acceptance

Independently reviewed candidate 754e9c9bd22e42b41ba6d607d29dd04db767d4b9, including final encoder, terminal adapter, single-frame and supervisor tests, original pinned capture source and implementation report. No production correction was needed. The candidate is remotely backed on task/enigma-single-frame-independent-closeout-oct24; conditional integration reconciles current main under the exclusive shared integration lock.

Only named default and single-frame profiles are accepted. Explicit single-frame requires lossless mode and flows through actual install, Module._compile, encoder and intercepted writer. Its per-frame/cumulative limits are 2097152/2097152 and max1; default remains 131072/393216/max3. Width800, height600, 480000pixels, non-interlaced RGBA8 and exact decoded pixel identity remain enforced; at most existing level9 strategies3 then0 are attempted. No quantization, resizing or alpha conversion is introduced.

Five relevant suites pass on the exact candidate tree: test-lossless-capture-png.js, test-enigma-lossless-independent.js, test-enigma-terminal-capture-guard.js, test-enigma-single-frame-profile.js and test-enigma-supervisor-exit.py. They verify original source and real installed pngjs pins. The real high-entropy640x480 input is1229723bytes, exceeds default128KiB, passes explicit single-frame with exact pixels including alpha and rejects default after two attempts. Invalid profiles/dimensions, malformed PNG/CRC/data, pixel mutation, writer EIO object identity, durable artifactAcceptedfalse and blocked subsequent writes are covered. The full historical transformed supervisor try/finally through EOF runs against fake OS child/group interfaces with real receipt and shell I/O; actual default/frame/cumulative receipts yield shell exit1 and AND-dependent absence. The unchanged stop function and unrelated error behavior remain checked. This is offline acceptance, not a guest execution.

Additional independent preload mutations alter the final deployed capture source at its last compile boundary, rather than the transform implementation: maxFrames1->2 and cumulative2MiB->4MiB both fail the original acceptance assertions. The first mutant hits cumulative rejection instead of the required frame rejection, which correctly fails the exact error oracle. Cumulative-only overflow is unreachable from zero under the one-frame and per-frame invariant; explicit prior-accounting injection exercises that defense. Existing profile/pixel mutations and reverted supervisor exit guard also reject.

Reviewer fixture corrections are retained: the initial sparse manifest omitted unchanged supervise.py.gz and test-tiers.js; explicit sparse restoration repaired the fixture. The independent frame mutation initially expected a generic missing rejection instead of the actual frame-message mismatch; a subsequent attempt encountered its own stale receipt. The probe now uses fresh owned fixture directories and exact message expectations. These were reviewer preparation failures, not candidate defects; their stderr remains adjacent. No substantive assertion was suppressed.

Historical authentic capture 7526174ea2c6edb0180e4977a07680efa6def158 FAILED both strategies at batch30000 with no retained pixels. Authentic fit under the new profile remains UNKNOWN, as do menu/Lua/gameplay outcomes. No runtime, guest, box, native instantiation, build, acquisition or deployment is authorized or performed here. Box assignment:none; lifecycle remains coordinator-owned.

The old allocation failure remains FAILED: task-owned peak440418438bytes, unintended materialization438716226bytes/9971files. Preserve original /tmp/enigma-bounded-single-frame-profile-oct24/ops/resource-first-rejection.json and cleanup.json, also committed gzip evidence in the candidate. Coordinator explicitly authorized prospective cleaned publication; that does not retroactively make the old run resource-compliant. This fresh task used git init, deduplicated flattened immutable donor alternates and explicit noncone paths, never checkout-index -a. Measured initial materialization1631131bytes before tests. Admission includes full external session/launcher/event bytes, positive SQLite growth, future growth and8MiB reserve within64MiB, another64MiB host reservation and2982150144byte floor. Trusted dedicated SSH identity/known-host configuration is retained exactly. Mount argv/files are empty because no mount or guest operation exists.

Acceptance evidence and source seals are adjacent. Exact merged-tree checks, atomic no-force main+task push and actual remote ref/blob verification are required by the integration script; final local receipts are /tmp/enigma-single-frame-independent-closeout-oct24/ops/. Root tracked files/index/refs and all donor repositories remain read-only; only append-only root messageboard is shared.