Summary

• narrow Telegram control-lane sequentialization to abort-style commands only
• keep non-abort slash commands (/status, /model, /queue, etc.) on the normal chat/topic lane
• update sequential key test expectation for /status

Root cause

getTelegramSequentialKey routed all control commands to telegram:<chat>:control, which let non-abort slash commands execute concurrently with in-flight normal message handling. That race could preempt/lose queued follow-up processing from the first run.

Validation

• pnpm test src/telegram/bot.create-telegram-bot.test.ts
• pnpm test src/telegram/bot.test.ts

Greptile Summary

Narrowed Telegram control-lane sequentialization to abort-style commands only (stop, abort, exit, wait, interrupt, esc), while non-abort slash commands like /status, /model, /queue now execute on the normal chat/topic lane. This prevents non-abort commands from executing concurrently with in-flight message handling, which could cause race conditions and preempt queued follow-up processing.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is well-focused and addresses a specific race condition. The implementation correctly identifies abort commands using the existing isAbortTrigger function and properly normalizes command bodies. Tests are updated to match the new behavior. The logic is straightforward and the changes are minimal.
• No files require special attention

_{Last reviewed commit: e629902}