The operator, 2026-10-15: add to playbook 08 that a small fix may handle a few related issues in one go. Case in point: issues 743 (the clipboard's history daemon not running) and 750 (the history tool handing out every copied entry) — fixing 743 alone would have made 750 worse.
The rule: two or three related issues, same repository, mostly the same module, together about an hour; they touch the same files, or one is wrong or unsafe without the other. Each issue named in the commit and the pull request, moved to fixing, and resolved on its own once delivered. More is a feature (playbook 07).
A few lines; per playbook 08 its review is the operator's word. sh merge-check.sh passes.
The operator, 2026-10-15: add to playbook 08 that a small fix may handle a few related issues in one go. Case in point: issues 743 (the clipboard's history daemon not running) and 750 (the history tool handing out every copied entry) — fixing 743 alone would have made 750 worse.
The rule: two or three related issues, same repository, mostly the same module, together about an hour; they touch the same files, or one is wrong or unsafe without the other. Each issue named in the commit and the pull request, moved to fixing, and resolved on its own once delivered. More is a feature (playbook 07).
A few lines; per playbook 08 its review is the operator's word. `sh merge-check.sh` passes.
Deliverynovox/hq@a227f98bddd4 — delivered since 2026-10-15T20:38:42Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-15 20:37 (new) → proposed (announced): novox/hq#368's head announced
2026-10-15 20:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
2026-10-15 20:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-15 20:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-15 20:38 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@a227f98bddd4` — **delivered** since 2026-10-15T20:38:42Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-15 20:37 (new) → proposed (announced): novox/hq#368's head announced
- 2026-10-15 20:38 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
- 2026-10-15 20:38 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-15 20:38 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-15 20:38 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.
The operator, 2026-10-15: add to playbook 08 that a small fix may handle a few related issues in one go. Case in point: issues 743 (the clipboard's history daemon not running) and 750 (the history tool handing out every copied entry) — fixing 743 alone would have made 750 worse.
The rule: two or three related issues, same repository, mostly the same module, together about an hour; they touch the same files, or one is wrong or unsafe without the other. Each issue named in the commit and the pull request, moved to fixing, and resolved on its own once delivered. More is a feature (playbook 07).
A few lines; per playbook 08 its review is the operator's word.
sh merge-check.shpasses.ready at
a227f98bdd(the operator's word, 2026-10-15: "yes, add it to playbook 08").Delivery
novox/hq@a227f98bddd4— delivered since 2026-10-15T20:38:42ZDelivery 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.