GameCult/VoidBot
Watch
9
0
Fork
You've already forked VoidBot
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Sync persistent state after Repixelizer monitoring

Browse source
This commit is contained in:
Meta Vens 2026-04-29 18:43:41 +01:00
commit aa4c54684e
4 changed files with 12 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

1
notes/fresh-workspace-handoff.md
View file

@ -26,6 +26,7 @@ Git history and smoke artifacts carry routine proof. `state/evidence.jsonl` shou
- Interaction-memory logic is no longer one thousand-line slab; event/tone analysis, shared constants, and profile synthesis are split across `packages/core/src/interaction-memory-*.ts`.
- State storage is no longer one persistence omnibus; `packages/core/src/state-storage.ts` is now a thin factory over domain-specific Postgres/file store modules plus bootstrap/migration helpers.
- Ops health, backup verification, offsite sync, and dashboard surfaces already exist.
- The operations watchdog now also carries Repixelizer fire signals: public `/api/health` checks plus recent `repixelizer-gui` journald pressure over SSH when configured, routed through the same owner DM alert path.
- The new state/notes surfaces are now the continuity spine for future nontrivial work.
## Likely Next Bounded Move

7
notes/voidbot-current-system-map.md
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, and offsite sync freshness.
- watchdog for process liveness, Qdrant, Postgres, Ollama, Discord auth, backup freshness, offsite sync freshness, and configured Repixelizer fire signals.
- `scripts/backup-voidbot-state.ps1`
- local backup of Postgres, Qdrant snapshots, and RAG archives.
- `scripts/restore-voidbot-state.ps1`
@ -96,6 +96,11 @@ 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
## Storage Boundaries
- Postgres:

1
notes/voidbot-implementation-plan.md
View file

@ -19,6 +19,7 @@ Use the persistent project-state surfaces to keep future work source-grounded an
- add a real restore-drill cadence instead of stopping at backup verification
- reduce dependence on interactive workstation logon where practical
- keep watchdog signals and dashboard diagnostics honest when dependencies are degraded
- keep adjacent-service checks deliberate so VoidBot does not quietly mutate into a generic infra panic funnel
### 3. Admin And Forensics Surfaces