Automated hermes-sweeper review: this appears to be implemented on current main.

Evidence:

• gateway/run.py:8635 propagates a compression-rotated agent_result["session_id"] into session_entry.session_id, persists session_store._save(), and syncs the topic binding when applicable.
• gateway/run.py:7927 walks stale Telegram topic bindings through SessionDB.get_compression_tip() before transcript load; gateway/run.py:7956 rewrites the binding to the descendant.
• gateway/run.py:8110 loads the next turn's transcript from the updated session_entry.session_id, so the next inbound turn reads the compact child transcript instead of the oversized parent.
• gateway/run.py:14607 detects mid-run compression splits and gateway/run.py:14717 returns the effective session id to the outer gateway path.
• tests/gateway/test_telegram_topic_mode.py:452 covers the stale parent-binding case and asserts the route/binding advance to the compression child.
• tests/gateway/test_compression_session_id_persistence.py:1 documents the infinite preflight compression loop class and pins the route persistence invariant.
• Commit db96fc60d0d3dc3f9e95dc6541d8edcccb2f2171 shipped the Telegram topic compression-child alignment/read-path self-heal and is contained in v2026.6.5.

Thanks for the detailed fix and for the local proof in the PR body. This is an automated hermes-sweeper review.