Add streaming output via editMessageText + /verbose tool display

[1872-svg]

Summary

• Live streaming responses: Claude's output streams to Telegram in real time using editMessageText. Sends a ⏳ placeholder on the first chunk, then progressively edits it as text arrives (throttled to 500ms). Final edit applies full HTML formatting.
• Race condition fix: waitForStreamMsg() ensures the placeholder sendMessage resolves before the handler decides to edit-vs-send, eliminating duplicate messages when Claude responds faster than the API round-trip.
• /verbose mode: Toggle per-chat display of tool calls. When on, the streaming message shows tool activity above the response text:

  ● Write(tcp_tls.py)
    ⎿  [Write] Wrote 117 lines
  ● Bash(python3 test.py)
    ⎿  [Bash] all tests passed
  
  Final response text here...
  

• /verbose is off by default — normal users see clean responses, power users can opt in.

Implementation details

runner.ts: switched main execution from --output-format json to --output-format stream-json --verbose. Added runClaudeStreaming() which parses NDJSON line-by-line, delivers text deltas via onChunk, and fires onToolEvent(line) for tool_use/tool_result events.

telegram.ts: makeStreamCallback() builds a closure that manages the streaming message lifecycle. In verbose mode it maintains separate toolLines and textAcc buffers and rebuilds the display on each flush.

Note: This PR depends on the fork-agent PR (#20) — it uses isMainBusy() and killActive() for auto-routing.

Test plan

• Send any message — response should stream live instead of appearing all at once
• /verbose → send a prompt that uses tools — tool calls should appear in the message as they happen
• /verbose again — should toggle off, responses go back to clean text
• Send a very fast one-word prompt — verify no duplicate messages