fix: abort button works while prompt is running + CODEX_PATH_OVERRIDE support

[roy3003]

Problem

Two bugs found while running TeleCodex in production:

1. Abort button does nothing during a long prompt

Root cause: grammY processes Telegram updates sequentially (one at a time). While a prompt handler is running (which can take minutes), the Abort button's callback query sits in the queue and expires after 30 seconds before it ever gets processed. The log showed:

Telegram bot error: Call to 'answerCallbackQuery' failed! (400: Bad Request: query is too old and response timeout expired or query ID is invalid)

A secondary issue: the handler called await ctx.answerCallbackQuery() before session.abort(), so if the query was already expired, the await would throw and abort would never execute.

2. CODEX_PATH_OVERRIDE env var was wired up in config but never passed to the Codex SDK constructor

The env var was read and stored on TeleCodexConfig but resetCodexClient() didn't pass codexPathOverride to new Codex({...}), so the override had no effect.

Fix

Abort fix (bot.ts):

• All prompt call sites (text / retry / voice / photo / document) now use a startPromptTask() fire-and-forget wrapper. The handler returns immediately, freeing the grammY update queue so Abort callbacks are processed concurrently with the running prompt.
• codex_abort callback handler now calls session.abort() first, then answers the callback query with .catch(() => {}) so an already-expired query ID never blocks the abort.

CODEX_PATH_OVERRIDE fix (codex-session.ts):

• Pass codexPathOverride to the Codex constructor in resetCodexClient().

Test plan

• Send a long-running prompt, press ⏹ Abort — response stops immediately
• Set CODEX_PATH_OVERRIDE=/usr/local/bin/codex — SDK uses the specified binary

🤖 Generated with Claude Code