One group with mesh-delivery, mesh-catalog, mesh-host and hq, all on the branch feat/774-vault-mints-l2 (the old feat/774-vault-mints holds stale commits). This head 8eafc0c is the reviewed 4e6e5cc rebased onto main with #120 and #121, unchanged otherwise; every member pins it exactly.
Under L2: the placement reader (delivery.Placed, buildrun.ToolchainGate) names the seat mesh-placement's state held by the assigner; the seat count is 49 (mesh-placement, mesh-delivery-checker, node-engine).
Tests: 1682 unit, 42 integration (approved head: 1683, 42).
L3 (issue 774, ADR 0561), rebased onto L2.
One group with mesh-delivery, mesh-catalog, mesh-host and hq, all on the branch feat/774-vault-mints-l2 (the old feat/774-vault-mints holds stale commits). This head 8eafc0c is the reviewed 4e6e5cc rebased onto main with #120 and #121, unchanged otherwise; every member pins it exactly.
Under L2: the placement reader (delivery.Placed, buildrun.ToolchainGate) names the seat mesh-placement's state held by the assigner; the seat count is 49 (mesh-placement, mesh-delivery-checker, node-engine).
Tests: 1682 unit, 42 integration (approved head: 1683, 42).
Reviewed-by: rev-l2@shanks at 8eafc0c5ce3cbb54a1a0b8a07beb55eab058a155
mesh/delivery-group group feat/774-vault-mints-l2 checking: the checker's verdict is out of date: novox/mesh-delivery@f6df07605dd0 was judged on trunk 5b2e5bc5…
2026-10-28 20:56 (new) → proposed (announced): novox/mesh-sdk#123's head announced
2026-10-28 20: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)
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-sdk@8eafc0c5ce3c` — **ready** since 2026-10-28T20:56:46Z
**Group** `feat/774-vault-mints-l2`: novox/hq@7d022710b34b, novox/mesh-catalog@c193d2b38970, novox/mesh-delivery@f6df07605dd0, novox/mesh-host@e0c7f36ca90c, novox/mesh-sdk@8eafc0c5ce3c
**Transitions**
- 2026-10-28 20:56 (new) → proposed (announced): novox/mesh-sdk#123's head announced
- 2026-10-28 20: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)
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
Closed for #126, which carries this same head 8eafc0c on its own branch (feat/774-vault-mints-sdk). L3's group check failed at 22:18Z on the composition misfire the seed fix group met: a group with a mesh-sdk member asks every reader module to read the group's manifests, and a stand-by controller build pinning mesh-sdk 748c564 cannot read the assigner's mesh-placement claim, which this group does not change. So mesh-sdk is checked and merged first, alone, and the four members of feat/774-vault-mints-l2 (mesh-delivery #105, mesh-catalog #556, mesh-host #168, hq #495), which pin 8eafc0c, pass their check after it merges.
Closed for #126, which carries this same head 8eafc0c on its own branch (feat/774-vault-mints-sdk). L3's group check failed at 22:18Z on the composition misfire the seed fix group met: a group with a mesh-sdk member asks every reader module to read the group's manifests, and a stand-by controller build pinning mesh-sdk 748c564 cannot read the assigner's mesh-placement claim, which this group does not change. So mesh-sdk is checked and merged first, alone, and the four members of feat/774-vault-mints-l2 (mesh-delivery #105, mesh-catalog #556, mesh-host #168, hq #495), which pin 8eafc0c, pass their check after it merges.
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.
L3 (issue 774, ADR 0561), rebased onto L2.
One group with mesh-delivery, mesh-catalog, mesh-host and hq, all on the branch feat/774-vault-mints-l2 (the old feat/774-vault-mints holds stale commits). This head
8eafc0cis the reviewed 4e6e5cc rebased onto main with #120 and #121, unchanged otherwise; every member pins it exactly.Under L2: the placement reader (delivery.Placed, buildrun.ToolchainGate) names the seat mesh-placement's state held by the assigner; the seat count is 49 (mesh-placement, mesh-delivery-checker, node-engine).
Tests: 1682 unit, 42 integration (approved head: 1683, 42).
Reviewed-by: rev-l2@shanks at
8eafc0c5ceDelivery
novox/mesh-sdk@8eafc0c5ce3c— ready since 2026-10-28T20:56:46ZGroup
feat/774-vault-mints-l2: novox/hq@7d022710b3, novox/mesh-catalog@c193d2b389, novox/mesh-delivery@f6df07605d, novox/mesh-host@e0c7f36ca9, novox/mesh-sdk@8eafc0c5ceTransitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.Closed for #126, which carries this same head
8eafc0con its own branch (feat/774-vault-mints-sdk). L3's group check failed at 22:18Z on the composition misfire the seed fix group met: a group with a mesh-sdk member asks every reader module to read the group's manifests, and a stand-by controller build pinning mesh-sdk748c564cannot read the assigner's mesh-placement claim, which this group does not change. So mesh-sdk is checked and merged first, alone, and the four members of feat/774-vault-mints-l2 (mesh-delivery #105, mesh-catalog #556, mesh-host #168, hq #495), which pin8eafc0c, pass their check after it merges.Pull request closed