Sets issues 296, 299 and 300 to status: resolved, with fixed-by: naming the controller's fix PR (#119, #121, #122) and replay: naming the replay in mesh-lab's register (R296, R299, R300), per playbook 03 and ADR 0237.
The replays: novox/mesh-controller PR #124 (the tests) and novox/mesh-lab PR #58 (the register). mesh-lab's prover: all three PROVED — each fails on its fix merge's first parent and passes on the fix merge.
Checks: records.py, cycle.py, index.py, words.py and sh merge-check.sh pass.
Merge after mesh-controller #124 and mesh-lab #58, so the named replays exist on their mains.
Sets issues 296, 299 and 300 to `status: resolved`, with `fixed-by:` naming the controller's fix PR (#119, #121, #122) and `replay:` naming the replay in mesh-lab's register (R296, R299, R300), per playbook 03 and ADR 0237.
The replays: novox/mesh-controller PR #124 (the tests) and novox/mesh-lab PR #58 (the register). mesh-lab's prover: all three PROVED — each fails on its fix merge's first parent and passes on the fix merge.
Checks: records.py, cycle.py, index.py, words.py and `sh merge-check.sh` pass.
Merge after mesh-controller #124 and mesh-lab #58, so the named replays exist on their mains.
Deliverynovox/hq@787f428e7e65 — delivered since 2026-10-07T21:55:22Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-07 21:45 (new) → proposed (announced): novox/hq#183's head announced
2026-10-07 21:45 proposed → checked (checked): the verdict names this commit
2026-10-07 21:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 21:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-07 21:55 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@787f428e7e65` — **delivered** since 2026-10-07T21:55:22Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-07 21:45 (new) → proposed (announced): novox/hq#183's head announced
- 2026-10-07 21:45 proposed → checked (checked): the verdict names this commit
- 2026-10-07 21:45 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-07 21:55 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-07 21:55 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.
Sets issues 296, 299 and 300 to
status: resolved, withfixed-by:naming the controller's fix PR (#119, #121, #122) andreplay:naming the replay in mesh-lab's register (R296, R299, R300), per playbook 03 and ADR 0237.The replays: novox/mesh-controller PR #124 (the tests) and novox/mesh-lab PR #58 (the register). mesh-lab's prover: all three PROVED — each fails on its fix merge's first parent and passes on the fix merge.
Checks: records.py, cycle.py, index.py, words.py and
sh merge-check.shpass.Merge after mesh-controller #124 and mesh-lab #58, so the named replays exist on their mains.
Delivery
novox/hq@787f428e7e65— delivered since 2026-10-07T21:55:22ZDelivery 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.