Automate a review finding as a lint or test: Both doors missing: the page has no terminal screen in `src/tui/` with its entry #10694

I fixed the wording, tightened the assertions and added a test for the git wiring. I ran bun scripts/gate.ts and bun x tsc --noEmit, and both came back clean. The new and changed tests pass, 5 of 5.

• Message join: src/kernel/both_doors.ts no longer puts an article in the missing list. The message now reads but no terminal screen in src/tui/ (entry where AGENTS.md says) and no docs/features/<name>.md how-to.
• Vacuous assertions: test/both-doors.test.ts now compares the whole expected sentence with toEqual for three cases: neither door, only the doc missing, and only the screen missing. A wording regression in any of them fails.
• bothDoorsRefusal coverage: new test/both-doors-refusal.test.ts builds a temporary git repo and runs bothDoorsRefusal against a real commit range. It covers three outcomes:

- A page added alone is refused. - A later No door: … commit message waives the refusal. - A page added together with its screen and its doc passes.

I did not run the rest of the suite; the forge runs the full check on the push.

Continues #10694

I fixed the wording, tightened the assertions and added a test for the git wiring. I ran bun scripts/gate.ts and bun x tsc --noEmit, and both came back clean. The new and changed tests pass, 5 of 5.

• Message join: src/kernel/both_doors.ts no longer puts an article in the missing list. The message now reads but no terminal screen in src/tui/ (entry where AGENTS.md says) and no docs/features/<name>.md how-to.
• Vacuous assertions: test/both-doors.test.ts now compares the whole expected sentence with toEqual for three cases: neither door, only the doc missing, and only the screen missing. A wording regression in any of them fails.
• bothDoorsRefusal coverage: new test/both-doors-refusal.test.ts builds a temporary git repo and runs bothDoorsRefusal against a real commit range. It covers three outcomes:

- A page added alone is refused. - A later No door: … commit message waives the refusal. - A page added together with its screen and its doc passes.

I did not run the rest of the suite; the forge runs the full check on the push.

The failing test was caused by main, not by my change. I've fixed it and pushed, and test/tui-asks-first.test.ts now passes. The pull's own both-doors test passes too, and bun scripts/gate.ts and bun x tsc --noEmit came back clean. I did not run the full suite; the forge's check runs it on the push.

Pull #10671, already on main, added revoke to src/tui/screens/devices.ts:122. The "terminal asks first" test flags it as a destructive call that runs without a confirm.

I merged current main into the branch, and the test was still red, so the cause is not just a stale base.

I added revoke in devices.ts to the test's own allowed list, with a reason. I did not add a confirm screen: the r key already opens a prompt where you type the app's slug, so the action is deliberate. Revoking only stops that app printing, and a undoes it. If you'd rather the screen ask y/n like hooks.ts does, that is a separate change to the devices screen. I left it out because this pull is about the both-doors lint.

I merged main into the branch and pushed. The branch now merges cleanly.

The only conflict was in test/tui-asks-first.test.ts. Both sides had added the same revoke entry for src/tui/screens/devices.ts to the allowed list, each with its own reason text. I kept main's wording ("passed to askApp, run only from the slug prompt's onSubmit") and dropped mine. The entry itself is unchanged.

The ask-first test and the two both-doors test files pass (12 tests). bun scripts/gate.ts and bun x tsc --noEmit were clean. I did not run the rest of the suite; the forge's check does that on the push.

Everything is already pushed; the branch is current with origin.

Pull description:

The gate now refuses a pull that adds a page without its terminal screen and how-to. This is the "both doors" finding reviewers made on #9464, #10595, #10609 and #9844.

• The rule: a pull that adds src/web/pages/*.ts must also add a screen under src/tui/ and a docs/features/<name>.md. Otherwise it needs a commit line No door: <why>. The rule lives in src/kernel/both_doors.ts.
• Where it runs: bun scripts/gate.ts calls it through bothDoorsRefusal. The failure message names the rule ("both doors", #10628). AGENTS.md line 6 states it for people and agents.
• Tests: test/both-doors.test.ts and test/both-doors-refusal.test.ts.
• Checked this run: both test files pass (5 tests). bun scripts/gate.ts is clean on the branch. I did not run bun x tsc --noEmit this run, and nothing changed since the last push.
• Not done: the rule doesn't judge whether a screen is a good one, and it doesn't check that the entry is wired where AGENTS.md says. It only checks that a screen and a how-to are present.

Nothing has changed since my last run. The branch is clean, level with main plus this change, and the gate passes. Nothing new to push.

Pull description:

The gate now refuses a pull that adds a page without its terminal screen and how-to. This is the "both doors" finding reviewers made on #9464, #10595, #10609 and #9844.

• The rule: a pull that adds src/web/pages/*.ts must also add a screen under src/tui/ and a docs/features/<name>.md. Otherwise it needs a commit line No door: <why>. The rule lives in src/kernel/both_doors.ts.
• Where it runs: bun scripts/gate.ts calls it through bothDoorsRefusal. The failure message names the rule ("both doors", #10628). AGENTS.md line 6 states it for people and agents.
• Tests: test/both-doors.test.ts and test/both-doors-refusal.test.ts. Both passed when I last ran them. I did not re-run them this time.
• Not done: the rule doesn't judge whether a screen is a good one, and it doesn't check that the entry is wired where AGENTS.md says. It only checks that a screen and a how-to are present.