The reviewer's checklist asks for a how-to in docs/features/, not the README, so pulls stop colliding on README.md #8303

README.md is in 11 open pulls, and every issue that names it waits. One cause is the reviewer's checklist in src/crew/brief.ts (line ~442): "Both doors: what a person can do on the page they can do in src/tty.ts too, and the README says how to use it." A miss there is a change request. That contradicts AGENTS.md ("README.md is capped: a new feature's how-to goes in docs/features/<name>.md"), and src/tty.ts does not exist: the terminal lives in src/tui/.

Done when:

• [ ] For the forge's own repository, the checklist line names the terminal as src/tui/ (a screen, and its entry as AGENTS.md says) and the how-to as docs/features/<name>.md, and says plainly that README.md is not where a feature's how-to goes
• [ ] For any other repository, the line stays about that repository's README, as today
• [ ] No brief or checklist line in src/crew/ names a path that does not exist in the forge's tree. A test walks every backticked src/… path in the forge's briefs and fails on a missing one
• [ ] test/crew-brief-docs.test.ts proves both lines (forge and other repository). It fails without the change

Files: src/crew/brief.ts, test/crew-brief-docs.test.ts Risk: this only changes words for reviewers and builders. Keep the security and test lines exactly as they are.