STANDING: Monitor daemon passenger registry when daemon is live

[koad]

Standing Healing Maintenance

Healer: Salus

Once daemon is deployed and running, Salus should monitor the passenger registry to ensure it stays in sync with actual entities on disk. This is a forward-looking standing task.

When Daemon is Live:
Salus will be able to query MongoDB Passengers collection to see what the daemon knows about each entity. Daily heal should:

1. Query daemon's passenger registry

2. Compare against entities on disk (has .env and passenger.json)

3. Flag mismatches:

   • Entity on disk but not in registry → daemon missed it; log issue
   • Entity in registry but not on disk → stale entry; daemon should have cleaned it up
   • passenger.json role doesn't match registry role → daemon may not have reloaded

4. Check avatar embedding (optional):

   • If avatar is still a file path (not data URI), flag as "warn" — daemon should embed it
   • If avatar file doesn't exist, flag as "error"

Reference:

• VESTA-SPEC-009-DAEMON, Section 2.4 "Daemon Processing of passenger.json"

Status: This task requires daemon to be deployed and MongoDB accessible. Currently dormant; activate after daemon deployment.

Standing Work:
Add to daily heal after daemon is live. Monitor registry health. Flag sync failures or avatar issues.