Files
hermes-agent/hermes_cli
kshitijk4poor 8e457dfad2 feat(cron): show an unwritable store at the top of cron status and in cron list
Since the tick stopped raising on a failed store write, ticker_last_error is not written during
an outage, so `hermes cron status` stayed green while every job was skipped. The CLI cannot read
the ticker's in-memory state or trust markers in a directory nobody can write, so it probes the
store itself (cron.store_health.probe_report). On failure it leads with a red
"⚠ Cron store is NOT writable — scheduled jobs are being skipped" headline. The detail names
the path, the OS error, the last successful write, how many due runs have not fired, and the
fix. `cron list` prints a one-line banner. The probe runs before any job read, because loading
jobs re-secures the directory mode.
2026-10-07 10:20:18 +05:30
..
…
…
…
…
…
…