{"repo":"NousResearch/hermes-agent","public_id":"60014","display_label":"Cron job file paths fixed at import defeat test isolation","summary":"The members describe cron path constants (such as JOBS_FILE and CRON_DIR) being computed at import time, which reportedly bypasses HERMES_HOME test overrides and lets test fixtures touch a user's real jobs file. One member is a pull request proposing lazy path resolution; the others are issue reports of the same behavior.","subsystem":"cron","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":0,"closed_issues":1,"merged_prs":0,"attempt_prs":1},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_PARTIAL","link_density":0.4533333333333333},"fix_edges":[],"members":[{"kind":"issue","number":60014,"title":"cron.jobs module-level JOBS_FILE caching defeats HERMES_HOME test isolation — real jobs leak into production (see also #52611, #50681)","url":null,"state":"open"},{"kind":"issue","number":61673,"title":"tests: cron fixtures write into the user's live `~/.hermes/cron/jobs.json` — import-time `CRON_DIR` bake defeats the conftest `HERMES_HOME` monkeypatch","url":null,"state":"closed"},{"kind":"pr","number":60824,"title":"fix(cron): resolve job paths lazily","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#60393","number":60393},{"kind":"pr","value":"#60014","number":60014},{"kind":"pr","value":"#61813","number":61813}],"category":"uncategorized","implication":"needs_llm"},"merged":false,"is_fix_pr":true,"fix_tier":"suggested","fix_detail_withheld":true}],"trust":{"default_tier":"verified","includes_suggested":false}}