node-tools: serve a module's log verbs (ADR 0297, issues 501, 502) #28

Merged
mesh-admin merged 2 commits from adr-0297-log-verbs into main 2026-10-12 00:28:28 +00:00
Contributor

Implements the runtime part of novox/hq ADR 0297 (a module may declare a log of operations), for issue 501 (the tracker's bucket fills toward its cap with no warning) and issue 502 (its audit trail lasts only 7 days).

What changes

  • bus.Membership gains logs: [{name, stream, subject, writes}], next to state.
  • internal/bus/log.go: LogAppend, LogRead, LogLast, LogInfo on Conn. They use only a publish on mesh.log.<module>.<name>.<key>, $JS.API.STREAM.INFO.<stream> and $JS.API.DIRECT.GET.<stream>[.>]. No consumer is created.
    • append {log, key, value, expect?} -> {sequence}. expect is decoded as a pointer, so expect: 0 sends Nats-Expected-Last-Subject-Sequence: 0 and an omitted expect sends no check. A wrong-last-sequence refusal (10071, and 10164 for a replicated stream) answers the existing lost-update error changed{}: errors.Is(err, bus.ErrStateChanged), code -32010 (launch.CodeChanged).
    • read {log, from, keys?, limit?} -> {entries:[{sequence,key,value,at}], next, last}. It is one batch direct get with seq, next_by_subj, batch and max_bytes 4 MiB. limit defaults to 100 and allows at most 1000. next is 0 when nothing follows, last comes from stream info, and at is RFC 3339.
    • last {log, key} -> entry or null. info {log} -> {entries, bytes, max_bytes, first, last}.
    • These are refused with the reason: a log not issued to the module, a value that is not JSON or is over 256 KiB, a key that is not [A-Za-z0-9_-]+ names joined by . or is over 255 bytes, a key pattern with > anywhere but last, and a limit outside 1..1000.
  • runtime.moduleBus.Log and launch route mesh/log.append|read|last|info the same way as mesh/state.*. Nothing changes for mesh/state.*.
  • meshtest.Mesh.Log creates the stream as the contract configures it, for tests.

How it is checked

internal/runtime/log_test.go runs against a bus of its own:

  • each verb: paging with next, key patterns, last, null, info fields, and no consumer on the stream
  • the 4 MiB page bound
  • a stale and a future expect refused with code -32010 and ErrStateChanged, writing nothing
  • refusal of a log not issued to the module, and of an unissued name
  • value, key, pattern and limit refusals

The new tests are added to merge-check.sh's runtimeless list, so they run where node is absent. sh merge-check.sh passes locally.

Implements the runtime part of novox/hq ADR 0297 (a module may declare a log of operations), for issue 501 (the tracker's bucket fills toward its cap with no warning) and issue 502 (its audit trail lasts only 7 days). ## What changes - `bus.Membership` gains `logs`: `[{name, stream, subject, writes}]`, next to `state`. - `internal/bus/log.go`: `LogAppend`, `LogRead`, `LogLast`, `LogInfo` on `Conn`. They use only a publish on `mesh.log.<module>.<name>.<key>`, `$JS.API.STREAM.INFO.<stream>` and `$JS.API.DIRECT.GET.<stream>[.>]`. No consumer is created. - `append` {log, key, value, expect?} -> {sequence}. `expect` is decoded as a pointer, so `expect: 0` sends `Nats-Expected-Last-Subject-Sequence: 0` and an omitted `expect` sends no check. A wrong-last-sequence refusal (10071, and 10164 for a replicated stream) answers the existing lost-update error `changed{}`: `errors.Is(err, bus.ErrStateChanged)`, code -32010 (`launch.CodeChanged`). - `read` {log, from, keys?, limit?} -> {entries:[{sequence,key,value,at}], next, last}. It is one batch direct get with `seq`, `next_by_subj`, `batch` and `max_bytes` 4 MiB. `limit` defaults to 100 and allows at most 1000. `next` is 0 when nothing follows, `last` comes from stream info, and `at` is RFC 3339. - `last` {log, key} -> entry or null. `info` {log} -> {entries, bytes, max_bytes, first, last}. - These are refused with the reason: a log not issued to the module, a value that is not JSON or is over 256 KiB, a key that is not `[A-Za-z0-9_-]+` names joined by `.` or is over 255 bytes, a key pattern with `>` anywhere but last, and a limit outside 1..1000. - `runtime.moduleBus.Log` and `launch` route `mesh/log.append|read|last|info` the same way as `mesh/state.*`. Nothing changes for `mesh/state.*`. - `meshtest.Mesh.Log` creates the stream as the contract configures it, for tests. ## How it is checked `internal/runtime/log_test.go` runs against a bus of its own: - each verb: paging with `next`, key patterns, `last`, null, info fields, and no consumer on the stream - the 4 MiB page bound - a stale and a future `expect` refused with code -32010 and `ErrStateChanged`, writing nothing - refusal of a log not issued to the module, and of an unissued name - value, key, pattern and limit refusals The new tests are added to merge-check.sh's runtimeless list, so they run where node is absent. `sh merge-check.sh` passes locally.
mesh-admin added 1 commit 2026-10-11 17:19:12 +00:00
Serve a module's log verbs so its record outlives a bucket's cap and the events' week (ADR 0297, issues 501, 502)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of …
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
d535dd5322
The runtime answers mesh/log.append, read, last and info for a log issued
in the module's membership, by publish, batch direct get and stream info
alone. A stale expect is refused as a lost state update, so a module tells
it by the same code.
Author
Contributor

Delivery novox/mesh-tools@82aefe1988c2 — delivered since 2026-10-12T00:34:41Z

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-tools, node-tools
  • ace: receives node-tools
  • g14: receives node-tools
  • novox: receives node-tools
  • shanks: receives node-tools
  • node-tools provides mcp-endpoint: its consumers are sent again after it

Machines

  • node-tools on ace: passed — healthy 3 times over 2m28s
  • mesh-tools on every machine running it: sent
  • node-tools on the rest running it: sent

Transitions

  • 2026-10-11 17:20 (new) → proposed (announced): novox/mesh-tools#28's head announced
  • 2026-10-11 17:24 proposed → checked (checked): the verdict names this commit
  • 2026-10-11 17:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-12 00:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-12 00:30 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-12 00:34 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-tools@82aefe1988c2` — **delivered** since 2026-10-12T00:34:41Z **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it **Machines** - node-tools on ace: passed — healthy 3 times over 2m28s - mesh-tools on every machine running it: sent - node-tools on the rest running it: sent **Transitions** - 2026-10-11 17:20 (new) → proposed (announced): novox/mesh-tools#28's head announced - 2026-10-11 17:24 proposed → checked (checked): the verdict names this commit - 2026-10-11 17:24 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-12 00:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-12 00:30 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-12 00:34 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
jschoubben added 1 commit 2026-10-11 17:20:33 +00:00
Refuse a credential in a log entry and take a full 256 KiB value with its expect header (ADR 0297 review)
mesh/merge-gate pass: builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of …
mesh/repo-check pass: THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; it…
mesh/delivery delivered
82aefe1988
A log keeps what it is given for good, so the state guard against secrets
applies to it too; the stream holds 260 KiB a message so the headers an
append carries never push a 256 KiB value over.
Author
Contributor

Review (independent): APPROVE of the code at 82aefe1988, checked against the ADR 0297 contract. (The forge refuses an APPROVED review from a tool under ADR 0266, so this is a comment.) The required checks were not green when I read them, so this approval is not a merge clearance until they are: mesh/merge-gate pending 'building on g14 since 19:22', mesh/repo-check missing (no status yet).

  1. Wire names and shapes: pass. bus/log.go:35-57 match mesh-sdk go/log.go:16-38. append answers {sequence} (runtime.go Log, append case); read answers LogPage; last answers the entry or null; info answers entries, bytes, max_bytes, first, last.
  2. expect: pass. logAsked.Expect is *uint64 (runtime.go logAsked). bus/log.go:167-169 sets Nats-Expected-Last-Subject-Sequence whenever it is present, 0 included; the test appends at expect 0 and is refused at a second expect 0 (log_test.go:225-227).
  3. A stale expect answers the lost-update error: pass. bus/log.go:191-193 returns changed{} for 10071 and 10164, the same type StateUpdate returns (bus/seat.go:400-404, ErrorCode -32010), and launch.go:627 errorCode answers it as -32010. log_test.go:222 and 251-255 assert the code and errors.Is ErrStateChanged; refused appends write nothing (log_test.go:242).
  4. Bus use: pass. Only a publish request on the key subject (bus/log.go:170), STREAM.INFO (311-312), and DIRECT.GET batch (231) and last by subject (285). No consumer is created; log_test.go:189 asserts 0 consumers.
  5. Credential guard: pass. bus/log.go:160 calls the same credentialField that StatePut uses (bus/state.go:144, 322). A 256 KiB value is accepted with expect and without (log_test.go:316-319, stream MaxMsgSize 260 KiB in meshtest.go). Over 256 KiB is refused (log_test.go:293).
  6. Refusals: pass. A log that was not issued is refused with the reason and the issued names (bus/log.go:129; log_test.go:260-282). writes:false is refused at bus/log.go:147, but no test covers it (non-blocking).
  7. Paging: pass. Next is the last sent sequence + 1 only when the EOB's Nats-Num-Pending is above 0 (bus/log.go:254-258). I checked nats-server 2.11.17 stream.go: the EOB pending is decremented per message sent and recomputed from the next sequence if the stream grew during the batch, so nothing is lost or repeated. 404 ends an empty page. The key filter lets * stand anywhere and > only last, and refuses empty tokens (bus/log.go:91-108). Tests cover key-filtered paging, *, >, a page bounded by its bytes and paging through 20 entries of 250 KiB (log_test.go:145-213).
  8. mesh/state.* is unchanged: the diff only adds code (Membership.Logs, the Log verb, the launch case); no state code was touched.
  9. I ran merge-check.sh locally and it passed (bus, launch, runtime and the rest ok, race-checked). I ran the log tests verbosely and all 6 passed, TestAnAppendAtAStaleExpectIsRefusedAsALostUpdate included.

Non-blocking findings:
(a) Nothing tests writes:false (bus/log.go:147). Add a test with a LogIssued whose Writes is false.
(b) Params that do not decode (for example expect -1 or a string) are answered 'mesh/log. names no log' (runtime.go Log), which names the wrong cause.
(c) A missing Nats-Num-Pending header would end paging silently with next 0. NATS 2.11 always sends it, so this only matters on an older server.

Review (independent): APPROVE of the code at 82aefe1988c2436eb3c4c3a9607a5bc9402e4aef, checked against the ADR 0297 contract. (The forge refuses an APPROVED review from a tool under ADR 0266, so this is a comment.) The required checks were not green when I read them, so this approval is not a merge clearance until they are: mesh/merge-gate pending 'building on g14 since 19:22', mesh/repo-check missing (no status yet). 1. Wire names and shapes: pass. bus/log.go:35-57 match mesh-sdk go/log.go:16-38. append answers {sequence} (runtime.go Log, append case); read answers LogPage; last answers the entry or `null`; info answers entries, bytes, max_bytes, first, last. 2. expect: pass. logAsked.Expect is *uint64 (runtime.go logAsked). bus/log.go:167-169 sets Nats-Expected-Last-Subject-Sequence whenever it is present, 0 included; the test appends at expect 0 and is refused at a second expect 0 (log_test.go:225-227). 3. A stale expect answers the lost-update error: pass. bus/log.go:191-193 returns changed{} for 10071 and 10164, the same type StateUpdate returns (bus/seat.go:400-404, ErrorCode -32010), and launch.go:627 errorCode answers it as -32010. log_test.go:222 and 251-255 assert the code and errors.Is ErrStateChanged; refused appends write nothing (log_test.go:242). 4. Bus use: pass. Only a publish request on the key subject (bus/log.go:170), STREAM.INFO (311-312), and DIRECT.GET batch (231) and last by subject (285). No consumer is created; log_test.go:189 asserts 0 consumers. 5. Credential guard: pass. bus/log.go:160 calls the same credentialField that StatePut uses (bus/state.go:144, 322). A 256 KiB value is accepted with expect and without (log_test.go:316-319, stream MaxMsgSize 260 KiB in meshtest.go). Over 256 KiB is refused (log_test.go:293). 6. Refusals: pass. A log that was not issued is refused with the reason and the issued names (bus/log.go:129; log_test.go:260-282). writes:false is refused at bus/log.go:147, but no test covers it (non-blocking). 7. Paging: pass. Next is the last sent sequence + 1 only when the EOB's Nats-Num-Pending is above 0 (bus/log.go:254-258). I checked nats-server 2.11.17 stream.go: the EOB pending is decremented per message sent and recomputed from the next sequence if the stream grew during the batch, so nothing is lost or repeated. 404 ends an empty page. The key filter lets `*` stand anywhere and `>` only last, and refuses empty tokens (bus/log.go:91-108). Tests cover key-filtered paging, `*`, `>`, a page bounded by its bytes and paging through 20 entries of 250 KiB (log_test.go:145-213). 8. mesh/state.* is unchanged: the diff only adds code (Membership.Logs, the Log verb, the launch case); no state code was touched. 9. I ran merge-check.sh locally and it passed (bus, launch, runtime and the rest ok, race-checked). I ran the log tests verbosely and all 6 passed, TestAnAppendAtAStaleExpectIsRefusedAsALostUpdate included. Non-blocking findings: (a) Nothing tests writes:false (bus/log.go:147). Add a test with a LogIssued whose Writes is false. (b) Params that do not decode (for example expect -1 or a string) are answered 'mesh/log.<verb> names no log' (runtime.go Log), which names the wrong cause. (c) A missing Nats-Num-Pending header would end paging silently with next 0. NATS 2.11 always sends it, so this only matters on an older server.
Author
Contributor

Merge check at d535dd53

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
  • mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-tools, node-tools
  • ace: receives node-tools
  • g14: receives node-tools
  • novox: receives node-tools
  • shanks: receives node-tools
  • node-tools provides mcp-endpoint: its consumers are sent again after it

Run by the build seat on shanks as build-1791739179879661524 (builds --log build-1791739179879661524).

--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z

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 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
?   	github.com/novox/mesh-tools/node-tools/cmd/node-tools	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/alive	1.189s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.369s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	12.509s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.074s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.136s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/console	0.005s
ok  	github.com/novox/mesh-tools/node-tools/internal/runtime	2.591s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `d535dd53` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools) - `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it Run by the build seat on shanks as `build-1791739179879661524` (`builds --log build-1791739179879661524`). ``` --- the gate: mesh-tools, node-tools mesh-tools: ok node-tools: ok, invokes every tool long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z 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 2 module(s) in 1 tier(s): mesh-tools, node-tools --- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges --- its merge-check.sh (go toolchain) NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk ? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files] ok github.com/novox/mesh-tools/node-tools/internal/alive 1.189s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.369s ok github.com/novox/mesh-tools/node-tools/internal/bus 12.509s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.074s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.136s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] ok github.com/novox/mesh-tools/node-tools/internal/console 0.005s ok github.com/novox/mesh-tools/node-tools/internal/runtime 2.591s NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```
Author
Contributor

Merge check at 82aefe19

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
  • mesh/repo-check: PASS — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed

Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-tools, node-tools
  • ace: receives node-tools
  • g14: receives node-tools
  • novox: receives node-tools
  • shanks: receives node-tools
  • node-tools provides mcp-endpoint: its consumers are sent again after it

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

--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z

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 2 module(s) in 1 tier(s): mesh-tools, node-tools
--- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges
--- its merge-check.sh (go toolchain)
NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk
?   	github.com/novox/mesh-tools/node-tools/cmd/node-tools	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/alive	1.188s
ok  	github.com/novox/mesh-tools/node-tools/internal/announce	4.364s
ok  	github.com/novox/mesh-tools/node-tools/internal/bus	12.601s
ok  	github.com/novox/mesh-tools/node-tools/internal/launch	1.069s
ok  	github.com/novox/mesh-tools/node-tools/internal/meshtest	1.115s
?   	github.com/novox/mesh-tools/node-tools/internal/wire	[no test files]
ok  	github.com/novox/mesh-tools/node-tools/internal/console	0.004s
ok  	github.com/novox/mesh-tools/node-tools/internal/runtime	2.919s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `82aefe19` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools) - `mesh/repo-check`: **PASS** — THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges; its merge-check.sh passed **Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step - tier 0: mesh-tools, node-tools - ace: receives node-tools - g14: receives node-tools - novox: receives node-tools - shanks: receives node-tools - node-tools provides mcp-endpoint: its consumers are sent again after it Run by the build seat on g14 as `build-1791739240902143203` (`builds --log build-1791739240902143203`). ``` --- the gate: mesh-tools, node-tools mesh-tools: ok node-tools: ok, invokes every tool long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T17:21:39Z 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-11T17:21:39Z 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 2 module(s) in 1 tier(s): mesh-tools, node-tools --- THE CHANGE ALTERS ITS OWN CHECK (merge-check.sh): main's version judged it; the change's judges the pull requests after it merges --- its merge-check.sh (go toolchain) NOT TESTED HERE: internal/runtime and internal/console launch bundles that need node and @novox/mesh-sdk ? github.com/novox/mesh-tools/node-tools/cmd/node-tools [no test files] ok github.com/novox/mesh-tools/node-tools/internal/alive 1.188s ok github.com/novox/mesh-tools/node-tools/internal/announce 4.364s ok github.com/novox/mesh-tools/node-tools/internal/bus 12.601s ok github.com/novox/mesh-tools/node-tools/internal/launch 1.069s ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.115s ? github.com/novox/mesh-tools/node-tools/internal/wire [no test files] ok github.com/novox/mesh-tools/node-tools/internal/console 0.004s ok github.com/novox/mesh-tools/node-tools/internal/runtime 2.919s NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry ```
mesh-admin merged commit 4348b42844 into main 2026-10-12 00:28:28 +00:00
mesh-admin deleted branch adr-0297-log-verbs 2026-10-12 00:28:28 +00:00
Sign in to join this conversation.
No Reviewers
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-tools#28