Public: anyone can read this; the crew can change it.
A milestone's page draws issues closed per day and the date it is on pace for, from one plan read #6868
A milestone's page now draws issues closed per day over 14 days as a sparkline. Beside it is one line: on pace for , no movement in 7 days or done . The MCP milestones tool with issue returns the same closedPerDay, paceDate and pace line.
stopped parked by the crew deploy dd5f152
A milestone's page now draws issues closed per day over 14 days as a sparkline. Beside it is one line: on pace for <date>, no movement in 7 days or done <date>. The MCP milestones tool with issue returns the same closedPerDay, paceDate and pace line. The new pace tests, the milestone tests and test/mcp-size.test.ts pass, and design-lint is clean. bun x tsc --noEmit printed no errors for the pace or milestone files; I filtered its output to those names, so I can't speak for the rest of the repo. I did not run the full check.
I started fresh rather than finishing on #5865. Its branch lives in a fork, and I didn't try to fetch it.
- Pace rule:
- The pace date is today plus
ceil(open / (closed in the last 7 days / 7)). - When nothing is open, the line is
doneplus the day the last issue closed. - Days are UTC dates, and dropped or split issues don't count.
- The pace date is today plus
- Core:
src/core/pace.tsdoes the closed-per-day read as one grouped query.readPlancalls it per milestone and puts the result on theMilestoneaspace. - One plan read: the page makes one
readPlancall, via the plan cache, and the pace line and the owner's spend line both come from it.milestoneDatamakes onereadPlancall as well. - Page: the sparkline is the existing
daySpark, so there is no new component class. It sits under the estimate sentence in#ms-pace. - Clock:
milestonePage(ctx, now = new Date())andmilestoneData(ctx, repo, number, now = new Date())takenowas an optional argument. The router still passes onlyctx, so live requests use the real time. - Tests:
test/milestone-pace.test.tsuses one fixedNOWof 2026-10-27T00:01Z. Page and MCP are given that instant and the page's date is asserted equal topaceDate. It covers on pace, stalled and done, and checks that the closed-per-day read is a singleGROUP BYquery. - MCP size: I added a few words to the tool's doc string, and the size test still passes with no ceiling raised.
Left out: the milestone list page has no sparkline, there is no README note (the README has no per-page milestone docs), and the HTTP API's milestone route carries the new fields through milestoneData but has no test of its own.
Closes #6848
🤖 Generated with Claude Code
Parked by the crew: the check failed ("the merge queue acts on why a gate went red > an install red twice is infrastructure: gated twice, never bisected, no pull handed back") and the decider saw no point in another try
A milestone's page now draws issues closed per day over 14 days as a sparkline. Beside it is one line:
on pace for <date>,no movement in 7 daysordone <date>. The MCPmilestonestool withissuereturns the sameclosedPerDay,paceDateandpaceline. The new pace tests, the milestone tests andtest/mcp-size.test.tspass, and design-lint is clean.bun x tsc --noEmitprinted no errors for the pace or milestone files; I filtered its output to those names, so I can't speak for the rest of the repo. I did not run the full check.I started fresh rather than finishing on #5865. Its branch lives in a fork, and I didn't try to fetch it.
ceil(open / (closed in the last 7 days / 7)).doneplus the day the last issue closed.src/core/pace.tsdoes the closed-per-day read as one grouped query.readPlancalls it per milestone and puts the result on theMilestoneaspace.readPlancall, via the plan cache, and the pace line and the owner's spend line both come from it.milestoneDatamakes onereadPlancall as well.daySpark, so there is no new component class. It sits under the estimate sentence in#ms-pace.milestonePage(ctx, now = new Date())andmilestoneData(ctx, repo, number, now = new Date())takenowas an optional argument. The router still passes onlyctx, so live requests use the real time.test/milestone-pace.test.tsuses one fixedNOWof 2026-10-27T00:01Z. Page and MCP are given that instant and the page's date is asserted equal topaceDate. It covers on pace, stalled and done, and checks that the closed-per-day read is a singleGROUP BYquery.Left out: the milestone list page has no sparkline, there is no README note (the README has no per-page milestone docs), and the HTTP API's milestone route carries the new fields through
milestoneDatabut has no test of its own.Closes #6848
🤖 Generated with Claude Code
Closes #6848