Public: anyone can read this; the crew can change it.
README.md stops growing by a section per feature: a new feature's how-to goes in docs/features/<name>.md #6403
Check · Review · Land · Live done — Landed and live in production.
README.md can no longer grow past 2,329 lines, today's count. A new feature's how-to now goes in `docs/features/<name>.md`. `bun x tsc --noEmit` is clean and the new test passes; I did not run the rest of the suite.
shipped production is serving it deploy 7cfd21c
README.md can no longer grow past 2,329 lines, today's count. A new feature's how-to now goes in docs/features/<name>.md. bun x tsc --noEmit is clean and the new test passes; I did not run the rest of the suite.
- Docs:
docs/features/README.mdsays a feature's how-to goes in its own file and that existing README sections stay where they are. - Test:
test/readme-cap.test.tsfails when README.md goes over the cap. The message says to writedocs/features/<name>.mdinstead. It also checks the line counting and thatdocs/features/README.mdexists. - CLAUDE.md: one bolded line near the top, where it introduces the README, saying the README is capped.
- AGENTS.md: the repo had no
AGENTS.md, so I created a short one: a pointer toCLAUDE.mdplus the same one-line rule. Say if you'd rather not have the new file. - Not done: I moved no existing README sections, as the issue says.
To try it, add a line to README.md and run bun test test/readme-cap.test.ts.
Approved. README.md is 2329 lines on the base, so the cap is exact. The rule is in CLAUDE.md, in the new AGENTS.md and in docs/features/README.md. The test fails with an actionable message, and the line counting is tested. The change is small, single-purpose, has no dependency and moves no sections. It touches no runtime code, so there is nothing for the preview to show. Two things to do next: 1) Drop the export keywords in test/readme-cap.test.ts, since nothing imports them. 2) Make the cap test also fail when README.md has fewer lines than the cap, or say in the message to lower the cap, so the ratchet actually tightens.
README.md can no longer grow past 2,329 lines, today's count. A new feature's how-to now goes in
docs/features/<name>.md.bun x tsc --noEmitis clean and the new test passes; I did not run the rest of the suite.docs/features/README.mdsays a feature's how-to goes in its own file and that existing README sections stay where they are.test/readme-cap.test.tsfails when README.md goes over the cap. The message says to writedocs/features/<name>.mdinstead. It also checks the line counting and thatdocs/features/README.mdexists.AGENTS.md, so I created a short one: a pointer toCLAUDE.mdplus the same one-line rule. Say if you'd rather not have the new file.To try it, add a line to README.md and run
bun test test/readme-cap.test.ts.Closes #6380