Register R336: a send held for the bus's planned step is told to the operator #73

2026-10-09T07:25:36Z

mesh-admin commented

2026-10-09 07:25:36 +00:00

hq issue 336 is a core issue, so it resolves with replay: R336 (ADR 0237).

Entry: R336, InRepository, mesh-controller. Fix b13a0f7 is the merge of mesh-controller #173, proved against its first parent. The test is TestReplay336, in cmd/mesh-controller/replay336_test.go.
Proved by hand, with go run ./cmd/prove --repos ../.. R336 and a throwaway postgres: R336 (issue 336): PROVED — before its fix fails, on its fix passes. Before the fix it fails with: "the first tick after the refusal told the operator nothing about the bus's step: 0 condition(s)".
replays/merge-check.sh passes.

Once merged, issue 336 can be set resolved with fixed-by: mesh-controller#173 and replay: R336.

hq issue 336 is a core issue, so it resolves with `replay: R336` (ADR 0237). - **Entry:** `R336`, InRepository, mesh-controller. Fix `b13a0f7` is the merge of mesh-controller #173, proved against its first parent. The test is `TestReplay336`, in `cmd/mesh-controller/replay336_test.go`. - **Proved by hand**, with `go run ./cmd/prove --repos ../.. R336` and a throwaway postgres: `R336 (issue 336): PROVED — before its fix fails, on its fix passes`. Before the fix it fails with: "the first tick after the refusal told the operator nothing about the bus's step: 0 condition(s)". - `replays/merge-check.sh` passes. Once merged, issue 336 can be set resolved with `fixed-by: mesh-controller#173` and `replay: R336`.

mesh-admin added 1 commit 2026-10-09 07:25:36 +00:00

Register R336: a send held for the bus's planned step is told to the operator

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go)

Details

mesh/delivery delivered

Details

fb5bb1e3de

hq issue 336 is a core issue and resolves with its replay. TestReplay336 in the controller, merged with
#173 (b13a0f7), fails on its first parent and passes on it: prove R336 says PROVED.

mesh-admin commented

2026-10-09 07:25:48 +00:00

Delivery novox/mesh-lab@fb5bb1e3de04 — delivered since 2026-10-09T07:29:42Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-09 07:25 (new) → proposed (announced): novox/mesh-lab#73's head announced
2026-10-09 07:26 proposed → checked (checked): the verdict names this commit
2026-10-09 07:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 07:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 07:29 published → delivered (done): nothing for a walk to move

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

**Delivery** `novox/mesh-lab@fb5bb1e3de04` — **delivered** since 2026-10-09T07:29:42Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-09 07:25 (new) → proposed (announced): novox/mesh-lab#73's head announced - 2026-10-09 07:26 proposed → checked (checked): the verdict names this commit - 2026-10-09 07:26 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-09 07:29 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-09 07:29 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin merged commit d9173d49b8 into main

2026-10-09 07:29:35 +00:00

mesh-admin deleted branch replays/336-a-send-held-for-the-bus-step

2026-10-09 07:29:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#73