{"repo":"NousResearch/hermes-agent","public_id":"53720","display_label":"Raise cron tick-skip log level to INFO","summary":"These items all concern changing the log level for cron tick lock-skip messages from DEBUG to INFO so the events are visible in dual-scheduler setups. The group is coherent and focused on a single logging visibility concern.","subsystem":"cron","counts":{"members":4,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":1,"attempt_prs":2},"landed_fix":{"status":"merged_to_main","basis":"structural","pr":131894,"merged_at":"2026-10-03T02:52:44+00:00"},"resolution":{"state":"resolved","by":"pr-131894"},"freshness":{"state":"verified","last_verified_at":"2026-10-03T02:52:44+00:00","is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[{"issue_number":53720,"pr_number":131894,"tier":"verified","basis":"closing_ref","confidence":0.95,"recoverable_from_timeline":true,"pr_merged_at":"2026-10-03T02:52:44+00:00"}],"members":[{"kind":"issue","number":53720,"title":"Cron tick log line is DEBUG-level; should be INFO for visibility in dual-scheduler setups","url":null,"state":"closed"},{"kind":"pr","number":53724,"title":"fix(cron): change tick-skip log level from DEBUG to INFO","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#131894","number":131894}],"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":53803,"title":"fix(cron): log tick lock-skip at INFO for dual-scheduler visibility","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#53724","number":53724}],"category":"duplicate_of","implication":"duplicate"},"merged":false},{"kind":"pr","number":131894,"title":"fix(cron): log tick lock contention at INFO [risk 0.30]","url":null,"state":"merged","close_reason":{"category":"merged"},"merged":true,"is_fix_pr":true,"fix_tier":"verified","files_changed":["cron/scheduler.py"]}],"trust":{"default_tier":"verified","includes_suggested":false}}