Design 47's last milestone, R4g+R5, one delivery group on feat/r4g.
The runtime's mesh/seat.pull and mesh/seat.settle: one Fetch(1) from the listed worker (issue 1887).
merge-check.sh deleted, its steps as tests; the root image module removed (issue 1295, issue 979; ADR 0524 §5, 0529).
Reviewed-by: review-r4g@shanks at 860043fd7f
Pushed-by: lead-47@shanks
Design 47's last milestone, R4g+R5, one delivery group on feat/r4g.
- The runtime's mesh/seat.pull and mesh/seat.settle: one Fetch(1) from the listed worker (issue 1887).
- merge-check.sh deleted, its steps as tests; the root image module removed (issue 1295, issue 979; ADR 0524 §5, 0529).
Reviewed-by: review-r4g@shanks at 860043fd7fa0fbe085c8f8cfffe0048890aa5cdb
Pushed-by: lead-47@shanks
mesh/check failed: g14: novox/mesh-catalog#464: checks/health/go.mod names mesh-sdk a9560890ee26, which is neither on mesh-sdk's trunk nor the group's…
Deliverynovox/mesh-tools@860043fd7fa0 — failed since 2026-10-23T17:59:26Z
Delivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
tier 0: 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
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before node-tools is judged on its first machine
2026-10-23 15:06 (new) → proposed (announced): novox/mesh-tools#40's head announced
2026-10-23 15:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 15:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-23 17:51 rejected → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's plans go
2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-tools@860043fd7fa0` — **failed** since 2026-10-23T17:59:26Z
**Delivery plan** — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
- tier 0: 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
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before node-tools is judged on its first machine
**Group** `feat/r4g`: novox/hq@e8bd9171cdbc, novox/mesh-catalog@454fb8a918ad, novox/mesh-controller@c9a7102bc53b, novox/mesh-delivery@b2c545c40aec, novox/mesh-host@4b4bb09a05a0, novox/mesh-lab@4653b17e18a7, novox/mesh-media-catalog@f4f0bbcfe59c, novox/mesh-sdk@a2c813a6b468, novox/mesh-tools-go@5023de36fded, novox/mesh-tools@860043fd7fa0, novox/okioki@e67d21e8b448
**Transitions**
- 2026-10-23 15:06 (new) → proposed (announced): novox/mesh-tools#40's head announced
- 2026-10-23 15:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 15:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-23 17:51 rejected → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on
- 2026-10-23 17:55 held → delivering (go): its walk started on a word that was not this owner's: the controller's own path, which waits for nobody, or a person's `plans go`
- 2026-10-23 17:59 delivering → failed (failed): its walk failed, carrying its own commit: a gate on a first machine (what it carried put back), a build, a machine
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
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.
Design 47's last milestone, R4g+R5, one delivery group on feat/r4g.
Reviewed-by: review-r4g@shanks at
860043fd7fPushed-by: lead-47@shanks
Delivery
novox/mesh-tools@860043fd7fa0— failed since 2026-10-23T17:59:26ZDelivery plan — builds mesh-tools, node-tools → ace, g14, novox, shanks; no bus step
Group
feat/r4g: novox/hq@e8bd9171cd, novox/mesh-catalog@454fb8a918, novox/mesh-controller@c9a7102bc5, novox/mesh-delivery@b2c545c40a, novox/mesh-host@4b4bb09a05, novox/mesh-lab@4653b17e18, novox/mesh-media-catalog@f4f0bbcfe5, novox/mesh-sdk@a2c813a6b4, novox/mesh-tools-go@5023de36fd, novox/mesh-tools@860043fd7f, novox/okioki@e67d21e8b4Transitions
plans goThe commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.