Fixes hq issue 359 (novox/hq#259): a bot token given at the controller's terminal reached the operator as "Novox needs a look — … a problem it calls "secret given"".
Cause, confirmed by a test:secretGivenObservation's explanation carried at.Local().Format("15:04"); PlainWords answered explanation: a clock time or date (23:32), so plainly replaced every word with scopeWords. Without the time the same words pass; the hyphenated secret name was not the cause.
Changes
desk_secret.go: headline "New secret given for on " (module only if over the bound), explanation names the secret as words ("telegram token") and how it was given, no time; needs "silence this if you just gave it; if you did not, give it again yourself so that only you hold it." Summary (with name and time) unchanged; severity Urgent and the one Silence action unchanged.
desk_secret_test.go: TestTheSecretGivenConditionSaysItselfInPlainWords holds the words to PlainWords for the terminal and a desk, and observes them through an in-memory keeper (so the suite-wide Unworded check in TestMain now covers this producer). Verified to fail against the old words with the cause above.
internal/conditions/plain.go: with Unworded unset (the serving controller), the keeper logs the condition kind %q is said in the scope's words, not its own: <why> once per kind and reason per process. Test: TestBorrowedWordsAreLogged.
go vet ./... and go test ./... pass locally.
Fixes hq issue 359 (novox/hq#259): a bot token given at the controller's terminal reached the operator as "Novox needs a look — … a problem it calls "secret given"".
**Cause, confirmed by a test:** `secretGivenObservation`'s explanation carried `at.Local().Format("15:04")`; `PlainWords` answered `explanation: a clock time or date (23:32)`, so `plainly` replaced every word with `scopeWords`. Without the time the same words pass; the hyphenated secret name was not the cause.
**Changes**
- `desk_secret.go`: headline "New secret given for <module> on <machine>" (module only if over the bound), explanation names the secret as words ("telegram token") and how it was given, no time; needs "silence this if you just gave it; if you did not, give it again yourself so that only you hold it." Summary (with name and time) unchanged; severity Urgent and the one Silence action unchanged.
- `desk_secret_test.go`: `TestTheSecretGivenConditionSaysItselfInPlainWords` holds the words to `PlainWords` for the terminal and a desk, and observes them through an in-memory keeper (so the suite-wide `Unworded` check in `TestMain` now covers this producer). Verified to fail against the old words with the cause above.
- `internal/conditions/plain.go`: with `Unworded` unset (the serving controller), the keeper logs `the condition kind %q is said in the scope's words, not its own: <why>` once per kind and reason per process. Test: `TestBorrowedWordsAreLogged`.
`go vet ./...` and `go test ./...` pass locally.
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
The secret-given condition's explanation carried a clock time, which the
plain rule refuses, so the operator read the scope's fallback ("needs a
look") instead of what changed. Its words now carry no time and say the
secret's name as words; a test holds them to the rule through a keeper.
With no test hook set, the keeper logs a refused or missing wording once
per kind and reason, so a fallback is never silent again (hq issue 359).
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Machines
mesh-controller on novox: passed — healthy 3 times over 3m53s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m30s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m18s
route-proxy on the rest running it: sent
Transitions
2026-10-09 21:44 (new) → proposed (announced): novox/mesh-controller#189's head announced
2026-10-09 21:50 proposed → checked (checked): the verdict names this commit
2026-10-09 21:50 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 22:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 22:00 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
2026-10-09 22:18 delivering → delivered (done): its walk is done: 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@a138c045bb04` — **delivered** since 2026-10-09T22:18:05Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 3m53s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m30s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m18s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-09 21:44 (new) → proposed (announced): novox/mesh-controller#189's head announced
- 2026-10-09 21:50 proposed → checked (checked): the verdict names this commit
- 2026-10-09 21:50 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 22:00 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 22:00 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
- 2026-10-09 22:18 delivering → delivered (done): its walk is done: 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: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
The reviewer found that the logged reason quoted the refused fragment: a
hash-shaped secret would reach the journal, and a changing clock time
defeated the once-per-kind dedupe. The reason is now logged without its
quoted fragment, the test resets the dedupe so it repeats, and a module
name too long for the headline falls back to the machine.
Independent review found three defects in the log path, fixed in a138c04: (1) the logged reason quoted the refused fragment, so a hash-shaped secret in a producer's words could reach the journal; it is now logged without its quoted fragment; (2) a changing fragment (a clock time) defeated the once-per-kind dedupe and grew the map; the dedupe key is now the kind and the reason without the fragment; (3) the log test was not repeatable (-count=2 failed); it now clears the dedupe and restores the previous log writer. Also: a module name too long for the headline or resolved line now falls back to naming the machine, with a test. go vet ./... and go test ./... pass.
Independent review found three defects in the log path, fixed in a138c04: (1) the logged reason quoted the refused fragment, so a hash-shaped secret in a producer's words could reach the journal; it is now logged without its quoted fragment; (2) a changing fragment (a clock time) defeated the once-per-kind dedupe and grew the map; the dedupe key is now the kind and the reason without the fragment; (3) the log test was not repeatable (`-count=2` failed); it now clears the dedupe and restores the previous log writer. Also: a module name too long for the headline or resolved line now falls back to naming the machine, with a test. `go vet ./...` and `go test ./...` pass.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as build-1791582105353592000 (builds --log build-1791582105353592000).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T21:38:32Z 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-09T21:38:32Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.055s
ok github.com/novox/mesh-controller/cmd/mesh-controller 241.238s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.046s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/route-proxy 1.138s
ok github.com/novox/mesh-controller/internal/artifacts 1.046s
ok github.com/novox/mesh-controller/internal/broker 2.872s
ok github.com/novox/mesh-controller/internal/builder 2.148s
ok github.com/novox/mesh-controller/internal/catalogue 5.175s
ok github.com/novox/mesh-controller/internal/conditions 2.482s
ok github.com/novox/mesh-controller/internal/envfile 1.045s
ok github.com/novox/mesh-controller/internal/facts 1.019s
ok github.com/novox/mesh-controller/internal/identity 4.781s
ok github.com/novox/mesh-controller/internal/inventory 93.845s
ok github.com/novox/mesh-controller/internal/lease 17.675s
ok github.com/novox/mesh-controller/internal/licences 4.323s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.013s
ok github.com/novox/mesh-controller/internal/link 54.852s
ok github.com/novox/mesh-controller/internal/lint 2.228s
ok github.com/novox/mesh-controller/internal/outward 1.037s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.450s
ok github.com/novox/mesh-controller/internal/store 3.320s
ok github.com/novox/mesh-controller/internal/testbus 1.192s
ok github.com/novox/mesh-controller/internal/token 1.019s
**Merge check** at `988e501c`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on novox as `build-1791582105353592000` (`builds --log build-1791582105353592000`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T21:38:32Z 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-09T21:38:32Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.055s
ok github.com/novox/mesh-controller/cmd/mesh-controller 241.238s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.046s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.016s
ok github.com/novox/mesh-controller/examples/route-proxy 1.138s
ok github.com/novox/mesh-controller/internal/artifacts 1.046s
ok github.com/novox/mesh-controller/internal/broker 2.872s
ok github.com/novox/mesh-controller/internal/builder 2.148s
ok github.com/novox/mesh-controller/internal/catalogue 5.175s
ok github.com/novox/mesh-controller/internal/conditions 2.482s
ok github.com/novox/mesh-controller/internal/envfile 1.045s
ok github.com/novox/mesh-controller/internal/facts 1.019s
ok github.com/novox/mesh-controller/internal/identity 4.781s
ok github.com/novox/mesh-controller/internal/inventory 93.845s
ok github.com/novox/mesh-controller/internal/lease 17.675s
ok github.com/novox/mesh-controller/internal/licences 4.323s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.013s
ok github.com/novox/mesh-controller/internal/link 54.852s
ok github.com/novox/mesh-controller/internal/lint 2.228s
ok github.com/novox/mesh-controller/internal/outward 1.037s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.450s
ok github.com/novox/mesh-controller/internal/store 3.320s
ok github.com/novox/mesh-controller/internal/testbus 1.192s
ok github.com/novox/mesh-controller/internal/token 1.019s
```
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as build-1791582287676207264 (builds --log build-1791582287676207264).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T21:38:32Z 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-09T21:38:32Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.043s
ok github.com/novox/mesh-controller/cmd/mesh-controller 220.567s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/route-proxy 1.196s
ok github.com/novox/mesh-controller/internal/artifacts 1.079s
ok github.com/novox/mesh-controller/internal/broker 2.825s
ok github.com/novox/mesh-controller/internal/builder 1.960s
ok github.com/novox/mesh-controller/internal/catalogue 4.903s
ok github.com/novox/mesh-controller/internal/conditions 2.567s
ok github.com/novox/mesh-controller/internal/envfile 1.047s
ok github.com/novox/mesh-controller/internal/facts 1.056s
ok github.com/novox/mesh-controller/internal/identity 4.771s
ok github.com/novox/mesh-controller/internal/inventory 87.503s
ok github.com/novox/mesh-controller/internal/lease 17.707s
ok github.com/novox/mesh-controller/internal/licences 4.329s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.051s
ok github.com/novox/mesh-controller/internal/link 53.778s
ok github.com/novox/mesh-controller/internal/lint 2.239s
ok github.com/novox/mesh-controller/internal/outward 1.079s
ok github.com/novox/mesh-controller/internal/overlay 1.071s
ok github.com/novox/mesh-controller/internal/secrets 1.569s
ok github.com/novox/mesh-controller/internal/store 3.460s
ok github.com/novox/mesh-controller/internal/testbus 1.239s
ok github.com/novox/mesh-controller/internal/token 1.014s
**Merge check** at `a138c045`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
Run by the build seat on shanks as `build-1791582287676207264` (`builds --log build-1791582287676207264`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 54 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-09T21:38:32Z 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-09T21:38:32Z
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 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.043s
ok github.com/novox/mesh-controller/cmd/mesh-controller 220.567s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.040s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.044s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.035s
ok github.com/novox/mesh-controller/examples/route-proxy 1.196s
ok github.com/novox/mesh-controller/internal/artifacts 1.079s
ok github.com/novox/mesh-controller/internal/broker 2.825s
ok github.com/novox/mesh-controller/internal/builder 1.960s
ok github.com/novox/mesh-controller/internal/catalogue 4.903s
ok github.com/novox/mesh-controller/internal/conditions 2.567s
ok github.com/novox/mesh-controller/internal/envfile 1.047s
ok github.com/novox/mesh-controller/internal/facts 1.056s
ok github.com/novox/mesh-controller/internal/identity 4.771s
ok github.com/novox/mesh-controller/internal/inventory 87.503s
ok github.com/novox/mesh-controller/internal/lease 17.707s
ok github.com/novox/mesh-controller/internal/licences 4.329s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.051s
ok github.com/novox/mesh-controller/internal/link 53.778s
ok github.com/novox/mesh-controller/internal/lint 2.239s
ok github.com/novox/mesh-controller/internal/outward 1.079s
ok github.com/novox/mesh-controller/internal/overlay 1.071s
ok github.com/novox/mesh-controller/internal/secrets 1.569s
ok github.com/novox/mesh-controller/internal/store 3.460s
ok github.com/novox/mesh-controller/internal/testbus 1.239s
ok github.com/novox/mesh-controller/internal/token 1.014s
```
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 hq issue 359 (novox/hq#259): a bot token given at the controller's terminal reached the operator as "Novox needs a look — … a problem it calls "secret given"".
Cause, confirmed by a test:
secretGivenObservation's explanation carriedat.Local().Format("15:04");PlainWordsansweredexplanation: a clock time or date (23:32), soplainlyreplaced every word withscopeWords. Without the time the same words pass; the hyphenated secret name was not the cause.Changes
desk_secret.go: headline "New secret given for on " (module only if over the bound), explanation names the secret as words ("telegram token") and how it was given, no time; needs "silence this if you just gave it; if you did not, give it again yourself so that only you hold it." Summary (with name and time) unchanged; severity Urgent and the one Silence action unchanged.desk_secret_test.go:TestTheSecretGivenConditionSaysItselfInPlainWordsholds the words toPlainWordsfor the terminal and a desk, and observes them through an in-memory keeper (so the suite-wideUnwordedcheck inTestMainnow covers this producer). Verified to fail against the old words with the cause above.internal/conditions/plain.go: withUnwordedunset (the serving controller), the keeper logsthe condition kind %q is said in the scope's words, not its own: <why>once per kind and reason per process. Test:TestBorrowedWordsAreLogged.go vet ./...andgo test ./...pass locally.The secret-given condition's explanation carried a clock time, which the plain rule refuses, so the operator read the scope's fallback ("needs a look") instead of what changed. Its words now carry no time and say the secret's name as words; a test holds them to the rule through a keeper. With no test hook set, the keeper logs a refused or missing wording once per kind and reason, so a fallback is never silent again (hq issue 359).Delivery
novox/mesh-controller@a138c045bb04— delivered since 2026-10-09T22:18:05ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Independent review found three defects in the log path, fixed in
a138c04: (1) the logged reason quoted the refused fragment, so a hash-shaped secret in a producer's words could reach the journal; it is now logged without its quoted fragment; (2) a changing fragment (a clock time) defeated the once-per-kind dedupe and grew the map; the dedupe key is now the kind and the reason without the fragment; (3) the log test was not repeatable (-count=2failed); it now clears the dedupe and restores the previous log writer. Also: a module name too long for the headline or resolved line now falls back to naming the machine, with a test.go vet ./...andgo test ./...pass.Merge check at
988e501cmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on novox as
build-1791582105353592000(builds --log build-1791582105353592000).Merge check at
a138c045mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791582287676207264(builds --log build-1791582287676207264).