Triage of the unresolved issues 279 to 298, done on 2026-10-08.
Resolved (12):
292 with replay: R292.
298 with replay: R298. Both replays are new: novox/mesh-controller #129 adds the tests and novox/mesh-lab #60 registers them. The prover says PROVED for both, failing before the fix and passing on it. Merge those two first.
293 with replay-none: the fix is in the forge module's TypeScript, and the prover runs only Go.
295 with replay-none: the fix lives inside a whole send over the bus, and the fix's own test uses the marker the fix added.
280, 281, 285, 286, 287, 289, 290, 291. For 285, 287, 289 and 291 the prover was run on 2026-10-08: each fix's tests do not build at the commit before the fix, so replay-none says so.
records.py, cycle.py, index.py, words.py and merge-check.sh pass. cycle.py checks that replay: R292 and replay: R298 are well-formed, but not that the register holds them, so merging this before mesh-lab #60 is safe for the check. In meaning, though, it should follow #60.
Triage of the unresolved issues 279 to 298, done on 2026-10-08.
**Resolved (12):**
- **292** with `replay: R292`.
- **298** with `replay: R298`. Both replays are new: novox/mesh-controller #129 adds the tests and novox/mesh-lab #60 registers them. The prover says PROVED for both, failing before the fix and passing on it. Merge those two first.
- **293** with `replay-none`: the fix is in the forge module's TypeScript, and the prover runs only Go.
- **295** with `replay-none`: the fix lives inside a whole send over the bus, and the fix's own test uses the marker the fix added.
- **280, 281, 285, 286, 287, 289, 290, 291.** For 285, 287, 289 and 291 the prover was run on 2026-10-08: each fix's tests do not build at the commit before the fix, so `replay-none` says so.
**Re-checked, still holds:**
279, 282 (partly fixed), 288 (partly fixed), 294.
records.py, cycle.py, index.py, words.py and merge-check.sh pass. cycle.py checks that `replay: R292` and `replay: R298` are well-formed, but not that the register holds them, so merging this before mesh-lab #60 is safe for the check. In meaning, though, it should follow #60.
292 and 298 resolve with replays now registered in mesh-lab. The other fixed
core issues say why no replay can be laid over the commit before their fix. The
rest are re-checked against main.
Deliverynovox/hq@64e97d0de18c — delivered since 2026-10-07T23:42:10Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-07 23:31 (new) → proposed (announced): novox/hq#188's head announced
2026-10-07 23:32 proposed → checked (checked): the verdict names this commit
2026-10-07 23:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 23:42 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 23:42 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@64e97d0de18c` — **delivered** since 2026-10-07T23:42:10Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-07 23:31 (new) → proposed (announced): novox/hq#188's head announced
- 2026-10-07 23:32 proposed → checked (checked): the verdict names this commit
- 2026-10-07 23:32 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-07 23:42 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 23:42 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.
Triage of the unresolved issues 279 to 298, done on 2026-10-08.
Resolved (12):
replay: R292.replay: R298. Both replays are new: novox/mesh-controller #129 adds the tests and novox/mesh-lab #60 registers them. The prover says PROVED for both, failing before the fix and passing on it. Merge those two first.replay-none: the fix is in the forge module's TypeScript, and the prover runs only Go.replay-none: the fix lives inside a whole send over the bus, and the fix's own test uses the marker the fix added.replay-nonesays so.Re-checked, still holds:
279, 282 (partly fixed), 288 (partly fixed), 294.
records.py, cycle.py, index.py, words.py and merge-check.sh pass. cycle.py checks that
replay: R292andreplay: R298are well-formed, but not that the register holds them, so merging this before mesh-lab #60 is safe for the check. In meaning, though, it should follow #60.Delivery
novox/hq@64e97d0de18c— delivered since 2026-10-07T23:42:10ZDelivery 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.