The watchman confirms a module unhealthy by time, and keeps a standing finding across its restart (issue 1952) #127

Merged

mesh-tools merged 2 commits from fix/watchman-confirm into main 2026-10-31 21:34:06 +00:00

Conversation 1 Commits 2 Files Changed 2

+73 -13

2 Commits

Author	SHA1	Message	Date
jschoubben	8a658a4290	Watchman: an unhealthy finding read back at the start is kept as it was (issue 1952) ... At a restart a standing finding is observed again by the replayed failed have: kept, not confirmed again, and its urgent signal runs on from the finding's Since; an urgent one stays urgent with no signal restarted. Quick: skip the confirm when a finding stands. Thorough, chosen: the same, plus urgency read from the finding itself. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-10-31 22:01:59 +01:00
jschoubben	fb8d2386b9	Watchman: a module is unhealthy when its have still says failed a minute after it first did (issue 1952) ... A have that turned failed once and stayed unchanged was written once, so the old count of two writes never fired and the finding was never written (fail2ban on novox). Confirm by time, with a signal, also at a restart. Quick: raise the count to one write (loses the confirmation). Thorough, chosen: confirm by a time bound, as ADR 0564 s4's signals are keys that expire, so no write count is needed. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL	2026-10-31 21:59:46 +01:00