pm2-self-heal: contract says every 5 min, cron was every 30 min (6am-10pm only)
→ Fixed to */5 * * * * (24×7)
infra-monitor+control: was daytime-only (6am-10pm)
→ Fixed to 24×7
Stale references
infrastructure-update pre-flight still checked VM 101/103 (now bare metal)
→ Replaced with GPU bare-metal health check
Missing persistence
gpu-monitor-server not in PM2 — would die on reboot
→ Added to PM2 + @reboot pm2 resurrect cron
Cleanup
Removed commented-out zulip-monitor.sh cron
README: zulip-monitor.sh → agent-health-check.py
pm2-self-heal: added gpu-monitor to tracked processes
## Found by cron audit
### Misaligned schedules
- pm2-self-heal: contract says every 5 min, cron was every 30 min (6am-10pm only)
→ Fixed to */5 * * * * (24×7)
- infra-monitor+control: was daytime-only (6am-10pm)
→ Fixed to 24×7
### Stale references
- infrastructure-update pre-flight still checked VM 101/103 (now bare metal)
→ Replaced with GPU bare-metal health check
### Missing persistence
- gpu-monitor-server not in PM2 — would die on reboot
→ Added to PM2 + @reboot pm2 resurrect cron
### Cleanup
- Removed commented-out zulip-monitor.sh cron
- README: zulip-monitor.sh → agent-health-check.py
- pm2-self-heal: added gpu-monitor to tracked processes
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found by cron audit
Misaligned schedules
→ Fixed to */5 * * * * (24×7)
→ Fixed to 24×7
Stale references
→ Replaced with GPU bare-metal health check
Missing persistence
→ Added to PM2 + @reboot pm2 resurrect cron
Cleanup