Replaces the inline `claude.lock` blocking pattern with a real persistent queue. Each TG message enqueues a job and gets the typing indicator immediately; a dedicated worker thread drains the FIFO one at a time, replying as each claude run finishes. ## What's new - **Queue with persistence** — \`/etc/bux/tg-queue.json\`, atomic-rename writes, mode 600. Bot startup drops any \`status='in_flight'\` rows (previous crash, can't safely re-run). - **\`/queue\`** — lists pending + in-flight tasks with one-line previews. - **\`/cancel\`** — drops everything queued. In-flight task continues (we can't safely SIGTERM claude mid-run). - **\`/cancel \`** — drops one row by its 8-hex id. The id is shown in the queued ack reply. - **No duplicate "on it…" reply** — when the queue is empty, TG's typing indicator already conveys "I see you, working". Visible ack only fires when there's actual queueing happening (\`#2+ in queue\`). ## Bringing the public repo to parity This PR also includes a few related fixes that have been running on private boxes for a while: - MarkdownV2 reply rendering for claude's output (bold/code/links). 400 → plain-text fallback. - \`/cancel\` matched as a token, not a prefix (so \`/cancelled\` etc. aren't swallowed). - Type-narrowing on the worker: skip malformed queue rows instead of crashing. ## Diff size note The line count is large because \`ruff format\` reformatted the whole file (the public repo wasn't on the same formatter config). The actual queue logic is ~240 lines; the rest is whitespace / import grouping. Skim the new \`_queue_*\` helpers and the rewritten \`handle()\` / \`queue_worker()\` for the substance. ## Test plan - [ ] Send 3 TG messages back-to-back → first runs immediately (typing indicator only), next two get \`queued (#N) — id \`. - [ ] \`/queue\` lists all 3 with the running one marked ▶. - [ ] \`/cancel \` of a queued task removes it; \`/cancel \` of the in-flight one says it can't be cancelled. - [ ] Bare \`/cancel\` drops everything queued. - [ ] Restart \`bux-tg.service\` mid-claude → in-flight row dropped on restart, queued rows resumed. - [ ] Send a literal \`/cancelled my plans\` → goes to claude, NOT swallowed by /cancel handler. --- ## Summary by cubic Replaces the inline `claude.lock` blocking pattern with a persistent FIFO queue so Telegram messages get an immediate typing indicator and are processed one at a time by a worker. Adds `/queue` and `/cancel` commands for visibility and control. - **New Features** - Persistent on-disk queue at `/etc/bux/tg-queue.json` (mode 600, atomic writes); on startup, drops any `in_flight` rows from a previous crash. - Dedicated worker thread drains the FIFO; each job replies when its Claude run finishes. - `/queue` shows pending and running items with one-line previews; `/cancel` clears pending items; `/cancel ` removes a single pending job (running jobs are not aborted). - Smarter acks: rely on typing when no queue; send “queued (#N) — id ” only when there’s actual queueing. - **Bug Fixes** - MarkdownV2 rendering for Claude output with plain-text fallback on Telegram 400. - `/cancel` matched as a token (no accidental matches like `/cancelled`). - Worker skips malformed queue rows instead of crashing. ^{Written for commit 963745c21018ce6a0e70c6e1fc267b3e7213c032. Summary will update on new commits. Review in cubic}