Issue 362 resolved: ADR 0276 gains the own-path batch rule and a progressive insight, to-be 45 gains S18 and S19 #277

Merged
mesh-admin merged 1 commits from issues/362-resolved into main 2026-10-10 12:43:19 +00:00
Contributor

Closes the record of issue 362 (two merges seconds apart left their delivery waiting for a person) now that both sides of ADR 0276 are built. Merge after mesh-controller#197 has rolled out: the issue is set resolved here already.

  • ADR 0276: a dated decision note, decided during the build on 2026-10-10 on the operator's delegation: a merge on the controller's own path never shares a batch with a merge that waits for mesh-delivery's word (its own batch and window; the catalogue batch cuts by the normal rules and queues behind the own-path walk; an own-path walk folds no waiting catalogue walk but batches its merges again behind it). Checked by the controller's TestAMergeOnTheControllersPathNeverSharesABatch. And a progressive insight: the controller has no consolidated schema file (a fresh install runs the embedded numbered migrations), so the consequence "and in the consolidated schema" was wrong for the controller; the decision stands.
  • To-be 47: the same rule as a bullet in The merge window and the batch.
  • To-be 45: the signals table gains S18 (batch-not-cut: a batch still assembling a minute past merge-window-at-most with no walk open) and S19 (batch-behind-walk: a batch queued behind an open walk past that walk's bound, naming it); ADR 0276 added to its decisions.
  • Issue 362: status: resolved, fixed-by: mesh-catalog#171, mesh-controller#197, replay: R362 (registered in mesh-lab#75), and a dated Resolved paragraph.

Checks run locally: records, index, words, cycle all pass; merge-check.sh exits 0.

Closes the record of issue 362 (two merges seconds apart left their delivery waiting for a person) now that both sides of ADR 0276 are built. **Merge after mesh-controller#197 has rolled out**: the issue is set `resolved` here already. - **ADR 0276**: a dated decision note, decided during the build on 2026-10-10 on the operator's delegation: a merge on the controller's own path never shares a batch with a merge that waits for mesh-delivery's word (its own batch and window; the catalogue batch cuts by the normal rules and queues behind the own-path walk; an own-path walk folds no waiting catalogue walk but batches its merges again behind it). Checked by the controller's `TestAMergeOnTheControllersPathNeverSharesABatch`. And a progressive insight: the controller has no consolidated schema file (a fresh install runs the embedded numbered migrations), so the consequence "and in the consolidated schema" was wrong for the controller; the decision stands. - **To-be 47**: the same rule as a bullet in *The merge window and the batch*. - **To-be 45**: the signals table gains S18 (`batch-not-cut`: a batch still assembling a minute past `merge-window-at-most` with no walk open) and S19 (`batch-behind-walk`: a batch queued behind an open walk past that walk's bound, naming it); ADR 0276 added to its decisions. - **Issue 362**: `status: resolved`, `fixed-by: mesh-catalog#171, mesh-controller#197`, `replay: R362` (registered in mesh-lab#75), and a dated *Resolved* paragraph. Checks run locally: records, index, words, cycle all pass; `merge-check.sh` exits 0.
mesh-admin added 1 commit 2026-10-10 12:15:15 +00:00
Issue 362 resolved: ADR 0276 gains the own-path batch rule and a progressive insight, to-be 45 gains S18 and S19
mesh/merge-gate pass: the change touches no module of the mesh's graph
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery delivered
952c984c34
Author
Contributor

Delivery novox/hq@952c984c3450 — delivered since 2026-10-10T12:43:37Z

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

Transitions

  • 2026-10-10 12:15 (new) → proposed (announced): novox/hq#277's head announced
  • 2026-10-10 12:17 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 12:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 12:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-10 12:43 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-delivery:view --> **Delivery** `novox/hq@952c984c3450` — **delivered** since 2026-10-10T12:43:37Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 12:15 (new) → proposed (announced): novox/hq#277's head announced - 2026-10-10 12:17 proposed → checked (checked): the verdict names this commit - 2026-10-10 12:17 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 12:43 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 12:43 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 76bb721cf4 into main 2026-10-10 12:43:19 +00:00
mesh-admin deleted branch issues/362-resolved 2026-10-10 12:43:19 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/hq#277