gavrielc 8eb80d4ed0 fix: prevent infinite message replay on container timeout (#164) ...

Container timeout and idle timeout both fire at 30min, racing the
graceful shutdown. The hard kill returns error status, rolling back
the message cursor even though output was already sent — causing
duplicate messages indefinitely.

- Grace period: hard timeout is now IDLE_TIMEOUT + 30s minimum
- Timeout after output resolves as success (idle cleanup, not failure)
- Don't roll back cursor if output was already sent to user
- Remove src/telegram.ts and config vars (added to PR #156 by mistake)
- Add typecheck step to CI workflow
- Add container-runner timeout behavior tests

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-11 17:25:42 +02:00

..

skills-only.yml

Add contribution guidelines and PR checks for skills-only model

2026-02-02 13:50:25 +02:00

test.yml

fix: prevent infinite message replay on container timeout (#164)

2026-02-11 17:25:42 +02:00