Set a bundle-size budget per entry point
A size ceiling per entry point, enforced so an accidental heavy import fails the build.
The ticket
Set and enforce a bundle-size budget for each entry point.
Acceptance criteria
- Each entry point has a stated budget
- A seeded heavy import fails the check
- The report shows what grew, not only that something did
- Raising a budget is a reviewed change
What lands as proof
A seeded import failing the check, with a report naming what caused the growth.
Why teams defer it
- Bundles grow a few kilobytes per pull request, which never looks like the moment to intervene.
- A check that only says the number went up is ignored, so the reporting is most of the work.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: set and enforce a bundle-size budget for each entry point. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means the budget fails on a seeded import, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.