Design 47: milestone 4 delivered; a fix of milestone 3 comes next. Playbook 07: new integration tests are read against the code before the first push (issues 980, 1082)
#415
Merged
mesh-toolsmerged 2 commits from feat/milestone-4-delivered into main2026-10-17 22:32:36 +00:00
Design 47. Milestone 4's row names the split of issue 980 into 1065-1068 (all delivered and resolved 2026-10-18). A new row "3 fix" (issues 1082, 1049, 1047, 1083, 1084), put after milestone 4 and before milestone 5 by the operator on 2026-10-18, with a sentence on milestone 3's first live group: one Approve held, but it merged in two passes and went out in two delivery plans.
Playbook 07. A review step 4: every new integration test is read against the code it drives before the first push, since its first run is otherwise the merge check (2026-10-17: two failed runs, and reading found a third fault). Steps 4-5 renumbered 5-6.
- **Design 47.** Milestone 4's row names the split of issue 980 into 1065-1068 (all delivered and resolved 2026-10-18). A new row "3 fix" (issues 1082, 1049, 1047, 1083, 1084), put after milestone 4 and before milestone 5 by the operator on 2026-10-18, with a sentence on milestone 3's first live group: one Approve held, but it merged in two passes and went out in two delivery plans.
- **Playbook 07.** A review step 4: every new integration test is read against the code it drives before the first push, since its first run is otherwise the merge check (2026-10-17: two failed runs, and reading found a third fault). Steps 4-5 renumbered 5-6.
hq's four checks pass locally.
Reviewed-by: review@shanks at c10efa4d8c8f82e10a422544acc4f4716154a041
Deliverynovox/hq@c10efa4d8c8f — delivered since 2026-10-17T22:32:38Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-17 22:31 (new) → proposed (announced): novox/hq#415's head announced
2026-10-17 22:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 22:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 22:32 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 22:32 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@c10efa4d8c8f` — **delivered** since 2026-10-17T22:32:38Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-17 22:31 (new) → proposed (announced): novox/hq#415's head announced
- 2026-10-17 22:31 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 22:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 22:32 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 22:32 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`.
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.
hq's four checks pass locally.
Reviewed-by: review@shanks at
c10efa4d8cDelivery
novox/hq@c10efa4d8c8f— delivered since 2026-10-17T22:32:38ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.