An issue's status lives in the issue tracker: playbook 03, cycle.py and the notes slice 3 of ADR 0275 asked for #280

Merged
mesh-admin merged 1 commits from process/issue-status-lives-in-the-tracker into main 2026-10-10 14:17:46 +00:00
Contributor

The hq half of slice 3 of to-be 53 (ADR 0275 §8): after the import, the tracker is the truth for every issue's status.

  • Playbook 03: the tracker holds the number and the status; a new report's frontmatter is opened: only, its first heading # NNN. The title; the trail and every status change go through issue-tracker.note / move. The reports numbered 001–364 keep their status: keys as the dated snapshot the import took; nobody edits them.
  • cycle.py: stops judging an issue's status, owner, fix and replay (the tracker's move refuses them at the write); keeps frontmatter-present and no-two-folders-one-number; refuses status:, located-in:, fixed-by:, amended-design:, replay: or replay-none: in a report opened from 2026-10-11 on (proved on a probe folder: refused with the key, passed without).
  • Dated notes in ADR 0019 (status in frontmatter stops holding for issues), ADR 0080 (the issue rules moved from cycle.py to the tracker's move), ADR 0275 (slice 3 built; dry run at 1ea678c6bd48f62a45db3b5e4b21b9c46867d31a on 2026-10-10: 361 folders, 27/1/48/284/1 by status, 29 unverified owners; the status keys stay as a snapshot instead of being removed; the consolidation passes are done through move/link/note, not by the import).
  • to-be 53 §2, §3, §5, §8 amended to match; AGENTS.md, process overview, 04-ISSUES/README and the three issue skills say where status lives.

All four checks green (sh merge-check.sh). Depends on mesh-catalog PR feat/mesh-issues-import being merged, rolled out and the import run once; merge this after.

The hq half of slice 3 of to-be 53 (ADR 0275 §8): after the import, the tracker is the truth for every issue's status. - **Playbook 03**: the tracker holds the number and the status; a new report's frontmatter is `opened:` only, its first heading `# NNN. The title`; the trail and every status change go through `issue-tracker.note` / `move`. The reports numbered 001–364 keep their `status:` keys as the dated snapshot the import took; nobody edits them. - **`cycle.py`**: stops judging an issue's status, owner, fix and replay (the tracker's `move` refuses them at the write); keeps frontmatter-present and no-two-folders-one-number; refuses `status:`, `located-in:`, `fixed-by:`, `amended-design:`, `replay:` or `replay-none:` in a report opened from 2026-10-11 on (proved on a probe folder: refused with the key, passed without). - Dated notes in ADR 0019 (status in frontmatter stops holding for issues), ADR 0080 (the issue rules moved from `cycle.py` to the tracker's `move`), ADR 0275 (slice 3 built; dry run at `1ea678c6bd48f62a45db3b5e4b21b9c46867d31a` on 2026-10-10: 361 folders, 27/1/48/284/1 by status, 29 unverified owners; the status keys stay as a snapshot instead of being removed; the consolidation passes are done through `move`/`link`/`note`, not by the import). - to-be 53 §2, §3, §5, §8 amended to match; AGENTS.md, process overview, 04-ISSUES/README and the three issue skills say where status lives. All four checks green (`sh merge-check.sh`). Depends on mesh-catalog PR `feat/mesh-issues-import` being merged, rolled out and the import run once; merge this after.
mesh-admin added 1 commit 2026-10-10 14:00:57 +00:00
An issue's status lives in the issue tracker: playbook 03, cycle.py and the notes slice 3 of ADR 0275 asked for
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
6d1310f1ea
Author
Contributor

Delivery novox/hq@6d1310f1eac7 — delivered since 2026-10-10T14:17:50Z

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

Transitions

  • 2026-10-10 14:01 (new) → proposed (announced): novox/hq#280's head announced
  • 2026-10-10 14:01 proposed → checked (checked): the verdict names this commit
  • 2026-10-10 14:01 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-10 14:17 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 14:17 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@6d1310f1eac7` — **delivered** since 2026-10-10T14:17:50Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 14:01 (new) → proposed (announced): novox/hq#280's head announced - 2026-10-10 14:01 proposed → checked (checked): the verdict names this commit - 2026-10-10 14:01 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 14:17 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 14:17 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 894be9971f into main 2026-10-10 14:17:46 +00:00
mesh-admin deleted branch process/issue-status-lives-in-the-tracker 2026-10-10 14:17:47 +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#280