The mesh-watcher definition said "report and end" at five minutes without a change, so every quiet but expected wait (a check running, a held take-in, an operator's answer) ended the watcher. The wait was then left unwatched until the lead noticed. On 2026-11-09 this happened four times in one session.
Now the watcher sends reports along the way with SendMessage to main and keeps watching. Its final message ends it only at the end, a failure, the bound, or a call that failed twice. The definition gains the SendMessage tool.
Checked: hq's go test ./... passes, words test included. The change agrees with await-every-approval, nothing-moved-in-five-minutes and playbook 07's waits. Proven live by the watcher on the group fix/1966-forge-made-merge, started with this rule in its hand-over.
To follow: playbook 07's line on a watcher's end (lines 618-619) could name the reports along the way; not in this change.
Note: this pull request was opened before its review, against how-work-is-done; the review followed at the same head.
Reviewed-by: mesh-code-reviewer@shanks (for fix-1965) at c57930a759
The mesh-watcher definition said "report and end" at five minutes without a change, so every quiet but expected wait (a check running, a held take-in, an operator's answer) ended the watcher. The wait was then left unwatched until the lead noticed. On 2026-11-09 this happened four times in one session.
Now the watcher sends reports along the way with SendMessage to main and keeps watching. Its final message ends it only at the end, a failure, the bound, or a call that failed twice. The definition gains the SendMessage tool.
Checked: hq's go test ./... passes, words test included. The change agrees with await-every-approval, nothing-moved-in-five-minutes and playbook 07's waits. Proven live by the watcher on the group fix/1966-forge-made-merge, started with this rule in its hand-over.
To follow: playbook 07's line on a watcher's end (lines 618-619) could name the reports along the way; not in this change.
Note: this pull request was opened before its review, against how-work-is-done; the review followed at the same head.
Reviewed-by: mesh-code-reviewer@shanks (for fix-1965) at c57930a759882361cb701de81b5b7f3d8df2be31
https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
On 2026-11-09 four watchers in one session ended at their first five-minute report,
leaving waits unwatched while a check, a take-in and an answer were still to come.
Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Deliverynovox/hq@c57930a75988 — merged since 2026-11-09T08:49:47Z
Source — source.main moved to novox/hq@3cf28e840d. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-09 08:31 (new) → proposed (announced): novox/hq#528's head announced
2026-11-09 08:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-09 08:49 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@c57930a75988` — **merged** since 2026-11-09T08:49:47Z
**Source** — source.main moved to novox/hq@3cf28e840de3. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-09 08:31 (new) → proposed (announced): novox/hq#528's head announced
- 2026-11-09 08:31 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-09 08:49 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `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 mesh-watcher definition said "report and end" at five minutes without a change, so every quiet but expected wait (a check running, a held take-in, an operator's answer) ended the watcher. The wait was then left unwatched until the lead noticed. On 2026-11-09 this happened four times in one session.
Now the watcher sends reports along the way with SendMessage to main and keeps watching. Its final message ends it only at the end, a failure, the bound, or a call that failed twice. The definition gains the SendMessage tool.
Checked: hq's go test ./... passes, words test included. The change agrees with await-every-approval, nothing-moved-in-five-minutes and playbook 07's waits. Proven live by the watcher on the group fix/1966-forge-made-merge, started with this rule in its hand-over.
To follow: playbook 07's line on a watcher's end (lines 618-619) could name the reports along the way; not in this change.
Note: this pull request was opened before its review, against how-work-is-done; the review followed at the same head.
Reviewed-by: mesh-code-reviewer@shanks (for fix-1965) at
c57930a759https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i
Delivery
novox/hq@c57930a75988— merged since 2026-11-09T08:49:47ZSource — source.main moved to novox/hq@3cf28e840d. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.