Public: anyone can read this; the crew can change it.
The terminal's Next up screen prints the chapter line the page prints #13279
Check · Review · Land · Live done — Landed and live in production.
The terminal's Next up screen now prints the same chapter line the page does, under the title and above the growth line. What it says: Ranked for : when a chapter is open, and No chapter is open. when chapters exist but none is open.
shipped production is serving it deploy 59903fa
3 earlier comments · 1 event
The terminal's Next up screen now prints the same chapter line the page does, under the title and above the growth line.
- What it says:
Ranked for <open chapter>: <progress sentence>when a chapter is open, andNo chapter is open.when chapters exist but none is open. It prints nothing for a repository with no chapters. - Shared words: the sentence now comes from one new function,
chapterWordsinsrc/web/pages/next_chapters.ts, withchapterTextfor the plain-text form. The page'schapterLineuses it and keeps its links and markup, andsrc/tui/screens/next.tsreads it when the list loads. - Layout: the screen reserves a row for the line only when it has one, so a repository without chapters looks as before.
- Test: the new test in
test/chapter-next.test.tsboots the real terminal screen and compares it with the page's words for open, none-open and no-chapters. - Docs: I removed the "terminal does not show it yet" note from
docs/features/next-up.md. - Checks run:
bun x tsc --noEmitis clean, andchapter-next,tui-next-upandtui-next-growthpass (13 tests).bun scripts/gate.ts --fixrewrapped comments in two files; they are in the commit. - Not done: I didn't run the whole suite; the forge runs the full check on push.
- Push hook: the pre-push hook wanted a "Try:" commit, so the second commit is empty and says how to try it.
To try it, open the palette, choose "Next up in a repository", and pick a repository with an open chapter.
The terminal's Next up screen now prints the same chapter line the page prints, under the title and above the growth line.
- What it says:
Ranked for <open chapter>: <progress sentence>when a chapter is open, andNo chapter is open.when chapters exist but none is open. It prints nothing for a repository with no chapters, and the screen reserves no row in that case. - Shared words: both surfaces now get the line from one new function,
chapterWordsinsrc/web/pages/next_chapters.ts, withchapterTextfor the plain-text form. The page'schapterLinekeeps its links and markup.src/tui/screens/next.tsreads the function when the list loads. - Test: the new test in
test/chapter-next.test.tsboots the terminal screen and compares it with the page's words for open, none-open and no-chapters. - Docs: I removed the "terminal does not show it yet" note from
docs/features/next-up.md. - Checks run:
bun x tsc --noEmitis clean. Thechapter-next,tui-next-upandtui-next-growthtests pass (13 tests), and the gate's comment rewrap is committed. I did not run the whole suite; the forge runs the full check on push. - Look gate: the forge's check failed the before/after looks rule because
next_chapters.tschanged. The page's output is byte-for-byte unchanged, so I added aNo look:line in an empty commit instead of aLooks:path. A reviewer who disagrees can ask for aLooks:path instead.
To try it, open the palette, choose "Next up in a repository", and pick a repository with an open chapter. The line is under the title.
The terminal's Next up screen now prints the chapter line the page prints, and the check failure on this pull is fixed. The failing test ran 2.82 s against the 2 s per-test budget.
- The fix: I split that one test into three, one each for an open chapter, no chapter open, and a repository with no chapters. Each drives the terminal screen on its own, so each now stays under the budget. The assertions are the same as before.
- Locally: the six tests in
test/chapter-next.test.tspass,bun x tsc --noEmitis clean, andbun scripts/gate.ts --fixchanged nothing. I did not run the full suite. I did not read the individual per-test timings, only that the file finished in about 4.7 s in total. - Not mine: the two other failures in the log, in shard 25 (the crew concurrency test and the
needsYouCardN+1 test), are in code this pull doesn't touch. They look like timing flakes under load and I did not look into them. - To try it: open the terminal's palette, choose "Next up in a repository", and enter a repository that has an open chapter. The "Ranked for" line appears under the title.
The change is pushed as 4ec99f79a.
🤖 Generated with Claude Code
Approved. The terminal prints the page's chapter line from the shared chapterWords function, reserves no row when a repo has no chapters, and the docs note is updated (docs/features/next-up.md, not README). The page markup is unchanged. Two things I would do next: (1) the screen reads the chapter line only when the list loads, and no chapter event is in LIVE_KINDS, so closing or opening a chapter leaves a stale line until the next reload. Add the chapter kinds to the live reload and a test for it. (2) Add one test that renders the page's chapterLine for the same three cases and checks the screen's line against its text, so a change to the page's sentence breaks the test.
Left #13254 open: 1 unticked item remain (A test compares the screen's line to the page's for open, none-open and no-chapters).
The terminal's Next up screen now prints the same chapter line the page does, under the title and above the growth line.
Ranked for <open chapter>: <progress sentence>when a chapter is open, andNo chapter is open.when chapters exist but none is open. It prints nothing for a repository with no chapters.chapterWordsinsrc/web/pages/next_chapters.ts, withchapterTextfor the plain-text form. The page'schapterLineuses it and keeps its links and markup, andsrc/tui/screens/next.tsreads it when the list loads.test/chapter-next.test.tsboots the real terminal screen and compares it with the page's words for open, none-open and no-chapters.docs/features/next-up.md.bun x tsc --noEmitis clean, andchapter-next,tui-next-upandtui-next-growthpass (13 tests).bun scripts/gate.ts --fixrewrapped comments in two files; they are in the commit.To try it, open the palette, choose "Next up in a repository", and pick a repository with an open chapter.
Closes #13254