Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086) #417

2026-10-18T00:20:46Z

mesh-tools commented

2026-10-18 00:20:46 +00:00

Step 2 item 4 of playbook 07 gains one sentence: the reviewer also checks that each new integration test enters through the same path the live trigger takes, not a state the test writes by hand.

Why: milestone 4 of design 47 had an integration test that saved its delivery plan directly. Every live plan is cut from a batch of merges instead, so the test skipped that path and passed while the backup step never ran (issue 1086, fixed by mesh-controller #377).

hq's own merge-check.sh passes locally; an independent reviewer (larger model, round 1) approved the commit.

Reviewed-by: reviewer-1086-playbook@shanks at 17c27ddf83

Step 2 item 4 of playbook 07 gains one sentence: the reviewer also checks that each new integration test enters through the same path the live trigger takes, not a state the test writes by hand. Why: milestone 4 of design 47 had an integration test that saved its delivery plan directly. Every live plan is cut from a batch of merges instead, so the test skipped that path and passed while the backup step never ran (issue 1086, fixed by mesh-controller #377). hq's own merge-check.sh passes locally; an independent reviewer (larger model, round 1) approved the commit. Reviewed-by: reviewer-1086-playbook@shanks at 17c27ddf834f0d4d173664c89152cab6223b6f73

mesh-tools added 1 commit 2026-10-18 00:20:46 +00:00

Playbook 07: a new integration test enters through the path the live trigger takes (issue 1086)

mesh/merge-gate head 17c27ddf834f merged into trunk 5c6b645c6ba9 — pass: the change touches no module of the mesh's graph

Details

mesh/repo-check head 17c27ddf834f merged into trunk 5c6b645c6ba9 — pass: its merge-check.sh passed

Details

mesh/delivery delivered

Details

17c27ddf83

Milestone 4's test saved its plan by hand, skipped the cut from a batch, and passed while the backup step never ran.

mesh-tools commented

2026-10-18 00:20:50 +00:00

Delivery novox/hq@17c27ddf834f — delivered since 2026-10-18T00:23:23Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-18 00:20 (new) → proposed (announced): novox/hq#417's head announced
2026-10-18 00:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-18 00:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-18 00:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-18 00:23 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.

**Delivery** `novox/hq@17c27ddf834f` — **delivered** since 2026-10-18T00:23:23Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-18 00:20 (new) → proposed (announced): novox/hq#417's head announced - 2026-10-18 00:21 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-18 00:21 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-18 00:23 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-18 00:23 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-tools merged commit f82a90dfa0 into main

2026-10-18 00:23:21 +00:00

mesh-tools deleted branch fix/1086-test-enters-live-path

2026-10-18 00:23:21 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#417