Issue 1886 (critical), note 7: R4e's plan plan-1792707174627079192 was stopped by hand at 02:01 on 2026-10-23 (the operator's urgent word) to free the check queue; plans retry refused a stopped plan with no failed module, and catch-up skips recorded merges, so nothing could carry its 48 remaining modules on. Decision: ADR 0523 (accepted).
Now plans retry resumes a plan a person stopped while its current tier still waited (asked, built and not sent, or not yet asked; none failed): it is set building again with its stop cleared and its asks kept; build-agent's own key-marked modules (ADR 0522 §6) are set unasked so the next look asks them of build-agent; nothing is asked by the verb. Refused as any retry beside a related open plan, when a newer open plan of its branch exists, or when a newer plan holds a module of the current tier that already holds a build not yet sent (holdingABuild); a plan whose stop left merges out is refused as before (ADR 0299).
Tests: TestRetryResumesAWalkStoppedByHand (every refusal of the stopped path), TestResumeIsNotRefusedByANewerPlanOfAModuleNotYetAsked; seen failing first except the two refusal cases added at 55ba7f2c, which the code already met. Unit suite and vet (with and without the integration tag) green. No try: the try verb is served by R4e's checker, which this very resume delivers.
After delivery: mesh-controller.plans {retry: plan-1792707174627079192}.
Reviewed-by: review-1886-resume@shanks at 55ba7f2cb8
Issue 1886 (critical), note 7: R4e's plan plan-1792707174627079192 was stopped by hand at 02:01 on 2026-10-23 (the operator's urgent word) to free the check queue; `plans retry` refused a stopped plan with no failed module, and catch-up skips recorded merges, so nothing could carry its 48 remaining modules on. Decision: ADR 0523 (accepted).
Now `plans retry` resumes a plan a person stopped while its current tier still waited (asked, built and not sent, or not yet asked; none failed): it is set building again with its stop cleared and its asks kept; build-agent's own key-marked modules (ADR 0522 §6) are set unasked so the next look asks them of build-agent; nothing is asked by the verb. Refused as any retry beside a related open plan, when a newer open plan of its branch exists, or when a newer plan holds a module of the current tier that already holds a build not yet sent (holdingABuild); a plan whose stop left merges out is refused as before (ADR 0299).
Tests: TestRetryResumesAWalkStoppedByHand (every refusal of the stopped path), TestResumeIsNotRefusedByANewerPlanOfAModuleNotYetAsked; seen failing first except the two refusal cases added at 55ba7f2c, which the code already met. Unit suite and vet (with and without the integration tag) green. No try: the try verb is served by R4e's checker, which this very resume delivers.
After delivery: mesh-controller.plans {retry: plan-1792707174627079192}.
Reviewed-by: review-1886-resume@shanks at 55ba7f2cb83cdcd3f74bb6f5b679c67156e474c5
mesh/merge-gate head 102f8dc2674e merged into trunk 296e11d499cb — pass: builds mesh-controller → novox; no bus step; the change touches no module of the m…
Deliverynovox/mesh-controller@55ba7f2cb83c — delivered since 2026-10-23T05:42:59Z
Delivery plan — builds mesh-controller → novox; no bus step
tier 0: mesh-controller
novox: receives mesh-controller
Machines
mesh-controller on every machine running it: sent
Transitions
2026-10-23 00:45 (new) → proposed (announced): novox/mesh-controller#443's head announced
2026-10-23 00:53 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-23 00:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-23 05:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-23 05:41 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
2026-10-23 05:42 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@55ba7f2cb83c` — **delivered** since 2026-10-23T05:42:59Z
**Delivery plan** — builds mesh-controller → novox; no bus step
- tier 0: mesh-controller
- novox: receives mesh-controller
**Machines**
- mesh-controller on every machine running it: sent
**Transitions**
- 2026-10-23 00:45 (new) → proposed (announced): novox/mesh-controller#443's head announced
- 2026-10-23 00:53 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-23 00:53 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-23 05:41 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-23 05:41 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
- 2026-10-23 05:42 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate head 55ba7f2cb83c merged into trunk 296e11d499cb — pass: builds mesh-controller → novox; no bus step; the change touches no module of the m…
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 102f8dc267 is no longer the pull request's head, or the pull request closed. 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: its head 102f8dc2674e is no longer the pull request's head, or the pull request closed. 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 1886 (critical), note 7: R4e's plan plan-1792707174627079192 was stopped by hand at 02:01 on 2026-10-23 (the operator's urgent word) to free the check queue;
plans retryrefused a stopped plan with no failed module, and catch-up skips recorded merges, so nothing could carry its 48 remaining modules on. Decision: ADR 0523 (accepted).Now
plans retryresumes a plan a person stopped while its current tier still waited (asked, built and not sent, or not yet asked; none failed): it is set building again with its stop cleared and its asks kept; build-agent's own key-marked modules (ADR 0522 §6) are set unasked so the next look asks them of build-agent; nothing is asked by the verb. Refused as any retry beside a related open plan, when a newer open plan of its branch exists, or when a newer plan holds a module of the current tier that already holds a build not yet sent (holdingABuild); a plan whose stop left merges out is refused as before (ADR 0299).Tests: TestRetryResumesAWalkStoppedByHand (every refusal of the stopped path), TestResumeIsNotRefusedByANewerPlanOfAModuleNotYetAsked; seen failing first except the two refusal cases added at
55ba7f2c, which the code already met. Unit suite and vet (with and without the integration tag) green. No try: the try verb is served by R4e's checker, which this very resume delivers.After delivery: mesh-controller.plans {retry: plan-1792707174627079192}.
Reviewed-by: review-1886-resume@shanks at
55ba7f2cb8Delivery
novox/mesh-controller@55ba7f2cb83c— delivered since 2026-10-23T05:42:59ZDelivery plan — builds mesh-controller → novox; no bus step
Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
102f8dc2Judged: head
102f8dc2674emerged into trunk296e11d499cb; read beside it: mesh-catalog89e15c7bcda6, mesh-controller-main296e11d499cb, mesh-host48c3e3834c69, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792715774631034166(builds --log build-1792715774631034166).mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head
102f8dc267is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.Merge check at
55ba7f2cJudged: head
55ba7f2cb83cmerged into trunk296e11d499cb; read beside it: mesh-catalog89e15c7bcda6, mesh-controller-main296e11d499cb, mesh-host48c3e3834c69, mesh-toolse0fadc43d9ddmesh/merge-gate: PASS — the change touches no module of the mesh's graphmesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-controller → novox; no bus step
Run by the build seat on ace as
build-1792716304580697539(builds --log build-1792716304580697539).