Playbook 07: a milestone has steps, runs the whole unit suite, writes its findings into its issues, watches on the smaller model; design 47 names milestone 2b and takes 895 (issue 1053)
#412
Merged
mesh-toolsmerged 1 commits from fix/1053-steps-not-phases into main2026-10-17 18:29:24 +00:00
Issue 1053 (the operator's words of 2026-10-17 that playbook 07 and design 47 did not yet say).
Playbook 07: a milestone has no phases; its five parts are steps, in headings, references, the report layouts and the save point.
Playbooks 07 and 08: the whole unit suite runs before every commit, not only the tests of what changed.
Playbook 07: watchers run on the smaller model, never the smallest.
Playbook 07, the prepare step: its findings go into the issues (files and tests by search, how the change is checked and delivered, a group's merge order) before any agent starts.
Each new rule says how it is checked.
Design 47: milestone 'II' is milestone 2b; milestone 3 takes issue 895 (the split of unit and integration tests; 1046 was closed as its duplicate).
Reviewed before the push by an independent reviewer (larger model), round 1: APPROVE at 2001d6e063. The matching change to the instruction section how-work-is-done is proposed through claude_code_instructions_propose.
Issue 1053 (the operator's words of 2026-10-17 that playbook 07 and design 47 did not yet say).
- Playbook 07: a milestone has no phases; its five parts are steps, in headings, references, the report layouts and the save point.
- Playbooks 07 and 08: the whole unit suite runs before every commit, not only the tests of what changed.
- Playbook 07: watchers run on the smaller model, never the smallest.
- Playbook 07, the prepare step: its findings go into the issues (files and tests by search, how the change is checked and delivered, a group's merge order) before any agent starts.
- Each new rule says how it is checked.
- Design 47: milestone 'II' is milestone 2b; milestone 3 takes issue 895 (the split of unit and integration tests; 1046 was closed as its duplicate).
Reviewed before the push by an independent reviewer (larger model), round 1: APPROVE at 2001d6e06334810b53e8a0d40fb97ee1f42a7229. The matching change to the instruction section how-work-is-done is proposed through claude_code_instructions_propose.
Deliverynovox/hq@2001d6e06334 — delivered since 2026-10-17T18:29:26Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-17 18:20 (new) → proposed (announced): novox/hq#412's head announced
2026-10-17 18:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 18:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 18:28 ready → proposed (trunk moved): out of date: judged against trunk 90c6793096, the trunk is now e44ec3f61235; judged again on a recheck or when it is merged
2026-10-17 18:29 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 18:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 18:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-17 18:29 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@2001d6e06334` — **delivered** since 2026-10-17T18:29:26Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-17 18:20 (new) → proposed (announced): novox/hq#412's head announced
- 2026-10-17 18:27 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 18:27 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 18:28 ready → proposed (trunk moved): out of date: judged against trunk 90c67930969b, the trunk is now e44ec3f61235; judged again on a recheck or when it is merged
- 2026-10-17 18:29 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 18:29 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 18:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-17 18:29 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Reviewed by review-1053@shanks: Round 1 APPROVE: issue 1053's five points hold in playbooks 07/08 and design 47; merge-check.sh passes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at 2001d6e06334810b53e8a0d40fb97ee1f42a7229
Reviewed by review-1053@shanks: Round 1 APPROVE: issue 1053's five points hold in playbooks 07/08 and design 47; merge-check.sh passes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
Out of date when it landed: out of date: judged against trunk 90c6793096, the trunk is now e44ec3f61235; judged again on a recheck or when it is merged
**Merge check** at `2001d6e0`: head 2001d6e06334 merged into trunk 90c67930969b, pass
**Out of date when it landed**: out of date: judged against trunk 90c67930969b, the trunk is now e44ec3f61235; judged again on a recheck or when it is merged
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 1053 (the operator's words of 2026-10-17 that playbook 07 and design 47 did not yet say).
Reviewed before the push by an independent reviewer (larger model), round 1: APPROVE at
2001d6e063. The matching change to the instruction section how-work-is-done is proposed through claude_code_instructions_propose.Delivery
novox/hq@2001d6e06334— delivered since 2026-10-17T18:29:26ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
90c6793096, the trunk is now e44ec3f61235; judged again on a recheck or when it is mergedThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.ready at
2001d6e063Reviewed by review-1053@shanks: Round 1 APPROVE: issue 1053's five points hold in playbooks 07/08 and design 47; merge-check.sh passes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
Merge check at
2001d6e0: head2001d6e063merged into trunk90c6793096, passOut of date when it landed: out of date: judged against trunk
90c6793096, the trunk is now e44ec3f61235; judged again on a recheck or when it is merged