Cron lifecycle guard scoping and matching fixes

NousResearch/hermes-agent · cluster 124700 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address two over-matching bugs in the cron lifecycle guard: one where it incorrectly matched unrelated service labels instead of only its own, and one where a parse-only bash invocation triggered unintended script scanning.

Open issues1

  • Issue#124700[Bug]: lifecycle guard over-matches — blocks unrelated LaunchAgent maintenance and non-executing commands, with no sanctioned path to install an independent service

Open PRs2

  • PR#124716fix(cron): a parse-only `bash -n` invocation no longer scans the script it names
  • PR#124753fix(cron): lifecycle guard matches the gateway's own service label, not any prefix-containing label
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.