milestone.md: a close-only arm #218

Merged
john merged 1 commit from cadence/close-only-arm into main 2026-08-18 19:26:03 +00:00
Owner

Closing a milestone without opening the next one has been hand-written four times, most recently at the v3.5.4 close. Steps 4 and 5 both assumed the close opens a cycle, so "no cycle open" was a deviation from the workflow rather than a path through it.

Step 4 now asks which it is, with no preselected default, and carries the record form for ### Active. Step 5 gets its own close-only bullet. Step 6 already worked on both arms and is untouched.

The arm lives inside step 4 rather than becoming a new step, so the ten external references to milestone.md steps 1, 2, 3, 4 and 7 all still resolve. weight-budgets.json moves in the same commit per D-17 (12183 -> 13307).

self-verify clean, prose-agreement 31/31.

Closing a milestone without opening the next one has been hand-written four times, most recently at the v3.5.4 close. Steps 4 and 5 both assumed the close opens a cycle, so "no cycle open" was a deviation from the workflow rather than a path through it. Step 4 now asks which it is, with no preselected default, and carries the record form for `### Active`. Step 5 gets its own close-only bullet. Step 6 already worked on both arms and is untouched. The arm lives inside step 4 rather than becoming a new step, so the ten external references to milestone.md steps 1, 2, 3, 4 and 7 all still resolve. weight-budgets.json moves in the same commit per D-17 (12183 -> 13307). self-verify clean, prose-agreement 31/31.
docs: give milestone.md a close-only arm
All checks were successful
test / node-test (git, 22) (pull_request) Successful in 33s
test / node-test (git, 24) (pull_request) Successful in 33s
test / node-test (other, 22) (pull_request) Successful in 24s
test / node-test (other, 24) (pull_request) Successful in 23s
test / node-test (planning, 22) (pull_request) Successful in 1m14s
test / node-test (planning, 24) (pull_request) Successful in 1m26s
test / node-test (prose, 22) (pull_request) Successful in 37s
test / node-test (prose, 24) (pull_request) Successful in 29s
test / node-test (review, 22) (pull_request) Successful in 18s
test / node-test (review, 24) (pull_request) Successful in 17s
test / node-test (routing, 22) (pull_request) Successful in 27s
test / node-test (routing, 24) (pull_request) Successful in 32s
test / self-verify (pull_request) Successful in 14s
test / typecheck (pull_request) Successful in 19s
57a9f143c1
Closing a milestone without opening the next one has been hand-written four
times now, most recently at the v3.5.4 close. Steps 4 and 5 both assumed the
close opens a cycle, so "no cycle open" was a deviation from the workflow
rather than a path through it.

Step 4 now asks which it is, with no preselected default, and carries the
record form for `### Active`. Step 5 gets its own close-only bullet. Step 6's
cursor call was already right on both arms and is untouched.

The arm lives inside step 4 instead of becoming a new step, so the ten
external references to milestone.md steps 1, 2, 3, 4 and 7 all still resolve.
weight-budgets.json moves in the same commit per D-17: 12183 -> 13307.
john merged commit cc2d4ed192 into main 2026-08-18 19:26:03 +00:00
Sign in to join this conversation.
No description provided.