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.
Deliverynovox/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`.
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.
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
resolvedhere already.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.batch-not-cut: a batch still assembling a minute pastmerge-window-at-mostwith 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.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.shexits 0.Delivery
novox/hq@952c984c3450— delivered since 2026-10-10T12:43:37ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.