[boly38]

Closes #18

Summary

• Acknowledge authorized Telegram requests immediately, then edit the acknowledgement with progress,
  the final response, or a safe error reference.
• Submit OpenCode prompts asynchronously and correlate responses and progress events with the request.
• Distinguish OpenCode timeouts from other failures and log the client, phase, duration, timeout, and
  safe error details without logging prompts, credentials, session IDs, or raw response bodies.
• Set the OpenCode request deadline to 300 seconds; keep Telegram HTTP at 70 seconds and long polling
  at 50 seconds.
• Use OpenCode-compatible message IDs and expose only generic progress states, not raw reasoning.

Validation

• make test — 45 tests passed
• python3 -m py_compile bot/telegram/bridge.py bot/telegram/http_api.py bot/telegram/opencode_api.py bot/telegram/bridge_config.py
• make config
• git diff --check
• A manual Telegram ping was tested locally; the user reported that acknowledgement and response
  handling worked better after the message ID fix.