feat(tui): detect interrupted JSONL sessions

[undivisible]

Summary

• Land session_interrupted() on current main so crash/kill JSONL tails can be classified without waiting on PRs feat(tui): cache MCP tool schemas for instant advertisement #2–perf(tui): paint first, connect providers in background #5 (all CONFLICTING).
• Fix two gaps from PR feat(tui): detect interrupted sessions and offer resume #3: truncated tails use file mtime (not the last parsed timestamp) so a 24h resume window still fires, and a durable session_info interrupted marker survives persist() rewrite.
• Esc-cancel is distinguished via a cancelled marker so it does not look like a crash.

Test plan

• cargo fmt --check (ui/tui)
• cargo clippy --locked --all-features -- -D warnings
• cargo test --locked — 140 passed, including:
  • truncated tail uses mtime, not 48h-old parsed stamp
  • mid-file garbage then clean assistant is not interrupted
  • interrupted marker survives a clean-looking rewrite
  • cancelled marker is not interrupted
  • trailing user prompt / tool call / tool result

Reviews left on open PRs (not merged — dirty vs main):

• feat(tui): cache MCP tool schemas for instant advertisement #2 MCP cache: mixed-cache registry swap, OnceCell seed race, non-atomic write
• feat(tui): detect interrupted sessions and offer resume #3 resume: this classifier + the persist/mtime gaps above
• feat(tui): auto-poke continuation for unfinished turns #4 auto-poke: last_assistant_text not cleared on ToolCall; no maybe_auto_poke test
• perf(tui): paint first, connect providers in background #5 fast startup: set_provider vs spawn_prompts race; record-before-queue duplicates

Made with Cursor

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_8ed772dd-ff66-4324-9b69-3b4b63974b15)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_c2b6391b-d64e-407b-89b9-f25af0cfbb9e)