Issue 1979, design 42 milestone zfs-owns-zfs (lead answers A-42, A-44). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-host, mesh-delivery and mesh-catalog.
a775b42e: the tool runner answers mesh/stream.publish for the calling bundle's own bound stream only (another module's or a non-stream binding refused), an acknowledged JetStream publish on the binding's subject plus .<event>, the id as the message id, under the grant the runner already holds (boundOf).
df2162e3: the call is the family of its own capability stream-publish, stated by the runner, so a module asking for it is placed only where the runner answers it (A-44).
Quick or thorough: thorough — a bundle had no way onto a template events stream (met twice: the zfs keeper, the zfs tools; messenger shows the same gap, noted on issue 1979).
Reviewed-by: mesh-code-reviewer of fix-1977@ace at df2162e381
Issue 1979, design 42 milestone zfs-owns-zfs (lead answers A-42, A-44). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-host, mesh-delivery and mesh-catalog.
- a775b42e: the tool runner answers `mesh/stream.publish` for the calling bundle's own bound stream only (another module's or a non-stream binding refused), an acknowledged JetStream publish on the binding's subject plus `.<event>`, the id as the message id, under the grant the runner already holds (`boundOf`).
- df2162e3: the call is the family of its own capability `stream-publish`, stated by the runner, so a module asking for it is placed only where the runner answers it (A-44).
Quick or thorough: thorough — a bundle had no way onto a template events stream (met twice: the zfs keeper, the zfs tools; messenger shows the same gap, noted on issue 1979).
Reviewed-by: mesh-code-reviewer of fix-1977@ace at df2162e381f5c192884e81dbb49de782ac6ca9da
mesh/check being carried to df2162e381f5 on af8385495688 | from 447a8d035935, mesh-catalog 117f933dacf0, mesh-delivery 7221a1e5cd7f, mesh-host 0193949…
Deliverynovox/mesh-tools@df2162e381f5 — merged since 2026-11-13T08:00:55Z
Source — source.main moved to novox/mesh-tools@af83854956. 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 (13bf070ecb87)
Transitions
2026-11-13 01:07 (new) → proposed (announced): novox/mesh-tools#70's head announced
2026-11-13 01:07 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-13 08:00 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@df2162e381f5` — **merged** since 2026-11-13T08:00:55Z
**Source** — source.main moved to novox/mesh-tools@af8385495688. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Group** `feature/1979-zfs-owns-zfs`: novox/mesh-catalog@0041b69d1736, novox/mesh-delivery@ad7e58091801, novox/mesh-host@96a869063977, novox/mesh-sdk@2895a21e69cd, novox/mesh-tools@df2162e381f5
- composed together: pass — the checker's verdict at the members' heads (13bf070ecb87)
**Transitions**
- 2026-11-13 01:07 (new) → proposed (announced): novox/mesh-tools#70's head announced
- 2026-11-13 01:07 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-13 08:00 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: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
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.
Issue 1979, design 42 milestone zfs-owns-zfs (lead answers A-42, A-44). Delivery group feature/1979-zfs-owns-zfs with mesh-sdk, mesh-host, mesh-delivery and mesh-catalog.
a775b42e: the tool runner answersmesh/stream.publishfor the calling bundle's own bound stream only (another module's or a non-stream binding refused), an acknowledged JetStream publish on the binding's subject plus.<event>, the id as the message id, under the grant the runner already holds (boundOf).df2162e3: the call is the family of its own capabilitystream-publish, stated by the runner, so a module asking for it is placed only where the runner answers it (A-44).Quick or thorough: thorough — a bundle had no way onto a template events stream (met twice: the zfs keeper, the zfs tools; messenger shows the same gap, noted on issue 1979).
Reviewed-by: mesh-code-reviewer of fix-1977@ace at
df2162e381Delivery
novox/mesh-tools@df2162e381f5— merged since 2026-11-13T08:00:55ZSource — source.main moved to novox/mesh-tools@af83854956. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Group
feature/1979-zfs-owns-zfs: novox/mesh-catalog@0041b69d17, novox/mesh-delivery@ad7e580918, novox/mesh-host@96a8690639, novox/mesh-sdk@2895a21e69, novox/mesh-tools@df2162e381Transitions
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: the operator's Approve of this pull request's merge into main is ended: a head it covers moved on: the heads it covers are no longer the group's heads. Nothing is merged on it. The operator is asked again once the checks pass at the new head.