R6: the gate keeps only the merge's states; walk, plan and step code and their verbs go (issue 1946) #475

Merged

mesh-tools merged 17 commits from feat/r6 into main 2026-10-24 23:00:26 +00:00

Conversation 1 Commits 17 Files Changed 93

+1535 -10787

mesh-tools commented 2026-10-24 22:17:12 +00:00

Member

Copy Link

Copy Source

The gate of release 6 (issue 1946): its table holds the merge's states only (proposed, ready, rejected, merged, held for a person); the walk, plan and step code, covering, answers, times and the controller port are deleted, and times, what-if, stalled, release, stop and retire-history leave the seat mesh-delivery. The catch-up of merges at start (the gate's earlier fix) is kept. The delivery comment and mesh/delivery drop the plan and machine steps. Three paths a local go build leaves behind are now ignored.

Tries: try-1792879382079279838 passed on d09cbf15.

Delivery group feat/r6 (design 47, milestone R6; ADR 0539, ADR 0540): mesh-sdk, mesh-host, mesh-delivery, mesh-catalog, hq, mesh-controller. One Approve for the group; its delivery is the last delivery plan the controller runs, and after it a merged change reaches each machine through its wants alone.

After the delivery: the operator's signing key is set as mesh-host's operator-signers setting, and acceptance test 18 is read live.

Release-switch: 6
Reviewed-by: reviewer-r6m@shanks at d09cbf1523
Pushed-by: lead-47@shanks

The gate of release 6 (issue 1946): its table holds the merge's states only (proposed, ready, rejected, merged, held for a person); the walk, plan and step code, covering, answers, times and the controller port are deleted, and `times`, `what-if`, `stalled`, `release`, `stop` and `retire-history` leave the seat `mesh-delivery`. The catch-up of merges at start (the gate's earlier fix) is kept. The delivery comment and `mesh/delivery` drop the plan and machine steps. Three paths a local go build leaves behind are now ignored. Tries: try-1792879382079279838 passed on d09cbf15. Delivery group feat/r6 (design 47, milestone R6; ADR 0539, ADR 0540): mesh-sdk, mesh-host, mesh-delivery, mesh-catalog, hq, mesh-controller. One Approve for the group; its delivery is the last delivery plan the controller runs, and after it a merged change reaches each machine through its wants alone. After the delivery: the operator's signing key is set as mesh-host's operator-signers setting, and acceptance test 18 is read live. Release-switch: 6 Reviewed-by: reviewer-r6m@shanks at d09cbf152317209703c663322b9e0094d7ca43cb Pushed-by: lead-47@shanks

mesh-tools added 17 commits 2026-10-24 22:17:12 +00:00

Gate keeps the merge's six states and asks the controller nothing (issue 1946, R6-C1, C2, C4) ... 5ff337e0dc

Release 6 deletes the plans: the walk half of the holder, the controller port, the carry-over of the former module and the verbs times, what-if, release, stop and retire-history go; the table holds proposed, ready, rejected, merged, held and closed; the delivery's status and view name the source revision the merge moved.

Pin the gate to mesh-sdk's release 6 verb tables and prove it holds the seat as they have it (issue 1946, R6-C3) ... 30d04f6bef

The integration tests hear the forge's own word that a pull request merged, as the real flow does, and fail on any call of the controller.

The group's integration test hears the forge's merges once both members are handed (issue 1946, R6-C3) 1a271a1fb1

The tracker derives a fix's delivered from the delivery view's event, not the gate's gone states (issue 1946) eb79996336

The backup module says on the bus when a backup asked for now has ended, so no one polls backed-up (issue 1944, ADR 0539 §16) e7ca8f7af1

Remove a binary built by mistake 2139e83a8a

A newer delivered revision covers the older merges of its repository, as the forge says ancestry (issue 1946) 8a79877a15

Pin the gate to the head of mesh-sdk feat/r6 (issue 1946) 4dee77df23

