fix home manager crons

home-manager/README.md

@@ -100,7 +100,9 @@ Docs: https://hermes-agent.nousresearch.com/docs/user-guide/docker
    places under `discord:`) with your numeric home channel ID. (Must match the
    secret's `DISCORD_HOME_CHANNEL`.)
 5. **Tailor `cron-seed.yaml`** schedules/prompts to your actual HA entities
-   (your sensor names, your `script.goodnight`, etc.).
+   (your sensor names, your calendars, your todo lists). The default schedule
+   has 4 jobs (energy anomaly, comfort check, morning briefing, evening
+   briefing) — adjust thresholds and wording to your setup.
 6. **Commit & push** the whole change (including the regenerated
    `argocd/apps/home-manager.yaml`). ArgoCD will create the namespace resources,
    deploy the pod, and bring up the ingress at `home-manager.rogi.casa`.
@@ -108,11 +110,13 @@ Docs: https://hermes-agent.nousresearch.com/docs/user-guide/docker
    automatically on every sync. The hook **reconciles** the cron schedule to
    match Git: it deletes + recreates each named job, so prompt/schedule edits
    in `cron-seed.yaml` take effect on the next sync (this overwrites any live
-   `hermes cron edit` changes — edit the prompts in Git instead). To re-run
-   it by hand: `kubectl apply -f home-manager/cron-seed.yaml`.
+   `hermes cron edit` changes — edit the prompts in Git instead). The schedule
+   has exactly 4 jobs: `energy-anomaly` (every 4h), `comfort-check` (every 4h),
+   `morning-briefing` (08:00 daily), `evening-briefing` (00:00 daily). To
+   re-run it by hand: `kubectl apply -f home-manager/cron-seed.yaml`.
 8. **Smoke test:** trigger a check manually —
-   `kubectl exec -n home-manager deploy/hermes -- hermes cron run door-window-check` —
-   and confirm the message lands in Discord (or `[SILENT]` if all clear).
+   `kubectl exec -n home-manager deploy/hermes -- hermes cron run morning-briefing` —
+   and confirm the message lands in Discord.
 
 ---