Playbooks 07 and 08 without the ready mark; a fixing agent runs no integration test; large issues split; the merge script ships first (issues 1022, 895)
#413
Merged
mesh-toolsmerged 5 commits from feat/one-group-one-plan into main2026-10-17 20:10:56 +00:00
Design 47 milestone 3, with mesh-controller and mesh-catalog on the same branch name; the text becomes true when their change is delivered.
Playbooks 07, 08, 04 and the glossary: no ready mark; the review record is a Reviewed-by: line in the pull request; the Approve is asked once the checks pass (ADR 0421).
Playbook 07: a fixing agent never runs an integration test locally; the prepare step splits an issue sized over an hour; a change the new merge script must judge ships the script first; reports every ten minutes (the operator, 2026-10-17).
Design 47: milestone 3's unit bound only; the integration bound is issue 1055.
Reviewed-by: review-m3@shanks at 64e357da7d (round 1 approved the first commit; the four later commits are read in round 2)
Design 47 milestone 3, with mesh-controller and mesh-catalog on the same branch name; the text becomes true when their change is delivered.
- Playbooks 07, 08, 04 and the glossary: no ready mark; the review record is a `Reviewed-by:` line in the pull request; the Approve is asked once the checks pass (ADR 0421).
- Playbook 07: a fixing agent never runs an integration test locally; the prepare step splits an issue sized over an hour; a change the new merge script must judge ships the script first; reports every ten minutes (the operator, 2026-10-17).
- Design 47: milestone 3's unit bound only; the integration bound is issue 1055.
Reviewed-by: review-m3@shanks at 64e357da7d7e8a68325329f8fb7ff9ed101165da (round 1 approved the first commit; the four later commits are read in round 2)
mesh/merge-gate head 64e357da7d7e merged into trunk a6db6a70cffa beside mesh-catalog#352@07717974 +1 more — pass: the change touches no module of the mesh'…
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Transitions
2026-10-17 19:41 (new) → proposed (announced): novox/hq#413's head announced
2026-10-17 19:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 19:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 20:02 ready → proposed (recheck): the merge tool's check ask at 22:00 is not in the build queue (queue empty at 22:03) and never answered; the merge is refused waiting for it since the operator's Approve at 22:00:12
2026-10-17 20:03 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 20:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 20:10 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 20:10 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@64e357da7d7e` — **delivered** since 2026-10-17T20:10:59Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Group** `feat/one-group-one-plan`, in order: novox/hq@64e357da7d7e → novox/mesh-controller@2d24fbb71611 → novox/mesh-catalog@0771797431ed
- novox/mesh-controller@2d24fbb71611 before novox/mesh-catalog@0771797431ed: built by
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Transitions**
- 2026-10-17 19:41 (new) → proposed (announced): novox/hq#413's head announced
- 2026-10-17 19:51 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 19:51 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 20:02 ready → proposed (recheck): the merge tool's check ask at 22:00 is not in the build queue (queue empty at 22:03) and never answered; the merge is refused waiting for it since the operator's Approve at 22:00:12
- 2026-10-17 20:03 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 20:03 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 20:10 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 20:10 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-m3@shanks: milestone 3 review round 2 APPROVE: playbooks 07, 08 without the ready mark; script first; split issues; reports every ten minutes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at 64e357da7d7e8a68325329f8fb7ff9ed101165da
Reviewed by review-m3@shanks: milestone 3 review round 2 APPROVE: playbooks 07, 08 without the ready mark; script first; split issues; reports every ten minutes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
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.
Design 47 milestone 3, with mesh-controller and mesh-catalog on the same branch name; the text becomes true when their change is delivered.
Reviewed-by:line in the pull request; the Approve is asked once the checks pass (ADR 0421).Reviewed-by: review-m3@shanks at
64e357da7d(round 1 approved the first commit; the four later commits are read in round 2)Delivery
novox/hq@64e357da7d7e— delivered since 2026-10-17T20:10:59ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Group
feat/one-group-one-plan, in order: novox/hq@64e357da7d → novox/mesh-controller@2d24fbb716 → novox/mesh-catalog@0771797431Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.ready at
64e357da7dReviewed by review-m3@shanks: milestone 3 review round 2 APPROVE: playbooks 07, 08 without the ready mark; script first; split issues; reports every ten minutes. Marked through mesh-delivery.mark-ready (novox/hq issue 913).