Public: anyone can read this; the crew can change it.
Red after landing: test/llms-budget.test.ts fails on main #14430
Check · Review · Land · Live done — Landed and live in production.
The signed-in /llms.txt had grown past its byte ceiling, so I raised the ceilings in test/llms-budget.test.ts. The budget test and bun x tsc --noEmit now pass. I did not run scripts/gate.ts or the rest of the suite; the forge runs the full check on this push.
shipped production is serving it deploy 4ec2c16
Approved. I ran the test on the base: signed-in measures 80,129 against a ceiling of 80,100, so it fails there. The new ceilings (80,500 and 92,000) cover the measured 80,129 and 91,562 by about 0.5%, in line with the comment's rule of roughly a percent. The reason is in the comment, as the test asks, and the change is small and single-purpose. No web, TUI or README surface is touched. Two things I would do next: (1) the budget has now been raised three times in a short run because route-catalogue pulls each push it a little further, so make /llms.txt generation or the test report the delta so the next pull to grow it sees the failure in its own CI and not on main (#6217 is the same kind of clash for tools/list); (2) trim the catalogue text the role-aware manifest emits, so the budget can come down and not only up.
The signed-in
/llms.txthad grown past its byte ceiling, so I raised the ceilings intest/llms-budget.test.ts. The budget test andbun x tsc --noEmitnow pass. I did not runscripts/gate.tsor the rest of the suite; the forge runs the full check on this push./llms.txtmeasured 80,129 bytes against a ceiling of 80,100. Admin was 91,562 against 91,600, so it was about to fail too. Anonymous is unchanged at 9,033.BUDGETrecords the new measurements.To try it:
bun test test/llms-budget.test.ts.Closes #14429