mesh-issues: a verdict naming issue 0 is none, and the tracker's own module is a registered owner (issue 396) #186

Merged
mesh-admin merged 2 commits from fix/triage-issue-zero-is-none into main 2026-10-10 17:22:25 +00:00
Contributor

Issue 396 (tracker). Seen live on test issue 395: the model answered related with issue 0 (its way of saying none) and the triage failed the issue as 'names an issue not offered'.

  • groom.go: a duplicate/related verdict with issue 0 is read as none (not a failure; nothing linked). A verdict naming a real issue not offered still fails, unchanged (hq ADR 0278 §2).
  • module.json: mesh-catalog modules/mesh-issues added to the registered owners (sorted), so an issue can be located in the tracker itself.
  • Test TestAVerdictNamingIssueZeroIsNone.

Reviewer checklist: unchanged rule for unoffered non-zero issues; no new verb or event; settings default only gains one owner.

Issue 396 (tracker). Seen live on test issue 395: the model answered `related` with issue 0 (its way of saying none) and the triage failed the issue as 'names an issue not offered'. - groom.go: a duplicate/related verdict with issue 0 is read as none (not a failure; nothing linked). A verdict naming a real issue not offered still fails, unchanged (hq ADR 0278 §2). - module.json: `mesh-catalog modules/mesh-issues` added to the registered owners (sorted), so an issue can be located in the tracker itself. - Test TestAVerdictNamingIssueZeroIsNone. Reviewer checklist: unchanged rule for unoffered non-zero issues; no new verb or event; settings default only gains one owner.
mesh-admin added 1 commit 2026-10-10 16:28:00 +00:00
mesh-issues: a verdict naming issue 0 is none, and the tracker's own module is a registered owner (issue 396)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
6bd69ebadc
The model says 'no issue' as related to 0; the triage took that as an issue not
offered and failed the issue instead of triaging it.
Author
Contributor

Delivery novox/mesh-catalog@383194488ba8 — delivered since 2026-10-10T17:32:08Z

Delivery plan — builds mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues

Machines

  • mesh-issues on novox: passed — healthy 3 times over 2m21s
  • mesh-issues on the rest running it: sent

Transitions

  • 2026-10-10 16:29 (new) → proposed (announced): novox/mesh-catalog#186's head announced
  • 2026-10-10 16:31 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 16:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 17: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-10 17:28 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-10 17:32 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@383194488ba8` — **delivered** since 2026-10-10T17:32:08Z **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues **Machines** - mesh-issues on novox: passed — healthy 3 times over 2m21s - mesh-issues on the rest running it: sent **Transitions** - 2026-10-10 16:29 (new) → proposed (announced): novox/mesh-catalog#186's head announced - 2026-10-10 16:31 proposed → checked (checked): the verdict names this commit - 2026-10-10 16:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 17: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-10 17:28 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-10 17:32 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-10 16:28:48 +00:00
mesh-issues: only a duplicate or related verdict naming 0 is none (review, issue 396)
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery delivered
383194488b
Author
Contributor

Merge check at 6bd69eba

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues
  • read by no module's build: modules/mesh-issues/cmd/mesh-issues/triage_test.go

Run by the build seat on novox as build-1791649685376551644 (builds --log build-1791649685376551644).

--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:19:15Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T16:19:15Z

modules the change moves:
  - mesh-issues (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.020s
words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.013s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.007s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	6.401s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `6bd69eba` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/mesh-issues/cmd/mesh-issues/triage_test.go Run by the build seat on novox as `build-1791649685376551644` (`builds --log build-1791649685376551644`). ``` --- the gate: mesh-issues mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:19:15Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-10T16:19:15Z modules the change moves: - mesh-issues (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.020s words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.013s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.007s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 6.401s --- its merge-check-typescript.sh (typescript toolchain) ```
Author
Contributor

Merge check at 38319448

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-issues → novox; no bus step

  • tier 0: mesh-issues
  • novox: receives mesh-issues
  • read by no module's build: modules/mesh-issues/cmd/mesh-issues/triage_test.go

Run by the build seat on g14 as build-1791649747312376820 (builds --log build-1791649747312376820).

--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:29:15Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-10T16:29:15Z

modules the change moves:
  - mesh-issues (changed)

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues

notes:
  - modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.011s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 69, as kept
testing modules/mesh-issues
ok  	mesh-issues/cmd/mesh-issues	6.189s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `38319448` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-issues) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-issues → novox; no bus step - tier 0: mesh-issues - novox: receives mesh-issues - read by no module's build: modules/mesh-issues/cmd/mesh-issues/triage_test.go Run by the build seat on g14 as `build-1791649747312376820` (`builds --log build-1791649747312376820`). ``` --- the gate: mesh-issues mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, keeps state issues, counters, grooming long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-10T16:29:15Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-10T16:29:15Z modules the change moves: - mesh-issues (changed) machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-issues notes: - modules/mesh-issues/cmd/mesh-issues/triage_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 38989 strings of 649 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.011s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 69, as kept testing modules/mesh-issues ok mesh-issues/cmd/mesh-issues 6.189s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-admin merged commit 63412ec36a into main 2026-10-10 17:22:25 +00:00
mesh-admin deleted branch fix/triage-issue-zero-is-none 2026-10-10 17:22:25 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#186