Summary

Two tests have been failing on every CI run on origin/main since 5338250da (fix(gateway): add direct_messages_topic_id for synthetic Telegram DM events) landed yesterday. The production change extended gateway/run.py::_thread_metadata_for_source to emit a new direct_messages_topic_id entry for non-General Telegram DM topic lanes, but two test expectations weren't updated alongside it. This PR aligns those snapshots — no production code is touched.

The bug

5338250da added six lines to gateway/run.py::_thread_metadata_for_source:

metadata["telegram_dm_topic_reply_fallback"] = True
# Telegram DM topic lanes need direct_messages_topic_id in metadata
# so synthetic/queued messages (goal continuations, status notices)
# route to the correct topic even when reply anchor is unavailable.
tid = str(thread_id)
if tid and tid not in {"", "1"}:
    metadata["direct_messages_topic_id"] = tid

For any Telegram DM MessageEvent with thread_id="20197", the helper now also emits "direct_messages_topic_id": "20197". Two tests use exactly that fixture and assert the metadata dict with a strict ==:

• tests/gateway/test_telegram_thread_fallback.py::test_gateway_runner_busy_ack_replies_to_triggering_message_for_telegram_dm_topic
• tests/gateway/test_voice_command.py::TestSendVoiceReply::test_auto_voice_reply_uses_thread_metadata_helper

Both fail on every CI run with:

Full diff:
  {
+     'direct_messages_topic_id': '20197',
      'telegram_dm_topic_reply_fallback': True,
      'telegram_reply_to_message_id': '463',
      'thread_id': '20197',
  }

These are baseline failures on clean origin/main (f36c89cd5) and show up red on every open PR.

The fix

Add "direct_messages_topic_id": "20197" to the expected metadata dict in each of the two failing assertions. Nothing else changes.

The other 12 occurrences of telegram_dm_topic_reply_fallback in test_telegram_thread_fallback.py test the Telegram adapter directly (without going through _thread_metadata_for_source) and continue to pass — only the two GatewayRunner-helper sites that call the production helper needed updating. Confirmed by running the full files: 194 passed, 21 skipped after the change vs 192 passed, 2 failed, 21 skipped before.

Test plan

• Reproduced baseline failure on clean origin/main (f36c89cd5):

  FAILED tests/gateway/test_telegram_thread_fallback.py::test_gateway_runner_busy_ack_replies_to_triggering_message_for_telegram_dm_topic
  FAILED tests/gateway/test_voice_command.py::TestSendVoiceReply::test_auto_voice_reply_uses_thread_metadata_helper
  

• Focused regression: both files combined — 194 passed, 21 skipped in 14.07s (was 192 passed, 2 failed, 21 skipped).
• Regression guard: removing the new "direct_messages_topic_id": "20197" lines reproduces the original failure under the same harness; restoring them flips both tests back to PASSED.
• No production code touched — gateway/run.py is untouched, so no risk of behavioral drift.

Related

• Follow-up to 5338250da (fix(gateway): add direct_messages_topic_id for synthetic Telegram DM events) by @Timur00Kh