fix: preserve cron telegram topic delivery after timeout#72317
Conversation
Greptile SummaryThis PR adds abort-signal forwarding to CLI-backed cron agent runs and regression coverage for Telegram supergroup topic delivery. The one-line production change ( Confidence Score: 5/5Safe to merge — one-line targeted fix with two well-structured regression tests. The production change is a single, clearly correct line (mirroring the already-present abortSignal in the embedded-agent path). Both new tests directly exercise the fixed path; the abort-signal test uses an in-process mock that resolves only after abort fires, confirming both signal forwarding and late-result suppression. No unrelated code is touched. No files require special attention. Reviews (1): Last reviewed commit: "fix: abort cli cron runs on timeout" | Re-trigger Greptile |
What
Adds regression coverage for explicit Telegram forum topic cron announce delivery and forwards cron timeout abort signals into CLI-backed isolated cron agent runs so late CLI completions are discarded before announce dispatch.
Why
A cron configured to announce to
telegram:-1003774691294:topic:47must preservemessageThreadId: 47. A timed-out isolated cron run could continue producing a late final answer after the job was marked timed out, risking fallback to the active/default Telegram topic.Changes
Testing
pnpm test src/cron/isolated-agent.direct-delivery-core-channels.test.tspnpm test src/cron/isolated-agent/run.skill-filter.test.tspnpm check:changed