A wave's page says which milestones it moved, each with how far along it is now #7957

A wave's page now has a short "Moved" list under the highlights. Each entry is a milestone the wave moved, linked, with how many of its issues are done out of how many. I didn't change any code this run, because the branch already held the work and was green locally.

I never saw why the check went red on pull #7798. The branch is already merged with current main and origin has everything, so this push was a no-op. If the forge check still fails on this branch, its log is the next thing to read.

What changed on the branch

• src/story/wave_moved.ts (new): a pure function. Given a wave's pull numbers, the issues those pulls closed and the plan graph, it returns the milestones above those issues, each with title, link and done/total. Pillar umbrellas and the Later gate are not counted as milestones, by the same rule milestones.ts uses.
• src/story/wave_pulls.ts: supplies the issues the wave's pulls closed.
• src/web/pages/waves.ts: renders the "Moved" list and shows nothing when the wave moved none. It reads the plan once per request through readPlan, not once per pull. A milestone the viewer can't read is left out.
• src/tui/screens/waves.ts: the terminal wave screen lists the same milestones, from the same function.
• src/web/pages/milestones.ts: refactored so the page and the new module share the milestone rule.
• README.md: updated.

Tests

• test/wave-moved.test.ts covers the module and the page. On a graph where two pulls close issues under one milestone and a third closes an issue under none, it gives exactly that milestone with the right counts.
• test/tui-waves.test.ts covers the terminal screen.

Checks run here

• scripts/gate.ts, tsc --noEmit and scripts/design-lint.ts are clean.
• 119 tests across the wave, milestone, plan-pillar and MCP/API wave suites pass.
• A further 141 across the route-timing, XSS, design-audit and map suites pass.
• scripts/fast.ts reported the diff as too broad to name tests, so I chose these files myself rather than run the full suite.

What I chose not to do I didn't split the issue. The parked comment suggested it, but the change is small and passes locally.

To try it Open any wave page that includes a pull closing an issue under a milestone. The "Moved" list sits under the highlights. In the terminal, the wave screen shows the same list.

🤖 Generated with Claude Code

Closes #7761

A wave's page now has a short "Moved" list under the highlights. Each entry is a milestone the wave moved, linked, with how many of its issues are done out of how many. I didn't change any code this run, because the branch already held the work and was green locally.

I never saw why the check went red on pull #7798. The branch is already merged with current main and origin has everything, so this push was a no-op. If the forge check still fails on this branch, its log is the next thing to read.

What changed on the branch

• src/story/wave_moved.ts (new): a pure function. Given a wave's pull numbers, the issues those pulls closed and the plan graph, it returns the milestones above those issues, each with title, link and done/total. Pillar umbrellas and the Later gate are not counted as milestones, by the same rule milestones.ts uses.
• src/story/wave_pulls.ts: supplies the issues the wave's pulls closed.
• src/web/pages/waves.ts: renders the "Moved" list and shows nothing when the wave moved none. It reads the plan once per request through readPlan, not once per pull. A milestone the viewer can't read is left out.
• src/tui/screens/waves.ts: the terminal wave screen lists the same milestones, from the same function.
• src/web/pages/milestones.ts: refactored so the page and the new module share the milestone rule.
• README.md: updated.

Tests

• test/wave-moved.test.ts covers the module and the page. On a graph where two pulls close issues under one milestone and a third closes an issue under none, it gives exactly that milestone with the right counts.
• test/tui-waves.test.ts covers the terminal screen.

Checks run here

• scripts/gate.ts, tsc --noEmit and scripts/design-lint.ts are clean.
• 119 tests across the wave, milestone, plan-pillar and MCP/API wave suites pass.
• A further 141 across the route-timing, XSS, design-audit and map suites pass.
• scripts/fast.ts reported the diff as too broad to name tests, so I chose these files myself rather than run the full suite.

What I chose not to do I didn't split the issue. The parked comment suggested it, but the change is small and passes locally.

To try it Open any wave page that includes a pull closing an issue under a milestone. The "Moved" list sits under the highlights. In the terminal, the wave screen shows the same list.

🤖 Generated with Claude Code

I've made both changes sentinel asked for and pushed them. tsc, the gate, design-lint and the wave and milestone tests pass locally (86 tests across 11 files). I did not run the full suite.

• Moved rows: each row now uses row({ href }), so the whole row navigates and j/k hover applies. The visible count is the single pill ("N of M done"). The progress bar stays and keeps its aria-label, so the count is no longer repeated as text.
• Layering: the terminal wave screen no longer imports from src/web/pages. A new src/story/wave_plan.ts holds milestonePath and planNow. The terminal reads the plan through planNow, which skips the web plan cache. milestoneHref in src/web/pages/milestones.ts now points at milestonePath, so the link has one definition.
• Import order: closesFromBody is now in alphabetical order in wave_pulls.ts.

Where I didn't fully follow sentinel's note: progress is still exported from the milestones page, because the wave page uses the bar. It is a web-to-web import. planFor is now exported for the same reason, and the wave page keeps the cached plan.