Public: anyone can read this; the crew can change it.
The terminal asks whoever can, and answers: "What stands in the way" #12976
Check · Review · Land · Live done — Landed and live in production.
This replaces #12970, which was based on #12953's branch. #12953 has landed, and the API cannot change a pull's base, so this is the same branch rebased onto main with the review's changes in it.
shipped production is serving it deploy 1b35e66
Approved. The terminal door is a screen under src/tui/screens/ with its palette entry in forgeCommands, offered to anyone signed in and to nobody else. Every write goes through the page's own actions (askAdmin, putAsideAsk), so who may ask and who may answer is decided in one place. The how-to is in docs/features/blocked-by.md and README is untouched. There is no new dependency. The terminal screen has no preview URL to open, but the tests exercise it end to end: member ask, admin Not now, the toasts on rows a key does not apply to, and a signed-out session. I did not run bun test myself.
Two things I would do next:
- The third test in test/tui-asks-admin.test.ts depends on rows left by the first two tests (bob's put-aside ask). Seed that state inside the test so it passes alone.
- Wrap the long one-line toasts and the inline user setup in asks_admin.ts and the test to the repository's formatting, and move the user factory into the shared make helper.
This replaces #12970, which was based on #12953's branch. #12953 has landed, and the API cannot change a pull's base, so this is the same branch rebased onto main with the review's changes in it.
Direction: what it serves, and why before the pipeline
It serves the review of #12953, which asked for the terminal door of the action that pull added: "No terminal door for this action (nothing in src/tui/). Add the screen, with its entry where AGENTS.md says, so the terminal can ask and answer too." That is the repository's three doors rule; there is no separate issue for it. It goes ahead of the pipeline items because #12953 is already on main: until this lands, an action people can take on the page and over the API has no terminal door. It is one screen, its palette entry, its test and a paragraph of how-to. It could not ride in #12953: a pull that adds a screen stays at twenty files (rule "small and single-purpose"), and that one was about seventy.
What a person now sees
In the terminal, ctrl-k, "What stands in the way", for anyone signed in:
oopens the exact control,nis Not now.oopens the control for one who can change it;asends the ask for one who cannot.Every write is the page's own action (
src/actions/ask_admin.ts).What the review of #12970 asked, and what changed
oon a row you already asked said "That is not yours to change: a asks whoever can." It now says "Already asked: the row says how it stands.";athere says the same, andaon a row that waits on you says "This one waits on you: o opens where it is changed."oon a row that waits on the admin opens/settings/accounts/cal#f-grant;oon the admin's own row opens/settings/crew#crew-key;aon an asked row andnon a row that is not an answer each say their sentence and write nothing.Also, as the review's next step: nobody signed in is offered no palette entry, tested.
To know before landing
Main is red on
test/refusals-lead-somewhere.test.ts(a sentence insrc/core/roles.ts), and #12974 clears it. This pull does not touch that file.Run locally on this commit:
bun x tsc --noEmitandbun scripts/gate.tsexit 0; the always-run set with the terminal and palette tests is green but for the two Mac-only reds and that one red of main's.🤖 Generated with Claude Code