hermes - 💡(How to fix) Fix Habit reminder workflows can silently decay without escalation

Bug Description

Habit reminder / review workflows are brittle enough to silently decay, which breaks trust for users relying on Hermes for accountability.

In this user setup, the system gave the impression that habits were being tracked and resurfaced, but the actual state drifted:

• the nightly habit check-in cron exists and reports last_status: ok
• the weekly habit review cron existed as a one-shot job and is now completed / disabled
• the source note became stale and contaminated with unrelated text without any protective surfacing
• the user experienced this as: "why are you not reminding me?"

Concrete Evidence

Current local state:

• nightly-habit-checkin (ead4013dbb13) is scheduled daily and still enabled
• weekly-habit-review (f347d8f5caf3) was created as once at 2026-05-03 18:00 and is now completed/disabled rather than recurring
• habit source note: /Users/jaydevram/Documents/Dillan 2026/openclaw/review/habits.md

The habit note currently contains unrelated junk near the top:

• use lenny oproduct pass similar for ligbtwork what can we offer for free, free air ourifiers sell them on purifiers.
• what can we offer get peopel into oter offers

It also appears stale:

• latest dated section in the note is ### 2026-05-03

Why This Matters

For accountability-oriented users, a reminder system that silently stops recurring or stops surfacing note corruption is worse than no system at all.

The failure mode here is not just "one cron misconfigured". It is that Hermes lacks guardrails for recurring habit workflows:

1. one-shot review jobs can be mistaken for durable habit infrastructure
2. stale source notes are not flagged early enough
3. unrelated contamination in the habit note is not surfaced as a reliability problem
4. user-facing reminder reliability is hard to audit from cron state alone

Expected Behavior

If Hermes is helping manage habits, it should make this class of failure obvious and harder to create.

Possible expected behaviors:

• recurring habit-review workflows should default to recurring schedules, not one-shot jobs, unless explicitly requested
• when a habit note goes stale past a threshold, Hermes should flag it proactively
• when a habit source note contains obviously unrelated non-habit lines near the top, Hermes should flag note contamination
• cron inspection should make it easier to distinguish "job ran" from "habit system is healthy"

Actual Behavior

• cron state can look healthy enough to imply reminders are working
• a key supporting review job can silently expire because it was one-shot
• the source note can drift into a degraded state without proactive escalation
• the user only discovers the issue after reminders are perceived as missing

Environment

• OS: macOS
• Hermes profile: default local profile
• Affected areas: cron, recurring reminder workflows, note-health surfacing

Suggested Fix Directions

1. Add a cron lint / warning for one-shot jobs whose names imply recurring behavior (daily, nightly, weekly, habit, review, etc.).
2. Add an optional recurring-workflow health check that can detect:
   • stale source note dates
   • expired companion cron jobs
   • malformed / contaminated habit notes
3. Add a standard pattern for "accountability workflows" so habit systems are less ad hoc.
4. Consider better visibility in cron inspection for jobs that have completed and are no longer protecting an expected recurring workflow.