The runtime's comments (broker-nats.ts, bus.go) said a handler failing for good "exhausts max-deliver and dead-letters"; nothing received what was given up (hq issue 330). The controller now keeps it in DEAD_LETTERS and delivers it again under mesh.again.<consumer>.<subject without mesh.> (mesh-controller#159, hq ADR 0264).
Comments corrected to say what happens.
TestAnEventDeliveredAgainHasItsOwnKey: an event delivered again (a module's and a seat's) has the key it had, so no runtime change is needed. The TypeScript keyFromSubject reads the same tokens.
merge-check.sh: passed locally.
Delivery group: fix/330-a-message-given-up-on-is-kept with mesh-controller, mesh-lab and hq.
The runtime's comments (broker-nats.ts, bus.go) said a handler failing for good "exhausts max-deliver and dead-letters"; nothing received what was given up (hq issue 330). The controller now keeps it in DEAD_LETTERS and delivers it again under `mesh.again.<consumer>.<subject without mesh.>` (mesh-controller#159, hq ADR 0264).
- Comments corrected to say what happens.
- `TestAnEventDeliveredAgainHasItsOwnKey`: an event delivered again (a module's and a seat's) has the key it had, so no runtime change is needed. The TypeScript `keyFromSubject` reads the same tokens.
merge-check.sh: passed locally.
Delivery group: `fix/330-a-message-given-up-on-is-kept` with mesh-controller, mesh-lab and hq.
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 …
The comments said a failing event dead-letters, which nothing did; the
controller now keeps it, and delivers it again under a subject this runtime
reads the same key from (ADR 0264).
node-tools on ace: passed — healthy 3 times over 2m24s
mesh-tools on every machine running it: sent
node-tools on the rest running it: sent
Transitions
2026-10-08 15:37 (new) → proposed (announced): novox/mesh-tools#24's head announced
2026-10-08 15:39 proposed → checked (checked): the verdict names this commit
2026-10-08 15:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-08 19:24 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-08 19:24 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-08 19:29 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-tools@c401bbff2d7a` — **delivered** since 2026-10-08T19:29:02Z
**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
**Group** `fix/330-a-message-given-up-on-is-kept`, in order: novox/hq@26ff767a7b89 → novox/mesh-controller@909062e7294d → novox/mesh-host@a31659ed0328 → novox/mesh-lab@54db7c3458f7 → novox/mesh-tools@c401bbff2d7a
- novox/mesh-controller@909062e7294d before novox/mesh-host@a31659ed0328: built by, over engine before controller
- novox/mesh-controller@909062e7294d before novox/mesh-tools@c401bbff2d7a: built by
**Machines**
- node-tools on ace: passed — healthy 3 times over 2m24s
- mesh-tools on every machine running it: sent
- node-tools on the rest running it: sent
**Transitions**
- 2026-10-08 15:37 (new) → proposed (announced): novox/mesh-tools#24's head announced
- 2026-10-08 15:39 proposed → checked (checked): the verdict names this commit
- 2026-10-08 15:39 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-08 19:24 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-08 19:24 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-08 19:29 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 — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-tools, node-tools)
mesh/repo-check: PASS — 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-1791473869829660682 (builds --log build-1791473869829660682).
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 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-08T15:33:40Z 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-08T15:33:40Z
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
--- 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.192s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.373s
ok github.com/novox/mesh-tools/node-tools/internal/bus 1.882s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.050s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.114s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.004s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
**Merge check** at `c401bbff`
- `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** — 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-1791473869829660682` (`builds --log build-1791473869829660682`).
```
--- the gate: mesh-tools, node-tools
mesh-tools: ok
node-tools: ok, invokes every tool
long-running resources without health: 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-08T15:33:40Z 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-08T15:33:40Z
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
--- 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.192s
ok github.com/novox/mesh-tools/node-tools/internal/announce 4.373s
ok github.com/novox/mesh-tools/node-tools/internal/bus 1.882s
ok github.com/novox/mesh-tools/node-tools/internal/launch 1.050s
ok github.com/novox/mesh-tools/node-tools/internal/meshtest 1.114s
? github.com/novox/mesh-tools/node-tools/internal/wire [no test files]
ok github.com/novox/mesh-tools/node-tools/internal/console 0.004s
NOT TESTED HERE: node-tools/src (TypeScript) needs @novox/mesh-sdk from the package registry
```
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.
The runtime's comments (broker-nats.ts, bus.go) said a handler failing for good "exhausts max-deliver and dead-letters"; nothing received what was given up (hq issue 330). The controller now keeps it in DEAD_LETTERS and delivers it again under
mesh.again.<consumer>.<subject without mesh.>(mesh-controller#159, hq ADR 0264).TestAnEventDeliveredAgainHasItsOwnKey: an event delivered again (a module's and a seat's) has the key it had, so no runtime change is needed. The TypeScriptkeyFromSubjectreads the same tokens.merge-check.sh: passed locally.
Delivery group:
fix/330-a-message-given-up-on-is-keptwith mesh-controller, mesh-lab and hq.Delivery
novox/mesh-tools@c401bbff2d7a— delivered since 2026-10-08T19:29:02ZDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Group
fix/330-a-message-given-up-on-is-kept, in order: novox/hq@26ff767a7b → novox/mesh-controller@909062e729 → novox/mesh-host@a31659ed03 → novox/mesh-lab@54db7c3458 → novox/mesh-tools@c401bbff2dMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
c401bbffmesh/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 — its merge-check.sh passedDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791473869829660682(builds --log build-1791473869829660682).