Fix Plan Walkthrough

A named wall, then the clearest possible path through it.

This is what SwarmWarn returns when Container Sizing detects a wall. Four panels: the verdict, the evidence, the recovery diff, and the cleared post-state.

Named wall512 MBVercel function ceiling

Bundle528 MB+16 MB over

Recovery3 stepsPR-ready diff

Cleared at364 MBvs. 512 MB ceiling

Named wall

wallcontainer_sizing.ceiling_exceeded

surfacevercel.functions.prod

rule_idSIZE-CEIL-001

severityhold-promotion

explanationmodel output (rules-first, model-second)

→ "Build #4291 produces a 528 MB function bundle. The Vercel ceiling for this project is 512 MB. The build is 16 MB over and trending +6 MB per promotion. Promotion will fail at the platform layer."

Evidence chain

build_id#4291 · commit 9a4f2c1

measured_at2026-05-28T17:14:08Z

bundle_size528 MB (compressed function payload)

top_contributors@swarm/i18n (62MB), admin routes (34MB)

trend_7d+47 MB / week

chainreadout signed · attested

Recovery diff (PR-ready)

action_1drop @swarm/i18n unused locales (-22 MB)

action_2defer /admin route bundle (-14 MB)

action_3switch /api/reports to OpenNext adapter

net_change-164 MB · 528 → 364 MB

PR_readygithub.com/your-org/app/pull/128

rollbackbuild #4287 (clean) — 388 MB

Cleared verdict

new_build#4292 (recovery applied)

bundle_after364 MB / 512 MB ceiling

edge_payloads12 / 12 under budget

trend_7d-12 MB · headroom recovered

verdictclear — promotion authorized

→ SwarmWarn never promoted the build. The named wall held. The recovery diff was merged. The next build cleared. That's the loop.

Want this on every push?

Sizing Recovery includes the fix-plan loop on every build. Sizing Watch tells you when the wall will land.

See pricing Request access