hermes-agent/cron
kshitij d13e8f7510 fix: Discord-specific guard + cron sibling + non-regression tests
- Guard the thread-id-as-chat_id normalization to Discord only; Slack
  and Telegram adapters use parent_channel as chat_id for thread messages,
  so the unconditional version broke their handoff keys.
- Apply the same Discord-specific guard to _seed_cron_thread_session in
  cron/scheduler.py (sibling site with the same bug, docstring said
  'Mirrors _process_handoff').
- Replace the change-detector test with contract tests that verify the
  actual invariant: Discord handoff key == organic thread key, Slack
  handoff key still uses parent channel (non-regression).
2026-08-03 00:32:17 +05:30
..
scripts
__init__.py
blueprint_catalog.py
executions.py fix(state): make journal mode canonical and behaviorally verified 2026-07-29 18:13:09 -07:00
jobs.py refactor(cron): drop dead advance_next_run import; wrapper tolerates duplicate ids 2026-08-02 21:15:16 +05:30
lifecycle_guard.py fix(gateway): add submit/bootstrap to lifecycle guard Branch B and label-independent detection 2026-08-01 10:52:08 -07:00
scheduler.py fix: Discord-specific guard + cron sibling + non-regression tests 2026-08-03 00:32:17 +05:30
scheduler_provider.py fix(cron): preserve jobs.json ownership on root rewrite + surface failing-tick reason 2026-07-24 15:52:13 -07:00
suggestion_catalog.py
suggestions.py