Fixes novox/hq issue 483. Decision: hq ADR 0294 (proposed in novox/hq#313; supersedes ADR 0281 in part). Do not merge before ADR 0294 is accepted.
Cause found. The tracker measured delivery only for fixed-by. Agents link the pull request (link kind pull-request) while the issue is in fixing and give fixed-by only when they resolve it (as on issue 457), so the 13 issues the operator found were never measured, and nothing said that one was left in fixing.
What changes (modules/mesh-issues only):
An issue's fixes are its fixed-by and its linked pull requests. They feed the delivery line, FixState, the ready-to-verify note, the stuck-fix sweep and the asks. Readiness of dependent issues still reads fixed-by alone. Each sweep asks mesh-delivery for at most 5 fixes never heard of.
Merged is read from the pull request, not the state. It comes from the transition's merged_as, or pull.merged in checks. A pull request that is stopped and was never merged (closed unmerged) is withdrawn: it is not stuck, not delivered and not open. The delivery line says "fix withdrawn: ..." when it is the only fix. (Review point 1.)
The ready-to-verify note names each fix with when it was delivered, and the worker. The event gains worker and delivered-at. No channel of the tracker reaches a worker, so the note and the event are how the worker hears.
Delivered, not resolved: an issue in fixing with every fix delivered. Past the setting delivered-not-resolved-after (default 1h), the sweep warns the operator's channel once:
summary "issue N: fixed and delivered, not resolved; works on it".
It clears at the issue's moved, or at the next sweep. This uses the operator's channel, like the stuck-fix warning, because a module that runs only its bundle cannot raise a controller condition (ADR 0240 rule 8, ADR 0256).
Abandoned: an issue in diagnosing or fixing whose worker is stale (worker-stale-after, 24h) and that has no open pull request. get and list rows carry abandoned. A move by someone else takes it over without a reason, and the answer, the note and the moved event say abandoned. The issue's word "stale claim" is not used, because the glossary keeps claim for a module on a seat.
list takes flag:delivered-not-resolved or abandoned.
Comments cite ADR 0284 for the worker rules, with its section numbers. They cited 0283, which is a different decision.
No store schema change: there is a new optional key on the issue's JSON value (not-resolved-open), and the new setting's default is in module.json.
TestAPullRequestClosedUnmergedIsWithdrawn (through a transition and through checks) was committed in 601eed0, before its fix in 3aaccba. On the previous head d81e7d0 it failed: the tracker told the operator "merged 26h ago, not delivered".
TestOnePullRequestLinkedToSeveralIssues guards the per-issue warning and clearing; it already passed on d81e7d0.
go vet ./..., go test -race ./... -count=1 and the words check pass.
On roll-out: the sweep measures the linked pull requests of today's issues in fixing, five every five minutes, and warns once for each issue delivered and not resolved past an hour. Expect several warnings in the first half hour. A fix recorded as merged from the state stopped before this change stays recorded that way until its delivery says something new.
Not touched: modules/docker (#205), modules/restic (#210).
Fixes novox/hq issue 483. **Decision: hq ADR 0294** (proposed in novox/hq#313; supersedes ADR 0281 in part). Do not merge before ADR 0294 is accepted.
**Cause found.** The tracker measured delivery only for `fixed-by`. Agents link the pull request (link kind `pull-request`) while the issue is in fixing and give `fixed-by` only when they resolve it (as on issue 457), so the 13 issues the operator found were never measured, and nothing said that one was left in fixing.
**What changes** (modules/mesh-issues only):
1. **An issue's fixes are its `fixed-by` and its linked pull requests.** They feed the delivery line, `FixState`, the ready-to-verify note, the stuck-fix sweep and the asks. Readiness of dependent issues still reads `fixed-by` alone. Each sweep asks mesh-delivery for at most 5 fixes never heard of.
2. **Merged is read from the pull request, not the state.** It comes from the transition's `merged_as`, or `pull.merged` in `checks`. A pull request that is `stopped` and was never merged (closed unmerged) is **withdrawn**: it is not stuck, not delivered and not open. The delivery line says "fix withdrawn: ..." when it is the only fix. (Review point 1.)
3. **The ready-to-verify note names each fix with when it was delivered, and the worker.** The event gains `worker` and `delivered-at`. No channel of the tracker reaches a worker, so the note and the event are how the worker hears.
4. **Delivered, not resolved:** an issue in fixing with every fix delivered. Past the setting `delivered-not-resolved-after` (default `1h`), the sweep warns the operator's channel once:
- key `issue-tracker.delivered-not-resolved.<number>`;
- summary "issue N: fixed and delivered, not resolved; <worker> works on it".
It clears at the issue's `moved`, or at the next sweep. This uses the operator's channel, like the stuck-fix warning, because a module that runs only its bundle cannot raise a controller condition (ADR 0240 rule 8, ADR 0256).
5. **Abandoned:** an issue in diagnosing or fixing whose worker is stale (`worker-stale-after`, `24h`) and that has no open pull request. `get` and list rows carry `abandoned`. A move by someone else takes it over without a reason, and the answer, the note and the `moved` event say `abandoned`. The issue's word "stale claim" is not used, because the glossary keeps *claim* for a module on a seat.
6. **`list` takes `flag`:** `delivered-not-resolved` or `abandoned`.
7. **Comments cite ADR 0284 for the worker rules**, with its section numbers. They cited 0283, which is a different decision.
No store schema change: there is a new optional key on the issue's JSON value (`not-resolved-open`), and the new setting's default is in module.json.
**Tests** (`claims_test.go`):
- Six tests, committed in c4ea58a, fail on main.
- `TestAPullRequestClosedUnmergedIsWithdrawn` (through a transition and through `checks`) was committed in 601eed0, before its fix in 3aaccba. On the previous head d81e7d0 it failed: the tracker told the operator "merged 26h ago, not delivered".
- `TestOnePullRequestLinkedToSeveralIssues` guards the per-issue warning and clearing; it already passed on d81e7d0.
`go vet ./...`, `go test -race ./... -count=1` and the words check pass.
**On roll-out**: the sweep measures the linked pull requests of today's issues in fixing, five every five minutes, and warns once for each issue delivered and not resolved past an hour. Expect several warnings in the first half hour. A fix recorded as merged from the state `stopped` before this change stays recorded that way until its delivery says something new.
Not touched: modules/docker (#205), modules/restic (#210).
Each test fails on main: a linked pull request is never measured, nothing
warns of a delivered fix left in fixing, and list has no flag to find either.
The operator found 13 issues in fixing whose fix was delivered hours before:
their pull requests were linked, not in fixed-by, so their delivery was never
measured, and nothing said an issue left there or a worker gone.
Deliverynovox/mesh-catalog@d6148a5ba797 — delivered since 2026-10-11T16:58:09Z
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 2m30s
mesh-issues on the rest running it: sent
Transitions
2026-10-11 10:27 (new) → proposed (announced): novox/mesh-catalog#212's head announced
2026-10-11 10:30 proposed → checked (checked): the verdict names this commit
2026-10-11 10:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 16:47 ready → proposed (recheck): Its checks (12:30 local) judged an older catalogue main; mesh-issues changed since (#214, #216). ADR 0294 is now accepted, so #212 is checked against today's main before it merges.
2026-10-11 16:50 proposed → checked (checked): the verdict names this commit
2026-10-11 16:50 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 16:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 16:54 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-11 16:58 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@d6148a5ba797` — **delivered** since 2026-10-11T16:58:09Z
**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 2m30s
- mesh-issues on the rest running it: sent
**Transitions**
- 2026-10-11 10:27 (new) → proposed (announced): novox/mesh-catalog#212's head announced
- 2026-10-11 10:30 proposed → checked (checked): the verdict names this commit
- 2026-10-11 10:30 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 16:47 ready → proposed (recheck): Its checks (12:30 local) judged an older catalogue main; mesh-issues changed since (#214, #216). ADR 0294 is now accepted, so #212 is checked against today's main before it merges.
- 2026-10-11 16:50 proposed → checked (checked): the verdict names this commit
- 2026-10-11 16:50 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 16:54 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 16:54 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-11 16:58 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/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/README.md, modules/mesh-issues/cmd/mesh-issues/claims_test.go
Run by the build seat on g14 as build-1791713865171920607 (builds --log build-1791713865171920607).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:15:21Z 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-11T10:15:21Z
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/README.md and modules/mesh-issues/cmd/mesh-issues/claims_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.004s
words: 12 retired words and 70 daemons' lines, none in the 41484 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
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 8.385s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d81e7d06`
- `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/README.md, modules/mesh-issues/cmd/mesh-issues/claims_test.go
Run by the build seat on g14 as `build-1791713865171920607` (`builds --log build-1791713865171920607`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:15:21Z 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-11T10:15:21Z
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/README.md and modules/mesh-issues/cmd/mesh-issues/claims_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.004s
words: 12 retired words and 70 daemons' lines, none in the 41484 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.009s
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 8.385s
--- its merge-check-typescript.sh (typescript toolchain)
```
mesh-delivery says stopped for a pull request closed unmerged too; read as
merged, it was said stuck to the operator for good. Cite ADR 0284 for the
worker rules, which the comments gave as 0283.
The glossary keeps claim for a module's on a seat.
mesh-admin
changed title from mesh-issues: say a delivered fix left in fixing, and flag a stale claim (hq issue 483) to mesh-issues: say a delivered fix left in fixing, and flag an abandoned issue (hq issue 483, ADR 0294)2026-10-11 10:27:24 +00:00
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on novox as build-1791714291447068493 (builds --log build-1791714291447068493).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:15:21Z 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-11T10:15:21Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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.003s
words: 12 retired words and 70 daemons' lines, none in the 41483 strings of 673 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.006s
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 8.813s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `3aaccba4`
- `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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on novox as `build-1791714291447068493` (`builds --log build-1791714291447068493`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:15:21Z 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-11T10:15:21Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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.003s
words: 12 retired words and 70 daemons' lines, none in the 41483 strings of 673 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.006s
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 8.813s
--- its merge-check-typescript.sh (typescript toolchain)
```
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on g14 as build-1791714443784435577 (builds --log build-1791714443784435577).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:25:21Z 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-11T10:25:21Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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.003s
words: 12 retired words and 70 daemons' lines, none in the 41483 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
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 8.295s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d6148a5b`
- `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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on g14 as `build-1791714443784435577` (`builds --log build-1791714443784435577`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T10:25:21Z 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-11T10:25:21Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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.003s
words: 12 retired words and 70 daemons' lines, none in the 41483 strings of 673 files
ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.012s
agent-home: no archive and no file written into under the agent's home
ok git.novox.be/novox/mesh-catalog/checks/paths 0.006s
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 8.295s
--- its merge-check-typescript.sh (typescript toolchain)
```
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on novox as build-1791737244429439346 (builds --log build-1791737244429439346).
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T16:22:35Z 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-11T16:22:35Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 41483 strings of 673 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.006s
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.691s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `d6148a5b`
- `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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go, modules/mesh-issues/cmd/mesh-issues/worker_test.go
Run by the build seat on novox as `build-1791737244429439346` (`builds --log build-1791737244429439346`).
```
--- the gate: mesh-issues
mesh-issues: ok, invokes claude-code.claude_code_judge, seat:mesh-delivery.checks, seat:operator-channel.notify, records.records_status, records.records_list, records.records_read, keeps state issues, counters, grooming, reservations
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-11T16:22:35Z 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-11T16:22:35Z
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/README.md, modules/mesh-issues/cmd/mesh-issues/bus_test.go, modules/mesh-issues/cmd/mesh-issues/claims_test.go, modules/mesh-issues/cmd/mesh-issues/memory_test.go, modules/mesh-issues/cmd/mesh-issues/tracker_test.go and modules/mesh-issues/cmd/mesh-issues/worker_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 41483 strings of 673 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.006s
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.691s
--- its merge-check-typescript.sh (typescript toolchain)
```
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.
Fixes novox/hq issue 483. Decision: hq ADR 0294 (proposed in novox/hq#313; supersedes ADR 0281 in part). Do not merge before ADR 0294 is accepted.
Cause found. The tracker measured delivery only for
fixed-by. Agents link the pull request (link kindpull-request) while the issue is in fixing and givefixed-byonly when they resolve it (as on issue 457), so the 13 issues the operator found were never measured, and nothing said that one was left in fixing.What changes (modules/mesh-issues only):
An issue's fixes are its
fixed-byand its linked pull requests. They feed the delivery line,FixState, the ready-to-verify note, the stuck-fix sweep and the asks. Readiness of dependent issues still readsfixed-byalone. Each sweep asks mesh-delivery for at most 5 fixes never heard of.Merged is read from the pull request, not the state. It comes from the transition's
merged_as, orpull.mergedinchecks. A pull request that isstoppedand was never merged (closed unmerged) is withdrawn: it is not stuck, not delivered and not open. The delivery line says "fix withdrawn: ..." when it is the only fix. (Review point 1.)The ready-to-verify note names each fix with when it was delivered, and the worker. The event gains
workeranddelivered-at. No channel of the tracker reaches a worker, so the note and the event are how the worker hears.Delivered, not resolved: an issue in fixing with every fix delivered. Past the setting
delivered-not-resolved-after(default1h), the sweep warns the operator's channel once:issue-tracker.delivered-not-resolved.<number>;It clears at the issue's
moved, or at the next sweep. This uses the operator's channel, like the stuck-fix warning, because a module that runs only its bundle cannot raise a controller condition (ADR 0240 rule 8, ADR 0256).Abandoned: an issue in diagnosing or fixing whose worker is stale (
worker-stale-after,24h) and that has no open pull request.getand list rows carryabandoned. A move by someone else takes it over without a reason, and the answer, the note and themovedevent sayabandoned. The issue's word "stale claim" is not used, because the glossary keeps claim for a module on a seat.listtakesflag:delivered-not-resolvedorabandoned.Comments cite ADR 0284 for the worker rules, with its section numbers. They cited 0283, which is a different decision.
No store schema change: there is a new optional key on the issue's JSON value (
not-resolved-open), and the new setting's default is in module.json.Tests (
claims_test.go):c4ea58a, fail on main.TestAPullRequestClosedUnmergedIsWithdrawn(through a transition and throughchecks) was committed in601eed0, before its fix in3aaccba. On the previous headd81e7d0it failed: the tracker told the operator "merged 26h ago, not delivered".TestOnePullRequestLinkedToSeveralIssuesguards the per-issue warning and clearing; it already passed ond81e7d0.go vet ./...,go test -race ./... -count=1and the words check pass.On roll-out: the sweep measures the linked pull requests of today's issues in fixing, five every five minutes, and warns once for each issue delivered and not resolved past an hour. Expect several warnings in the first half hour. A fix recorded as merged from the state
stoppedbefore this change stays recorded that way until its delivery says something new.Not touched: modules/docker (#205), modules/restic (#210).
Delivery
novox/mesh-catalog@d6148a5ba797— delivered since 2026-10-11T16:58:09ZDelivery plan — builds mesh-issues → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
d81e7d06mesh/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
Run by the build seat on g14 as
build-1791713865171920607(builds --log build-1791713865171920607).mesh-issues: say a delivered fix left in fixing, and flag a stale claim (hq issue 483)to mesh-issues: say a delivered fix left in fixing, and flag an abandoned issue (hq issue 483, ADR 0294)Merge check at
3aaccba4mesh/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
Run by the build seat on novox as
build-1791714291447068493(builds --log build-1791714291447068493).Merge check at
d6148a5bmesh/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
Run by the build seat on g14 as
build-1791714443784435577(builds --log build-1791714443784435577).Merge check at
d6148a5bmesh/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
Run by the build seat on novox as
build-1791737244429439346(builds --log build-1791737244429439346).