autoreg-skills-max: initial public release (restored, redacted, hardened)

skills/lobehub-pool/references/watchdog-cron-missing-2026-07-03.md

@@ -0,0 +1,36 @@
+# Watchdog Cron Missing — 2026-07-03
+
+## What happened
+
+Cron job `1b08ee756117` (lobehub-proxy-watchdog) was completely absent from the
+`hermes cron list` output. Not paused — missing entirely. The proxy on port 20140
+had crashed and stayed dead because nothing was restarting it.
+
+## Diagnosis
+
+```bash
+hermes cron list | grep -i '1b08ee\|lobehub.*watchdog'
+# → NO output. Cron is missing.
+```
+
+The cline-pass-healthcheck cron (`df4018142560`) was present and active, proving
+the cron system itself was working — only the lobehub watchdog was gone.
+
+## Fix applied
+
+1. Manually restarted proxy: `cd /c/Users/User && python -u lobehub_final.py`
+2. Verified proxy health: `curl -s http://localhost:20140/health` → HTTP 200, 18 models
+3. **Watchdog NOT recreated** — this cron job only ran the check, didn't have the
+   right tool access to recreate it. The watchdog remains missing. Next session
+   with full tool access must recreate it.
+
+## Proxy health at restart
+
+```json
+{"status":"ok","accounts":{"total":601,"configured":0},"models":18,"backend":"lobehub","stats":{"total_requests":0,"errors":0,"started":"2026-07-03T07:54:38.342054"}}
+```
+
+## Key takeaway
+
+**Always check BOTH:** is the proxy running AND does the watchdog cron exist?
+A running proxy without a watchdog is a time bomb — it will crash and stay dead.