hermes - 💡(How to fix) Fix Support base runtime overrides for Telegram DM topics [1 pull requests]

Problem

Telegram private-chat topics can already act as separate Hermes session lanes, but operators cannot predeclare the base runtime for each lane. Every topic starts from the gateway-wide provider/model/toolset defaults unless the user manually applies a session-level /model override.

That makes topic-based workflows awkward when different DM topics are intended for different kinds of work, for example:

• a research topic using a larger model and web/browser/file tools
• a quick/general topic using a smaller local model
• a project topic with a narrower toolset

Proposed behavior

Allow platforms.telegram.extra.dm_topics[].topics[] entries to carry optional runtime defaults:

platforms:
  telegram:
    extra:
      dm_topics:
        - chat_id: 123456789
          topics:
            - name: "Research"
              thread_id: 2503
              provider: "openrouter"
              model: "anthropic/claude-opus-4.6"
              toolsets: [web, file, session_search]

When a message arrives in a configured topic, Hermes should use that topic's provider/model/toolsets as the base runtime for the turn. Explicit session /model overrides should continue to take precedence.

Scope

This is intentionally narrower than full topic-to-profile routing:

• no separate profile process
• no memory/personality isolation
• no new Telegram topic lifecycle behavior
• no change to group forum topic routing

Related

• #18327 was closed after splitting out the seed-message fix; per-topic model overrides were left as future work.
• #4321 and #10143 discuss broader topic-to-profile routing.