Match a fix to a delivered revision by what the gate says of its merge; keep #474's source catch-up at start (issues 1946, 1726) 05f849979c

Pin the gate to mesh-sdk feat/r6 at a523a8cb (issue 1946) 9fa6710296

The messenger holds and tells what the delivery view says is in motion, not the controller's plans (issue 1946) a17d0c8e93

Pin the gate to mesh-sdk feat/r6 at e45bdc08 (issue 1946) 3a1017f559

Pin the gate to mesh-sdk feat/r6 at 7f9cc0e5 (issue 1946) d700ceca20

Pin the gate to mesh-sdk feat/r6 at d7a9b968 (issue 1946) b67b5af5e6

Merge main into feat/r6: keep R6's gate, which already carries #474's catch-up at start, and drop the seat and walk adoption R6 removed ... 5b32342ac2

The reads-outside markers, mesh-build-go's compose job and gitea's forge-account fix come in from main.

Pin mesh-sdk to feat/r6 748c564, which carries main's composer (issue 1943) ac6712cbb5

Ignore the binaries a local go build leaves in three module roots (issue 1943) d09cbf1523

mesh-tools commented 2026-10-24 22:17:15 +00:00

Author

Member

Copy Link

Copy Source

Delivery novox/mesh-catalog@d09cbf152317 — delivering since 2026-10-24T23:19:25Z

Delivery plan — builds mesh-delivery-gate, mesh-issues, messenger, restic → ace, g14, novox, shanks; no bus step

• tier 0: mesh-delivery-gate, mesh-issues, messenger, restic
• ace: receives restic
• g14: receives restic
• novox: receives mesh-delivery-gate, mesh-issues, messenger, restic
• shanks: receives restic
• restic keeps data (ADR 0233): what it holds is backed up before it moves
• 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 restic is judged on its first machine

Group feat/r6: novox/hq@ba09497092, novox/mesh-catalog@d09cbf1523, novox/mesh-controller@9c38aed789, novox/mesh-delivery@3e863884fd, novox/mesh-host@81758b24a8, novox/mesh-sdk@748c564cdf

• composed together: pass — the checker's verdict at the members' heads (d2bc2f317716)

Transitions

• 2026-10-24 22:17 (new) → proposed (announced): novox/mesh-catalog#475's head announced
• 2026-10-24 22:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
• 2026-10-24 22:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
• 2026-10-24 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
• 2026-10-24 23:19 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-catalog@d09cbf152317` — **delivering** since 2026-10-24T23:19:25Z **Delivery plan** — builds mesh-delivery-gate, mesh-issues, messenger, restic → ace, g14, novox, shanks; no bus step - tier 0: mesh-delivery-gate, mesh-issues, messenger, restic - ace: receives restic - g14: receives restic - novox: receives mesh-delivery-gate, mesh-issues, messenger, restic - shanks: receives restic - restic keeps data (ADR 0233): what it holds is backed up before it moves - 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 restic is judged on its first machine **Group** `feat/r6`: novox/hq@ba09497092ec, novox/mesh-catalog@d09cbf152317, novox/mesh-controller@9c38aed78905, novox/mesh-delivery@3e863884fda8, novox/mesh-host@81758b24a8e4, novox/mesh-sdk@748c564cdf7c - composed together: pass — the checker's verdict at the members' heads (d2bc2f317716) **Transitions** - 2026-10-24 22:17 (new) → proposed (announced): novox/mesh-catalog#475's head announced - 2026-10-24 22:59 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-24 22:59 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-24 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-24 23:19 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-tools merged commit 2167b95a36 into main 2026-10-24 23:00:26 +00:00

mesh-tools deleted branch feat/r6 2026-10-24 23:00:26 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

mesh/ready

Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

agent-ace agent-g14 agent-novox agent-shanks jschoubben mesh-tools miel.truyen nox-agent

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-catalog#475