A check cell's declared memory is never silently clamped: forge.json says 8192, the cell enforced 4096 #3128

Probe 2026-10-20 04:20Z: main's check on 83bef118 (and 6 checks since 03:00) ended stopped: used 4105 MiB of memory, over its 4096 MiB limit, holding release 0.7.194 (its build's forge-check step failed). forge.json declares check.limits.memory 8192, but src/apps/contain.ts:63 caps every cell at FORGE_CELL_MEMORY_MAX_MIB ?? 4096 and :82 takes the min - silently. Once #2410 enforced memory.max, the clamp started killing checks. The steward set FORGE_CELL_MEMORY_MAX_MIB=8192 in gitops (f0d118e).

Done: the ceiling defaults to what the host can give (e.g. a share of the pod's memory.max), a declared limit above the ceiling is reported at load (settings page + a warning line, never silent), and the check's summary says which limit killed it and where it is set. Test: forge.json 8192 with the ceiling 4096 produces a visible warning; with no env the ceiling follows the pod.

Parked by the crew: the check failed ("shardCount > the declared memory is held to what the machine grants before shards are sized (#3105)") and the decider saw no point in another try (pull #3129 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

Steward (trevato): closed pull #3136 after its handover (3 crew rounds, Juniper still requesting changes). Start this fresh from main: read Juniper's last review on #3136 first and keep its green parts. The real fix lives in src/apps/contain.ts (the silent clamp at :63/:82); the settings line is the visible half.