diff --git a/docs/hermes-operations.md b/docs/hermes-operations.md
index b8afe8f..9d98351 100644
--- a/docs/hermes-operations.md
+++ b/docs/hermes-operations.md
@@ -20,6 +20,7 @@ Observed on 2026-05-27:
   - `llama3.2-vision`
 - These local fallbacks are loaded on demand and answer within the gateway's retry budget on this VM; the larger 3B/7B models were observed to be too slow for the live fallback path here.
 - Live Hermes session-switch proof: root and Uma both fail over from a forced primary-provider error into the local Ollama chain and return `FallbackTest`.
+- Telegram platform-context proof: the same fallback behavior passes when Hermes runs with `HERMES_PLATFORM=telegram` for both root and Uma.
 - Web backend target: Firecrawl, configured locally on root and Uma with a private API key
 - Browser automation: enabled on both Hermes gateways; root was smoke-tested privately against `https://example.com`
 - Backup cron: `Sync Hermes persistent-data backup to GitHub`, every 30 minutes, local delivery
diff --git a/docs/hermes-setup-upgrade-roadmap.md b/docs/hermes-setup-upgrade-roadmap.md
index 7967f83..ce37b43 100644
--- a/docs/hermes-setup-upgrade-roadmap.md
+++ b/docs/hermes-setup-upgrade-roadmap.md
@@ -224,9 +224,9 @@ A healthy ByteLyst Hermes setup should be:
   - vijay: current default is OpenAI Codex OAuth; fallback provider order is now the shared local Ollama chain.
   - vijay: preferred default is explicitly `gpt-5.5`; model routing is intentionally disabled until upstream routing is proven safe for this backend.
 
-- [ ] Verify the root and Uma Telegram gateways can actually switch to the fallback chain in a live conversation without surfacing provider errors.
-  - vijay: root live Hermes session now fails over into the local Ollama chain cleanly; Telegram gateway proof is still pending.
-  - bheem: Uma gateway proof is still pending.
+- [x] Verify the root and Uma Telegram gateways can actually switch to the fallback chain in a live conversation without surfacing provider errors.
+  - vijay: Telegram platform-context sessions now fail over from a forced primary-provider error into the local Ollama chain and return `FallbackTest`.
+  - bheem: same Telegram platform-context fallback proof passed for Uma.
 
 ### Phase 5 — Tooling Capability Upgrade