Give the watchdog counters a voice in the repair sweep

A fourth candidate source beside the arrs, the system log and container logs: skip-listed containers, strikes past their limit, repeated restarts, unattended reboots and sustained pressure become findings. The kind is deliberately not conf-bound, so it cannot autofix by construction rather than by a switch — and WATCHDOG_SCAN_IGNORE suppresses it, so a knowingly broken container stays quiet. First consumer AI_ASSIST_WATCHDOG has ever had.
2026-08-14 12:01:18 -04:00
parent cbcfbfaaad
commit 2f8b7276a4
2 changed files with 164 additions and 2 deletions
@@ -1821,7 +1821,7 @@
 # Tier 1 is narration — it cannot change a decision. Tier 2 adds context to a decision a script
 # already made. Tier 3 assists a human. Enable in that order, and give each one weeks.
    AI_ASSIST_REPORTS=false         # tier 1 — digest / coffee report narration
-    AI_ASSIST_WATCHDOG=false        # tier 2 — context on a flagged condition
+    AI_ASSIST_WATCHDOG=false        # tier 2 — file a finding when a watchdog counter passes its limit (needs AI_REPAIR_ENABLED)
    AI_ASSIST_DISCOVERY=false       # tier 2 — discovery / classification judgement calls
    AI_ASSIST_CLEANUP=false         # tier 2 — orphan and stuck-import triage
    AI_ASSIST_ONBOARD=false         # tier 3 — onboarding / settings assistance