Move private monitoring behind watchdog extension

This commit is contained in:
Meta Vens 2026-04-29 18:50:19 +01:00
commit f17c46a750
7 changed files with 48 additions and 128 deletions

View file

@ -86,7 +86,7 @@ This note is the source-grounded description of how the live VoidBot stack is sh
- `scripts/start-voidbot-stack.ps1`
- stack bootstrap, health checks, fresh build, stale-process cleanup, bot/worker restart, runtime status emission.
- `scripts/check-voidbot-operations.ps1`
- watchdog for process liveness, Qdrant, Postgres, Ollama, Discord auth, backup freshness, offsite sync freshness, and configured Repixelizer fire signals.
- watchdog for process liveness, Qdrant, Postgres, Ollama, Discord auth, backup freshness, offsite sync freshness, and optional ignored local extension checks.
- `scripts/backup-voidbot-state.ps1`
- local backup of Postgres, Qdrant snapshots, and RAG archives.
- `scripts/restore-voidbot-state.ps1`
@ -96,10 +96,7 @@ This note is the source-grounded description of how the live VoidBot stack is sh
- `scripts/voidbot-operations-dashboard-lib.ps1`
- dashboard rendering for the local ops surface.
When configured, the watchdog now also federates a small amount of adjacent-service pain into the same ops lane:
- public `GET /api/health` against Repixelizer
- recent `repixelizer-gui` journald pressure on Yggdrasil over SSH
- owner DM escalation for queue saturation, failed jobs, stale cancellations, and slow-job clusters
When present, an ignored local script at `.voidbot/private/check-voidbot-operations.local.ps1` can inject adjacent-service checks into the same ops lane. That keeps private infrastructure gossip out of tracked code while preserving one boring place for smoke alarms to land.
## Storage Boundaries