Fixes the controller's part of issues 369 and 373. The router's and channels' part is mesh-catalog fix/373-one-message-per-condition.
Cause
asker.reconcile kept the newest refused ask per condition and asked again only when the channels' fingerprint changed (channelsIn: which module holds which kind, promising what). The router refused at 2026-10-10 00:26 because the channels had not yet said whether they could send (a router restart: standing not heard yet). Standing is the channel's word, not part of that fingerprint, so when both channels could send (02:33) nothing changed for the controller: seat.operator-channel.unasked was observed every minute with that refusal's words for eleven hours, and its severity followed the conditions it listed.
Fix (cmd/mesh-controller/asker.go)
A refused ask is asked again after askEvery (1 min), doubling with each refusal in a row (counted since the last ask not refused, within 6 h), at most askRefusedRetryMost (30 min); at once when the channels change, as before. So no refusal is believed longer than 30 min without being observed again.
While the router's word on an ask made again is awaited (askVerdictWait, 2 min; the router refuses as it reads), the condition stands as it was: no clear-and-raise at every try. Once taken, it clears. A new refusal is said in its own words.
The condition's explanation no longer repeats its verdict ("Needs you: … Needs you: …").
Tests (mutation-checked)
TestAnAskTheRouterRefusedIsAskedAgainAfterAGrowingWait (replaces the test that asserted a refusal waits for a channels change): waits of 1, 2, 4, 8, 16, 30, 30 min, nothing before each, one ask after; at once on a channels change. Mutants: no time bound, no doubling: fail.
TestARefusalIsAskedAgainAndTheUndeliveredConditionClearsOnceTaken: the issue-369 sequence; the condition stands during the verdict wait (mutant: flaps, fails), says the newest refusal's words, clears once taken, one verdict in its explanation (mutant: fails).
sh merge-check.sh passes locally.
Not merged: needs one independent review.
Reviewers' checklist: a genuinely new problem is never swallowed; an urgent condition still rings once; a cleared condition is said once; no condition is lost; tests fail with the fixes removed.
Fixes the controller's part of issues 369 and 373. The router's and channels' part is mesh-catalog `fix/373-one-message-per-condition`.
## Cause
`asker.reconcile` kept the newest refused ask per condition and asked again **only when the channels' fingerprint changed** (`channelsIn`: which module holds which kind, promising what). The router refused at 2026-10-10 00:26 because the channels had not yet said whether they could send (a router restart: `standing` not heard yet). Standing is the channel's word, not part of that fingerprint, so when both channels could send (02:33) nothing changed for the controller: `seat.operator-channel.unasked` was observed every minute with that refusal's words for eleven hours, and its severity followed the conditions it listed.
## Fix (`cmd/mesh-controller/asker.go`)
- A refused ask is asked again after `askEvery` (1 min), doubling with each refusal in a row (counted since the last ask not refused, within 6 h), at most `askRefusedRetryMost` (30 min); at once when the channels change, as before. So no refusal is believed longer than 30 min without being observed again.
- While the router's word on an ask made again is awaited (`askVerdictWait`, 2 min; the router refuses as it reads), the condition stands as it was: no clear-and-raise at every try. Once taken, it clears. A new refusal is said in its own words.
- The condition's explanation no longer repeats its verdict ("Needs you: … Needs you: …").
## Tests (mutation-checked)
- `TestAnAskTheRouterRefusedIsAskedAgainAfterAGrowingWait` (replaces the test that asserted a refusal waits for a channels change): waits of 1, 2, 4, 8, 16, 30, 30 min, nothing before each, one ask after; at once on a channels change. Mutants: no time bound, no doubling: fail.
- `TestARefusalIsAskedAgainAndTheUndeliveredConditionClearsOnceTaken`: the issue-369 sequence; the condition stands during the verdict wait (mutant: flaps, fails), says the newest refusal's words, clears once taken, one verdict in its explanation (mutant: fails).
`sh merge-check.sh` passes locally.
Not merged: needs one independent review.
Reviewers' checklist: a genuinely new problem is never swallowed; an urgent condition still rings once; a cleared condition is said once; no condition is lost; tests fail with the fixes removed.
The router refused an ask while its channels had not yet said they could
send; both could twenty minutes later, and the controller repeated that
refusal every minute for eleven hours, escalating "Questions for you not
delivered" on it, because a refused ask was asked again only when the
channels' claims changed.
A refused ask is now asked again after 1 min, doubling with each refusal
in a row, at most 30 min, and at once when the channels change. While the
router's word on an ask made again is awaited (2 min), the condition
stands as it was, so it neither flaps nor clears early; once the ask is
taken it clears; a new refusal is said in its own words. Its explanation
no longer says its verdict twice.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-controller on novox: passed — healthy 3 times over 3m37s
mesh-controller on the rest running it: sent
Transitions
2026-10-10 12:14 (new) → proposed (announced): novox/mesh-controller#198's head announced
2026-10-10 12:19 proposed → checked (checked): the verdict names this commit
2026-10-10 12:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 12:47 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 12:47 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 12:51 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-controller@2e0a7d1cbd2d` — **delivered** since 2026-10-10T12:51:47Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Group** `fix/373-one-message-per-condition`, in order: novox/mesh-controller@2e0a7d1cbd2d → novox/mesh-catalog@8dfc19c9f7c8
- novox/mesh-controller@2e0a7d1cbd2d before novox/mesh-catalog@8dfc19c9f7c8: version skew
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m37s
- mesh-controller on the rest running it: sent
**Transitions**
- 2026-10-10 12:14 (new) → proposed (announced): novox/mesh-controller#198's head announced
- 2026-10-10 12:19 proposed → checked (checked): the verdict names this commit
- 2026-10-10 12:19 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-10 12:47 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 12:47 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 12:51 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-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
read by no module's build: cmd/mesh-controller/asker_test.go
Run by the build seat on shanks as build-1791633834028145163 (builds --log build-1791633834028145163).
--- the gate: mesh-controller
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-10T11:55:18Z 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-10T11:55:18Z
modules the change moves:
- mesh-controller (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-controller
notes:
- cmd/mesh-controller/asker_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 220.019s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.039s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/route-proxy 1.250s
ok github.com/novox/mesh-controller/internal/artifacts 1.070s
ok github.com/novox/mesh-controller/internal/broker 2.840s
ok github.com/novox/mesh-controller/internal/builder 2.783s
ok github.com/novox/mesh-controller/internal/catalogue 5.124s
ok github.com/novox/mesh-controller/internal/conditions 2.592s
ok github.com/novox/mesh-controller/internal/envfile 1.048s
ok github.com/novox/mesh-controller/internal/facts 1.050s
ok github.com/novox/mesh-controller/internal/identity 4.791s
ok github.com/novox/mesh-controller/internal/inventory 88.049s
ok github.com/novox/mesh-controller/internal/lease 17.705s
ok github.com/novox/mesh-controller/internal/licences 4.349s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 53.890s
ok github.com/novox/mesh-controller/internal/lint 2.309s
ok github.com/novox/mesh-controller/internal/outward 1.080s
ok github.com/novox/mesh-controller/internal/overlay 1.064s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 3.527s
ok github.com/novox/mesh-controller/internal/testbus 1.234s
ok github.com/novox/mesh-controller/internal/token 1.014s
**Merge check** at `d3b45496`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
- read by no module's build: cmd/mesh-controller/asker_test.go
Run by the build seat on shanks as `build-1791633834028145163` (`builds --log build-1791633834028145163`).
```
--- the gate: mesh-controller
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-10T11:55:18Z 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-10T11:55:18Z
modules the change moves:
- mesh-controller (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-controller
notes:
- cmd/mesh-controller/asker_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 220.019s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.039s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/route-proxy 1.250s
ok github.com/novox/mesh-controller/internal/artifacts 1.070s
ok github.com/novox/mesh-controller/internal/broker 2.840s
ok github.com/novox/mesh-controller/internal/builder 2.783s
ok github.com/novox/mesh-controller/internal/catalogue 5.124s
ok github.com/novox/mesh-controller/internal/conditions 2.592s
ok github.com/novox/mesh-controller/internal/envfile 1.048s
ok github.com/novox/mesh-controller/internal/facts 1.050s
ok github.com/novox/mesh-controller/internal/identity 4.791s
ok github.com/novox/mesh-controller/internal/inventory 88.049s
ok github.com/novox/mesh-controller/internal/lease 17.705s
ok github.com/novox/mesh-controller/internal/licences 4.349s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.046s
ok github.com/novox/mesh-controller/internal/link 53.890s
ok github.com/novox/mesh-controller/internal/lint 2.309s
ok github.com/novox/mesh-controller/internal/outward 1.080s
ok github.com/novox/mesh-controller/internal/overlay 1.064s
ok github.com/novox/mesh-controller/internal/secrets 1.546s
ok github.com/novox/mesh-controller/internal/store 3.527s
ok github.com/novox/mesh-controller/internal/testbus 1.234s
ok github.com/novox/mesh-controller/internal/token 1.014s
```
A refusal stood for its part whenever no ask was open, so after the retry
was taken and answered, "Questions for you not delivered" came back with
the old words for an hour, then again after each answer. A refusal is now
current only while no ask was made after it that the router did not refuse;
the verdict wait applies only to that newer ask. Tests reconcile inside the
wait and after an answer.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
read by no module's build: cmd/mesh-controller/asker_test.go
Run by the build seat on ace as build-1791634475526073501 (builds --log build-1791634475526073501).
--- the gate: mesh-controller
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-10T11:55:18Z 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-10T11:55:18Z
modules the change moves:
- mesh-controller (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-controller
notes:
- cmd/mesh-controller/asker_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 188.563s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/route-proxy 1.163s
ok github.com/novox/mesh-controller/internal/artifacts 1.035s
ok github.com/novox/mesh-controller/internal/broker 2.669s
ok github.com/novox/mesh-controller/internal/builder 2.586s
ok github.com/novox/mesh-controller/internal/catalogue 4.526s
ok github.com/novox/mesh-controller/internal/conditions 2.481s
ok github.com/novox/mesh-controller/internal/envfile 1.089s
ok github.com/novox/mesh-controller/internal/facts 1.092s
ok github.com/novox/mesh-controller/internal/identity 4.210s
ok github.com/novox/mesh-controller/internal/inventory 72.609s
ok github.com/novox/mesh-controller/internal/lease 17.699s
ok github.com/novox/mesh-controller/internal/licences 3.852s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.088s
ok github.com/novox/mesh-controller/internal/link 51.351s
ok github.com/novox/mesh-controller/internal/lint 2.057s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.070s
ok github.com/novox/mesh-controller/internal/secrets 1.439s
ok github.com/novox/mesh-controller/internal/store 3.392s
ok github.com/novox/mesh-controller/internal/testbus 1.263s
ok github.com/novox/mesh-controller/internal/token 1.015s
**Merge check** at `2e0a7d1c`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
- read by no module's build: cmd/mesh-controller/asker_test.go
Run by the build seat on ace as `build-1791634475526073501` (`builds --log build-1791634475526073501`).
```
--- the gate: mesh-controller
mesh-controller: ok, 55 tool(s); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
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-10T11:55:18Z 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-10T11:55:18Z
modules the change moves:
- mesh-controller (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-controller
notes:
- cmd/mesh-controller/asker_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.036s
ok github.com/novox/mesh-controller/cmd/mesh-controller 188.563s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.060s
ok github.com/novox/mesh-controller/examples/route-proxy 1.163s
ok github.com/novox/mesh-controller/internal/artifacts 1.035s
ok github.com/novox/mesh-controller/internal/broker 2.669s
ok github.com/novox/mesh-controller/internal/builder 2.586s
ok github.com/novox/mesh-controller/internal/catalogue 4.526s
ok github.com/novox/mesh-controller/internal/conditions 2.481s
ok github.com/novox/mesh-controller/internal/envfile 1.089s
ok github.com/novox/mesh-controller/internal/facts 1.092s
ok github.com/novox/mesh-controller/internal/identity 4.210s
ok github.com/novox/mesh-controller/internal/inventory 72.609s
ok github.com/novox/mesh-controller/internal/lease 17.699s
ok github.com/novox/mesh-controller/internal/licences 3.852s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.088s
ok github.com/novox/mesh-controller/internal/link 51.351s
ok github.com/novox/mesh-controller/internal/lint 2.057s
ok github.com/novox/mesh-controller/internal/outward 1.091s
ok github.com/novox/mesh-controller/internal/overlay 1.070s
ok github.com/novox/mesh-controller/internal/secrets 1.439s
ok github.com/novox/mesh-controller/internal/store 3.392s
ok github.com/novox/mesh-controller/internal/testbus 1.263s
ok github.com/novox/mesh-controller/internal/token 1.015s
```
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 the controller's part of issues 369 and 373. The router's and channels' part is mesh-catalog
fix/373-one-message-per-condition.Cause
asker.reconcilekept the newest refused ask per condition and asked again only when the channels' fingerprint changed (channelsIn: which module holds which kind, promising what). The router refused at 2026-10-10 00:26 because the channels had not yet said whether they could send (a router restart:standingnot heard yet). Standing is the channel's word, not part of that fingerprint, so when both channels could send (02:33) nothing changed for the controller:seat.operator-channel.unaskedwas observed every minute with that refusal's words for eleven hours, and its severity followed the conditions it listed.Fix (
cmd/mesh-controller/asker.go)askEvery(1 min), doubling with each refusal in a row (counted since the last ask not refused, within 6 h), at mostaskRefusedRetryMost(30 min); at once when the channels change, as before. So no refusal is believed longer than 30 min without being observed again.askVerdictWait, 2 min; the router refuses as it reads), the condition stands as it was: no clear-and-raise at every try. Once taken, it clears. A new refusal is said in its own words.Tests (mutation-checked)
TestAnAskTheRouterRefusedIsAskedAgainAfterAGrowingWait(replaces the test that asserted a refusal waits for a channels change): waits of 1, 2, 4, 8, 16, 30, 30 min, nothing before each, one ask after; at once on a channels change. Mutants: no time bound, no doubling: fail.TestARefusalIsAskedAgainAndTheUndeliveredConditionClearsOnceTaken: the issue-369 sequence; the condition stands during the verdict wait (mutant: flaps, fails), says the newest refusal's words, clears once taken, one verdict in its explanation (mutant: fails).sh merge-check.shpasses locally.Not merged: needs one independent review.
Reviewers' checklist: a genuinely new problem is never swallowed; an urgent condition still rings once; a cleared condition is said once; no condition is lost; tests fail with the fixes removed.
Delivery
novox/mesh-controller@2e0a7d1cbd2d— delivered since 2026-10-10T12:51:47ZDelivery plan — builds mesh-controller → novox; no bus step
Group
fix/373-one-message-per-condition, in order: novox/mesh-controller@2e0a7d1cbd → novox/mesh-catalog@8dfc19c9f7Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
d3b45496mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on shanks as
build-1791633834028145163(builds --log build-1791633834028145163).Merge check at
2e0a7d1cmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1791634475526073501(builds --log build-1791634475526073501).