fix: reach Telegram from resumed asks

[TerrifiedBug]

Summary

• fall back to the paired Telegram owner when an explicit telegram_ask has no pre-resolved chat, even when a terminal picker is available
• preserve dual-surface first-answer behavior for resumed daemon and locally injected turns
• pin the exact Hermes regression: hydrated token and owner, interactive terminal, no active prompt target
• clarify paired-owner fallback in the user guide

Addresses #50. The issue stays open until the follow-up release passes the live fleet smoke.

Root cause

Paired-owner fallback was gated by !canTerminal. After the fleet session restarted, its custom turn had an interactive terminal but no pre-resolved Telegram target, so telegram_ask never attempted a Telegram post and correctly reported only posted:["terminal"].

Verification

• red before fix: bun test src/index.wiring.test.ts --test-name-pattern "resumed daemon UI ask"
• green after fix: same command
• bun install
• bun run check (275 tests pass)