Lesson from issue 1025's first check (mesh-controller #369, 2026-10-17), playbook 08:
Phase 3 step 3: a failed check is read from its whole log (mesh-delivery.show gives the build id, mesh-controller.builds with log prints it), never reasoned from the summary, which showed a store test's FAIL without its cause.
A change to merge-check.sh is judged by main's version, so a test the change adds runs a file of its own, not merge-check.sh.
Checks: sh merge-check.sh green locally.
Lesson from issue 1025's first check (mesh-controller #369, 2026-10-17), playbook 08:
- Phase 3 step 3: a failed check is read from its whole log (`mesh-delivery.show` gives the build id, `mesh-controller.builds` with `log` prints it), never reasoned from the summary, which showed a store test's FAIL without its cause.
- A change to `merge-check.sh` is judged by main's version, so a test the change adds runs a file of its own, not `merge-check.sh`.
Checks: `sh merge-check.sh` green locally.
Deliverynovox/hq@06440c152298 — delivered since 2026-10-17T15:58:27Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-17 15:56 (new) → proposed (announced): novox/hq#405's head announced
2026-10-17 15:57 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-17 15:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-17 15:58 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 15:58 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@06440c152298` — **delivered** since 2026-10-17T15:58:27Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-17 15:56 (new) → proposed (announced): novox/hq#405's head announced
- 2026-10-17 15:57 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-17 15:57 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-17 15:58 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 15:58 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 reviewer-1025@shanks: playbook 07 phase 3 step 3: read the whole log, merge-check.sh judged by main's version; matches what happened on #369, no disclosure, words hold. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at 0e7eb9c2dac8d0d3b9cd661f96f043922fb5cc25
Reviewed by reviewer-1025@shanks: playbook 07 phase 3 step 3: read the whole log, merge-check.sh judged by main's version; matches what happened on #369, no disclosure, words hold. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-delivery: not merged. This pull request is marked ready at 0e7eb9c2da, and its check failed: the change touches no module of the mesh's graph (head 0e7eb9c2da merged into trunk cf73f96797). A new head, marked ready once reviewed, or a recheck that passes, merges it.
mesh-delivery: **not merged.** This pull request is marked ready at 0e7eb9c2dac8d0d3b9cd661f96f043922fb5cc25, and its check failed: the change touches no module of the mesh's graph (head 0e7eb9c2dac8 merged into trunk cf73f9679771). A new head, marked ready once reviewed, or a recheck that passes, merges it.
Merge check at 0e7eb9c2
Judged: head 0e7eb9c2dac8 merged into trunk cf73f9679771; read beside it: mesh-catalog 0d2fc5e4d79c, mesh-controller b8c810a3499c, mesh-controller-main b8c810a3499c, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: FAIL — its merge-check.sh failed: words: 1 problem(s)
Run by the build seat on ace as build-1792250993048890842 (builds --log build-1792250993048890842).
--- its merge-check.sh (go toolchain)
records: all checks passed
index: 6 topics in the reading order, no stored list
cycle: 440 documents checked, the chain holds
NOT COMPARED: MESH_CATALOG_DIR is not set, so the catalogue's copy of the list was not read
00-META/process/07-feature-branches.md:148: 'build machine' is retired (glossary)
words: 1 problem(s)
**Merge check** at `0e7eb9c2`
Judged: head `0e7eb9c2dac8` merged into trunk `cf73f9679771`; read beside it: mesh-catalog `0d2fc5e4d79c`, mesh-controller `b8c810a3499c`, mesh-controller-main `b8c810a3499c`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5`
- `mesh/merge-gate`: **PASS** — the change touches no module of the mesh's graph
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: words: 1 problem(s)
Run by the build seat on ace as `build-1792250993048890842` (`builds --log build-1792250993048890842`).
```
--- its merge-check.sh (go toolchain)
records: all checks passed
index: 6 topics in the reading order, no stored list
cycle: 440 documents checked, the chain holds
NOT COMPARED: MESH_CATALOG_DIR is not set, so the catalogue's copy of the list was not read
00-META/process/07-feature-branches.md:148: 'build machine' is retired (glossary)
words: 1 problem(s)
```
Merge check at 0e7eb9c2
Judged: head 0e7eb9c2dac8 merged into trunk cf73f9679771; read beside it: mesh-catalog 0d2fc5e4d79c, mesh-controller b8c810a3499c, mesh-controller-main b8c810a3499c, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5
mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: FAIL — its merge-check.sh failed: words: 1 problem(s)
Run by the build seat on ace as build-1792251020361637853 (builds --log build-1792251020361637853).
--- its merge-check.sh (go toolchain)
records: all checks passed
index: 6 topics in the reading order, no stored list
cycle: 440 documents checked, the chain holds
NOT COMPARED: MESH_CATALOG_DIR is not set, so the catalogue's copy of the list was not read
00-META/process/07-feature-branches.md:148: 'build machine' is retired (glossary)
words: 1 problem(s)
**Merge check** at `0e7eb9c2`
Judged: head `0e7eb9c2dac8` merged into trunk `cf73f9679771`; read beside it: mesh-catalog `0d2fc5e4d79c`, mesh-controller `b8c810a3499c`, mesh-controller-main `b8c810a3499c`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5`
- `mesh/merge-gate`: **PASS** — the change touches no module of the mesh's graph
- `mesh/repo-check`: **FAIL** — its merge-check.sh failed: words: 1 problem(s)
Run by the build seat on ace as `build-1792251020361637853` (`builds --log build-1792251020361637853`).
```
--- its merge-check.sh (go toolchain)
records: all checks passed
index: 6 topics in the reading order, no stored list
cycle: 440 documents checked, the chain holds
NOT COMPARED: MESH_CATALOG_DIR is not set, so the catalogue's copy of the list was not read
00-META/process/07-feature-branches.md:148: 'build machine' is retired (glossary)
words: 1 problem(s)
```
Reviewed by reviewer-1025@shanks: one-line fix drops the retired word 'build machine' for the glossary's description of the builder; content as approved at 0e7eb9c2. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
ready at 06440c15229821fa53335166ed899bdc11989306
Reviewed by reviewer-1025@shanks: one-line fix drops the retired word 'build machine' for the glossary's description of the builder; content as approved at 0e7eb9c2. 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.
Lesson from issue 1025's first check (mesh-controller #369, 2026-10-17), playbook 08:
mesh-delivery.showgives the build id,mesh-controller.buildswithlogprints it), never reasoned from the summary, which showed a store test's FAIL without its cause.merge-check.shis judged by main's version, so a test the change adds runs a file of its own, notmerge-check.sh.Checks:
sh merge-check.shgreen locally.Delivery
novox/hq@06440c152298— delivered since 2026-10-17T15:58:27ZDelivery 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.ready at
0e7eb9c2daReviewed by reviewer-1025@shanks: playbook 07 phase 3 step 3: read the whole log, merge-check.sh judged by main's version; matches what happened on #369, no disclosure, words hold. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-delivery: not merged. This pull request is marked ready at
0e7eb9c2da, and its check failed: the change touches no module of the mesh's graph (head0e7eb9c2damerged into trunkcf73f96797). A new head, marked ready once reviewed, or a recheck that passes, merges it.Merge check at
0e7eb9c2Judged: head
0e7eb9c2dac8merged into trunkcf73f9679771; read beside it: mesh-catalog0d2fc5e4d79c, mesh-controllerb8c810a3499c, mesh-controller-mainb8c810a3499c, mesh-hostcd13f7726ef0, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: FAIL — its merge-check.sh failed: words: 1 problem(s)Run by the build seat on ace as
build-1792250993048890842(builds --log build-1792250993048890842).Merge check at
0e7eb9c2Judged: head
0e7eb9c2dac8merged into trunkcf73f9679771; read beside it: mesh-catalog0d2fc5e4d79c, mesh-controllerb8c810a3499c, mesh-controller-mainb8c810a3499c, mesh-hostcd13f7726ef0, mesh-tools7412c5b6c9c5mesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: FAIL — its merge-check.sh failed: words: 1 problem(s)Run by the build seat on ace as
build-1792251020361637853(builds --log build-1792251020361637853).ready at
06440c1522Reviewed by reviewer-1025@shanks: one-line fix drops the retired word 'build machine' for the glossary's description of the builder; content as approved at
0e7eb9c2. Marked through mesh-delivery.mark-ready (novox/hq issue 913).