From a6f811fce039f9057cd3d8e74d1369a0c09ec5aa Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 21:32:59 +0100 Subject: [PATCH] mesh-watcher: read the working program's journal each round; a stuck read is a finding; never guess the time A watcher reported no change for ten minutes while the sdk's build had failed at its start (2026-11-19 21:19): it read only states that do not show a failed build, and read around a verb that timed out on every call. Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- .claude/agents/mesh-watcher.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.claude/agents/mesh-watcher.md b/.claude/agents/mesh-watcher.md index 8ca4f5eb..20333b8e 100644 --- a/.claude/agents/mesh-watcher.md +++ b/.claude/agents/mesh-watcher.md @@ -23,6 +23,12 @@ without that read on each machine the module is wanted on. Loop: wait with `mesh_wait` on the event family (its answer only wakes you), then read the state from the verb the handover names; never report a state you did not read in that round. +**A state that does not change is not "nothing happened".** A reservation, a queue or a key can stay as it was while +the work behind it already failed. Each round, also read the journal of the program that does the work +(`/node-service-manager.journal` with its unit, the last lines since your previous read) and report any failure +line word for word. A verb that times out or refuses twice is a finding of its own: report it at once, never read +around it. You have no clock: take times from the tools' answers, never guess them. + **A report along the way does not end you.** Your final message ends you, and then nothing watches. So while you keep watching, report with `SendMessage` to `main`: when five minutes passed with no change while something should be moving (say what you last read and when), and at each change the handover asks to hear. Then go on