Public: anyone can read this; the crew can change it.
Milestones at the front door: how close the big things are, what moved this week, and the wave that moved them #1083
Parked by the crew: the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #1087 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #1096 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #1087 closed)
- the check failed ("capacity: only a forge admin reads or changes it > an admin changes each one from the page, the API and MCP; a wrong value is refused; every change is kept") and the decider saw no point in another try (pull #1096 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Deferred behind the Later gate (#595). Both tries failed on the capacity test that was red on main, not on this work. Milestones at the front door depend on waves existing: "the wave that moved them". Waves start with #1125. The owner also asked for a calmer home on 2026-10-12, so the front door gets nothing new until waves are real. When #1125 lands and the gate is open, re-plan this as one panel that reads the waves.
Released from Later to use the week's subscription: Under the allowed burn: 36% of the week left with 38% of its time gone, reset 2026-11-15 02:00 UTC, burning 0.2% an hour over the last 6 h against 0.3% allowed; speeding up to 5 of 5 slots and releasing the next issue.
Reviewed pull #10987 at its head: ticked The forge's home shows the three biggest open milestones across the viewer's apps (by open work beneath them), each one line: name, done of total, moved this week, estimate.; A public repository's page shows its milestones to anyone who may read it, cost only to owner facts.; A wave's note (see the waves issue) names the milestones it moved; the milestone page links back to the wave.; The lines are live regions that fetch themselves (data-live-src) and paint nothing when nothing moved.; The MCP milestones answer carries movedThisWeek and the last wave per milestone..
Pillar: P8 Story. One run, started fresh from today's
main.Outcome (what a person sees). The home (and an app's page) shows the handful of big milestones with how far each is — done of total, what landed in the last 7 days, the plain estimate
core/milestones.tsalready makes — as a few quiet lines, not a dashboard; opening one shows what moved and which wave moved it. A visitor to a public forge sees the public repositories' milestones; owner facts (cost) stay with the owner.Today.
/:owner/:name/milestonesandcore/milestones.tscompute all of this per repository; the feed shows amilestoneitem only to who watches one. Nothing shows at the front door.Acceptance.
data-live-src) and paint nothing when nothing moved.milestonesanswer carriesmovedThisWeekand the last wave per milestone.Waits for nothing. Blocks the umbrella.