{"repo":"NousResearch/hermes-agent","public_id":"99879","display_label":"Expose cron lateness and catch-up run timing in UI","summary":"These items address surfacing missed-fire catch-up lateness information in cron list and status views, ensuring that runs dispatched late after downtime are tagged with scheduled vs actual time and visible in the UI.","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":100445,"merged_at":"2026-09-01T15:31:38+00:00"},"resolution":{"state":"unresolved","by":null},"freshness":{"state":"verified","last_verified_at":"2026-09-01T15:31:38+00:00","is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[{"issue_number":99879,"pr_number":100445,"tier":"verified","basis":"superseded_ref","confidence":0.9,"recoverable_from_timeline":false,"pr_merged_at":"2026-09-01T15:31:38+00:00"}],"members":[{"kind":"issue","number":99879,"title":"Routines run late after gateway downtime with no missed-run status","url":null,"state":"closed"},{"kind":"pr","number":99919,"title":"fix(cron): tag catch-up dispatches with scheduled vs actual time and lateness so late runs surface in UI","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#100445","number":100445},{"kind":"pr","value":"#99879","number":99879}],"category":"superseded_by_pr","implication":"superseded"},"merged":false},{"kind":"pr","number":100445,"title":"fix(cron): surface missed-fire catch-up lateness in hermes cron list/status","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_dispatch_lateness_stamp.py","tests/hermes_cli/test_cron_dispatch_visibility.py"]}],"trust":{"default_tier":"verified","includes_suggested":false}}