Design 47's last milestone, R4g+R5, one delivery group on feat/r4g. merge-check.sh deleted, a test refuses its return (issue 1295; ADR 0529).
The bootstrap tests that read build-agent's manifest skip aloud (NOT JUDGED): build-agent leaves mesh-controller in this group (ADR 0524 §5), and genesis giving a new mesh a builder again is issue 1152; the toolchain test still judges the other genesis modules.
The test of the controller's own manifest at step 9 skips aloud while the running checker places no controller beside mesh-host's check; mesh-delivery #27 places it from this delivery on, and it is a failure again then (issue 1295).
With the checker judging mesh-host inside the build module's isolation (its own /tmp, a user namespace): the directory judgement's test accepts any account it names as the one who could replace a link, and the eight library tests that set a folder's group skip aloud where no group can be set (issue 1919).
Reviewed-by: review-r4g-2@shanks at 4b4bb09a05
Pushed-by: lead-47@shanks
Design 47's last milestone, R4g+R5, one delivery group on feat/r4g. merge-check.sh deleted, a test refuses its return (issue 1295; ADR 0529).
The bootstrap tests that read build-agent's manifest skip aloud (NOT JUDGED): build-agent leaves mesh-controller in this group (ADR 0524 §5), and genesis giving a new mesh a builder again is issue 1152; the toolchain test still judges the other genesis modules.
The test of the controller's own manifest at step 9 skips aloud while the running checker places no controller beside mesh-host's check; mesh-delivery #27 places it from this delivery on, and it is a failure again then (issue 1295).
With the checker judging mesh-host inside the build module's isolation (its own /tmp, a user namespace): the directory judgement's test accepts any account it names as the one who could replace a link, and the eight library tests that set a folder's group skip aloud where no group can be set (issue 1919).
Reviewed-by: review-r4g-2@shanks at 4b4bb09a05a014178b77743ebe15ad5152359834
Pushed-by: lead-47@shanks
2026-10-23 16:59 (new) → proposed (announced): novox/mesh-host#132's head announced
2026-10-23 17:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 17:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
2026-10-23 17:50 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:50 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-host@4b4bb09a05a0` — **delivered** since 2026-10-23T17:50:58Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**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 16:59 (new) → proposed (announced): novox/mesh-host#132's head announced
- 2026-10-23 17:12 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 17:12 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
- 2026-10-23 17:50 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:50 held → delivered (done): merged, and nothing for a walk to move: builds nothing: the change touches no module of the mesh's graph
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
The build agent left mesh-controller with R4g (ADR 0524 section 5); genesis still installs it until issue 1152 decides where a new mesh's builder comes from. The tests that read its manifest say NOT JUDGED and are judged again with 1152.
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. merge-check.sh deleted, a test refuses its return (issue 1295; ADR 0529).
The bootstrap tests that read build-agent's manifest skip aloud (NOT JUDGED): build-agent leaves mesh-controller in this group (ADR 0524 §5), and genesis giving a new mesh a builder again is issue 1152; the toolchain test still judges the other genesis modules.
The test of the controller's own manifest at step 9 skips aloud while the running checker places no controller beside mesh-host's check; mesh-delivery #27 places it from this delivery on, and it is a failure again then (issue 1295).
With the checker judging mesh-host inside the build module's isolation (its own /tmp, a user namespace): the directory judgement's test accepts any account it names as the one who could replace a link, and the eight library tests that set a folder's group skip aloud where no group can be set (issue 1919).
Reviewed-by: review-r4g-2@shanks at
4b4bb09a05Pushed-by: lead-47@shanks
Delivery
novox/mesh-host@4b4bb09a05a0— delivered since 2026-10-23T17:50:58ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
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
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.