Files
hermes-agent/gateway
liuhao1024 3e8fe26a2e fix(gateway): enter the secondary profile scope per callback, not from a configure-time snapshot
Review feedback (#120650): the prebuilt secret scope froze the profile's
`.env` at configure time, so an operator's runtime TELEGRAM_ALLOWED_USERS
edit reached the next text message (per-message scope re-read) but not the
next button tap, and it skipped hydrate_profile_secret_sources. Enter the
owning profile's runtime scope per call via _scope_or_null — the exact
pattern every sibling secondary handler already uses — so taps and messages
share one freshness and hydration story, and an unresolvable profile home
still binds nothing (fail-closed).
2026-09-26 06:41:34 +05:30
..