Issue 305: a recheck left the old verdict standing #190

2026-10-08T08:12:59Z

mesh-admin commented

2026-10-08 08:12:59 +00:00

Registers issue 305 (playbook 03), resolved by novox/mesh-catalog#118 with replay R305 (novox/mesh-lab#62, proved: fails before the fix, passes on it). Core (located in the catalogue's forge holder and the delivery's owner). A recheck now puts mesh/merge-gate and mesh/repo-check back to pending before the check is asked, so the forge refuses the merge until the fresh verdict lands. cycle, records, index and words pass.

Registers issue 305 (playbook 03), resolved by novox/mesh-catalog#118 with replay R305 (novox/mesh-lab#62, proved: fails before the fix, passes on it). Core (located in the catalogue's forge holder and the delivery's owner). A recheck now puts `mesh/merge-gate` and `mesh/repo-check` back to pending before the check is asked, so the forge refuses the merge until the fresh verdict lands. cycle, records, index and words pass.

mesh-admin added 1 commit 2026-10-08 08:13:00 +00:00

Issue 305: a recheck must put the merge check back to pending, or the old verdict merges

mesh/delivery delivered

Details

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed

Details

573a44a33d

mesh-admin commented

2026-10-08 08:13:30 +00:00

Delivery novox/hq@573a44a33d70 — delivered since 2026-10-08T08:35:02Z

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

Transitions

2026-10-08 08:13 (new) → proposed (announced): novox/hq#190's head announced
2026-10-08 08:13 proposed → checked (checked): the verdict names this commit
2026-10-08 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 08:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 08:35 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@573a44a33d70` — **delivered** since 2026-10-08T08:35:02Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-08 08:13 (new) → proposed (announced): novox/hq#190's head announced - 2026-10-08 08:13 proposed → checked (checked): the verdict names this commit - 2026-10-08 08:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-08 08:35 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-08 08:35 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-admin merged commit 879b183268 into main

2026-10-08 08:34:30 +00:00

mesh-admin deleted branch issues/305-a-recheck-left-the-old-verdict-standing

2026-10-08 08:34:30 +00:00

mesh-admin referenced this pull request

2026-10-09 23:03:59 +00:00

Issue 361: the control-node's agent account is never judged, because its search for setuid programs cannot finish in fifteen minutes #261

mesh-tools referenced this pull request

2026-11-11 09:08:14 +00:00

Design 25: the grants part takes a first view of the bus module's bindings at every start, so a missed created event is recovered (issue 1966) #543

mesh-tools referenced this pull request

2026-11-13 01:07:25 +00:00