This registers issue 296, at status located, with a report and a diagnosis.
plans counted a plan's time from its last save. Every advance saved the plan, even when nothing had changed. So a build queued for minutes read as "building for 1s" and was never LATE. The cause is in the controller, and the fix is mesh-controller PR #119, which is open. LATE now uses the stalled condition's start time and bound.
This is a core issue. When it resolves, it needs replay: or replay-none: (ADR 0237).
The number is free across main and every open branch; 295 is taken on issues/295-…. records.py, cycle.py, index.py and sh merge-check.sh all pass.
This registers issue 296, at status `located`, with a report and a diagnosis.
`plans` counted a plan's time from its last save. Every advance saved the plan, even when nothing had changed. So a build queued for minutes read as "building for 1s" and was never LATE. The cause is in the controller, and the fix is mesh-controller PR #119, which is open. LATE now uses the stalled condition's start time and bound.
This is a core issue. When it resolves, it needs `replay:` or `replay-none:` (ADR 0237).
The number is free across main and every open branch; 295 is taken on `issues/295-…`. records.py, cycle.py, index.py and `sh merge-check.sh` all pass.
plans counted a plan's time from its last save, and every advance saved it, so a queued build read
as seconds old and was never late; located in the controller, fix in mesh-controller PR #119.
Deliverynovox/hq@6caa471ed032 — delivered since 2026-10-07T19:05:19Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-07 18:47 (new) → proposed (announced): novox/hq#175's head announced
2026-10-07 18:48 proposed → checked (checked): the verdict names this commit
2026-10-07 18:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-07 19:05 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 19:05 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@6caa471ed032` — **delivered** since 2026-10-07T19:05:19Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-07 18:47 (new) → proposed (announced): novox/hq#175's head announced
- 2026-10-07 18:48 proposed → checked (checked): the verdict names this commit
- 2026-10-07 18:48 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-07 19:05 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 19:05 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.
This registers issue 296, at status
located, with a report and a diagnosis.planscounted a plan's time from its last save. Every advance saved the plan, even when nothing had changed. So a build queued for minutes read as "building for 1s" and was never LATE. The cause is in the controller, and the fix is mesh-controller PR #119, which is open. LATE now uses the stalled condition's start time and bound.This is a core issue. When it resolves, it needs
replay:orreplay-none:(ADR 0237).The number is free across main and every open branch; 295 is taken on
issues/295-…. records.py, cycle.py, index.py andsh merge-check.shall pass.Delivery
novox/hq@6caa471ed032— delivered since 2026-10-07T19:05:19ZDelivery 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.