{"repo":"NousResearch/hermes-agent","public_id":"118354","display_label":"Cron no-agent script failure visibility bug fix","summary":"A bug where a no-agent cron script failure is silently overwritten by the next successful run, causing the failure to disappear from history. The fix preserves a sticky last-failure stamp so past failures remain visible even after subsequent successes.","subsystem":null,"counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":1,"attempt_prs":1},"landed_fix":{"status":"merged_to_main","basis":"structural","pr":127596,"merged_at":"2026-10-03T01:29:56+00:00"},"resolution":{"state":"resolved","by":"pr-127596"},"freshness":{"state":"verified","last_verified_at":"2026-10-03T01:29:56+00:00","is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[{"issue_number":118354,"pr_number":127596,"tier":"verified","basis":"closing_ref","confidence":0.95,"recoverable_from_timeline":true,"pr_merged_at":"2026-10-03T01:29:56+00:00"}],"members":[{"kind":"issue","number":118354,"title":"[Bug]: no_agent cron script failure is erased by the next successful run - last_status and failure_streak self-heal, so a relapse is invisible","url":null,"state":"closed"},{"kind":"pr","number":118387,"title":"fix(cron): preserve no-agent script failure history","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#118354","number":118354},{"kind":"pr","value":"#127596","number":127596}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":127596,"title":"fix(cron): keep a sticky last_failure stamp so a healed no_agent script failure stays visible","url":null,"state":"merged","close_reason":{"category":"merged"},"merged":true,"is_fix_pr":true,"fix_tier":"verified","files_changed":["cron/jobs.py","hermes_cli/cron.py","tests/cron/test_last_failure_stamp.py"]}],"trust":{"default_tier":"verified","includes_suggested":false}}