v0.8.5

v0.8.5 — Phase 11G-C: Telegram Rejection Diagnosis

Added

• When Telegram rejects a send (non-2xx), the sender now reads the API response body's description (e.g. Forbidden: bot was blocked by the user) and includes it in the controlled error stored on the delivery: Telegram API returned HTTP 403: Forbidden: ...
• Sanitization: description truncated to 200 chars; bot-token-shaped substrings → [token]; URL-shaped → [url]; non-JSON/missing body → status-only message (unchanged behavior). Errors never contain the token, API base, or sensitive values

Quality

• 785 tests (53 files) — 5 new (description inclusion, token/URL redaction, non-JSON fallback, long-description truncation); tsc 0, lint 0, prettier PASS, build PASS (BUILD_ID vaw7Vhxu43aSQAc2U_hOY)

Notes

• Added to diagnose a production Telegram 403 (controlled test sends reached the API and were rejected with HTTP 403, but the previous sender only recorded the status code). The precise Telegram-side reason is captured on the next real test send.
• No schema/migration change; no behavior change for successful sends