Issues 285, 286, 287, 288: the merge gate judged nothing; the seat's check disagreed with agents' machines; a seat and a module of one name were unreachable; the facts still name the installation #161

2026-10-06T23:43:04Z

mesh-admin commented

2026-10-06 23:43:04 +00:00

Renumbered from 282-284, because 282 was taken on main by #160. The branch name keeps the old numbers.

285 (located): every gated check said PASS with 0 of 4 machines composing, with the change and without. The gate raised bus credentials without their accounts, no outward links, and settings judged one layer at a time. A baseline that does not compose is now an error, never a pass. Fix: mesh-controller#104.
286 (located): merge-check.sh passed on agents' machines and failed on the build seat. The causes were the toolchain's older gofmt, siblings at a feature branch instead of the running commit, and a different user. mesh-controller check-here now runs a check exactly as the seat does. Fix: mesh-controller#104, mesh-host#46. Left open: a delivery group's members' own scripts still run without the other heads beside them.
287 (located): the console listed the seat mesh-delivery with no verbs, and refused every address with that name, the module's tools included. Fix: mesh-tools#19.
288 (located): the facts snapshot still named the forge's address in every repository, and carries owners, whole manifests and a login in a setting. Repositories are now owner/repo (mesh-controller#105); the rest is left open for the design.

records/index/cycle pass. Role names only.

Renumbered from 282-284, because 282 was taken on main by #160. The branch name keeps the old numbers. - **285** (located): every gated check said PASS with 0 of 4 machines composing, with the change and without. The gate raised bus credentials without their accounts, no outward links, and settings judged one layer at a time. A baseline that does not compose is now an error, never a pass. Fix: mesh-controller#104. - **286** (located): `merge-check.sh` passed on agents' machines and failed on the build seat. The causes were the toolchain's older gofmt, siblings at a feature branch instead of the running commit, and a different user. `mesh-controller check-here` now runs a check exactly as the seat does. Fix: mesh-controller#104, mesh-host#46. Left open: a delivery group's members' own scripts still run without the other heads beside them. - **287** (located): the console listed the seat `mesh-delivery` with no verbs, and refused every address with that name, the module's tools included. Fix: mesh-tools#19. - **288** (located): the facts snapshot still named the forge's address in every repository, and carries owners, whole manifests and a login in a setting. Repositories are now `owner/repo` (mesh-controller#105); the rest is left open for the design. records/index/cycle pass. Role names only.

mesh-admin commented

2026-10-06 23:43:28 +00:00

Delivery novox/hq@a9f396a0a039 — delivered since 2026-10-07T00:28:18Z

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

Transitions

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

jschoubben added 2 commits 2026-10-07 00:04:49 +00:00

Issues 282-284: the merge gate judged nothing, the seat's check disagreed with agents' machines, a seat and a module of one name were unreachable 41a0e77748

Renumber the gate's issues 285-287 (282 was taken on main); issue 288: the facts snapshot still names the installation

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

mesh/delivery delivered

Details

a9f396a0a0

jschoubben force-pushed issues/282-284-the-merge-gate-judged-nothing from f2fd8229b4 to a9f396a0a0

2026-10-07 00:04:49 +00:00

Compare

mesh-admin changed title from ~~Issues 282, 283, 284: the merge gate judged nothing; the seat's check disagreed with agents' machines; a seat and a module of one name were unreachable~~ to Issues 285, 286, 287, 288: the merge gate judged nothing; the seat's check disagreed with agents' machines; a seat and a module of one name were unreachable; the facts still name the installation

2026-10-07 00:04:56 +00:00

mesh-admin merged commit 7d57ace896 into main

2026-10-07 00:28:01 +00:00

mesh-admin deleted branch issues/282-284-the-merge-gate-judged-nothing

2026-10-07 00:28:01 +00:00

mesh-admin referenced this pull request

2026-10-09 11:51:19 +00:00

Issue 348: a resolver that stopped answering ran on unnoticed, and builds sent after it were blamed #249

mesh-admin referenced this pull request

2026-10-14 21:18:17 +00:00

ADR 0280: the resolver restarts itself when it stops answering, braked and said as its health (issue 348) #284

mesh-admin referenced this pull request