One delivery group, branch feat/l3-final in mesh-sdk, mesh-delivery, mesh-catalog, mesh-tools and mesh-host: the final release of design 47's step L3 (issue 774, with 1367 and 1585).
This member: tool-runner back in node-tools' module.json (revert of 40e0e82); node-tools pins mesh-sdk 85ba0a9a70d8. After check 278aa5f0ccbe failed: the manifest takes version 2. That gives new bytes, because the running indexer holds a stale refusal for the reverted bytes (a recovery of the moment, said to the operator; the thorough fix is in mesh-delivery in this group).
What the operator sees: the tool runner restarts on every node, so the mesh MCP server drops briefly.
Reviewed-by: mesh-code-reviewer@shanks at 7fd9d893c0
Pushed-by: lead-47@shanks
One delivery group, branch feat/l3-final in mesh-sdk, mesh-delivery, mesh-catalog, mesh-tools and mesh-host: the final release of design 47's step L3 (issue 774, with 1367 and 1585).
This member: `tool-runner` back in node-tools' module.json (revert of 40e0e82); node-tools pins mesh-sdk 85ba0a9a70d8. After check 278aa5f0ccbe failed: the manifest takes version 2. That gives new bytes, because the running indexer holds a stale refusal for the reverted bytes (a recovery of the moment, said to the operator; the thorough fix is in mesh-delivery in this group).
What the operator sees: the tool runner restarts on every node, so the mesh MCP server drops briefly.
Reviewed-by: mesh-code-reviewer@shanks at 7fd9d893c0a50323dc4422fe46a82a9026b65dc9
Pushed-by: lead-47@shanks
https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn
mesh/check failed (2): unit: mesh-provisioner-client/cmd/mesh-provisioner-client.TestNatsANodeComingBackFil…; and 1 more | 0fb4591c9da9 on b4819dc1fb73
Deliverynovox/mesh-tools@7fd9d893c0a5 — merged since 2026-11-04T00:24:05Z
Source — source.main moved to novox/mesh-tools@84ede95c4a. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
composed together: pass — the checker's verdict at the members' heads (d6a3e805db4a)
Transitions
2026-11-03 23:56 (new) → proposed (announced): novox/mesh-tools#60's head announced
2026-11-03 23:56 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-04 00:24 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-tools@7fd9d893c0a5` — **merged** since 2026-11-04T00:24:05Z
**Source** — source.main moved to novox/mesh-tools@84ede95c4af7. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Group** `feat/l3-final`: novox/mesh-catalog@6c09be4a703e, novox/mesh-delivery@70ade15c36eb, novox/mesh-host@30b86ea602a8, novox/mesh-sdk@85ba0a9a70d8, novox/mesh-tools@7fd9d893c0a5
- composed together: pass — the checker's verdict at the members' heads (d6a3e805db4a)
**Transitions**
- 2026-11-03 23:56 (new) → proposed (announced): novox/mesh-tools#60's head announced
- 2026-11-03 23:56 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-04 00:24 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
mesh-delivery: not merged. The merge of this pull request into main at 0fb4591c9d was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.
mesh-delivery: **not merged.** The merge of this pull request into main at 0fb4591c9da9d03bd9b8bb659faf96e774c1d44d was declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.
The running indexer holds a refusal from 21:14 for the exact bytes of this manifest, which says tool-runner again. A new digest is read afresh; the thorough fix of stale verdicts is in the indexer in this group (issue 774).
Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn
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.
One delivery group, branch feat/l3-final in mesh-sdk, mesh-delivery, mesh-catalog, mesh-tools and mesh-host: the final release of design 47's step L3 (issue 774, with 1367 and 1585).
This member:
tool-runnerback in node-tools' module.json (revert of40e0e82); node-tools pins mesh-sdk 85ba0a9a70d8. After check 278aa5f0ccbe failed: the manifest takes version 2. That gives new bytes, because the running indexer holds a stale refusal for the reverted bytes (a recovery of the moment, said to the operator; the thorough fix is in mesh-delivery in this group).What the operator sees: the tool runner restarts on every node, so the mesh MCP server drops briefly.
Reviewed-by: mesh-code-reviewer@shanks at
7fd9d893c0Pushed-by: lead-47@shanks
https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn
Delivery
novox/mesh-tools@7fd9d893c0a5— merged since 2026-11-04T00:24:05ZSource — source.main moved to novox/mesh-tools@84ede95c4a. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
feat/l3-final: novox/mesh-catalog@6c09be4a70, novox/mesh-delivery@70ade15c36, novox/mesh-host@30b86ea602, novox/mesh-sdk@85ba0a9a70, novox/mesh-tools@7fd9d893c0Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.mesh-delivery: not merged. The merge of this pull request into main at
0fb4591c9dwas declined: the operator, via telegram (user id verified), chose Decline. A new head asks the operator again.