feat: add telegram thread routing and delivery test

[juanjoGonDev]

Additional finding (out of scope)

• During manual validation, I observed that deleting a secret from the Secrets section does not immediately invalidate already-exported env vars in the running process.
• Because of that, ${...}-based tokens may still work for bot runtime and test action until process restart.
• This appears to be a separate concern related to secret lifecycle/runtime env management, not to the Telegram thread-routing changes in this PR.
• Suggestion: track and address in a dedicated follow-up issue/PR.

What

• Test action now surfaces Telegram API error details in UI toasts (preview + remaining count).
• Improved allowed chats validation UX with explicit row-level error messages in the save flow.
• Reworked Telegram client access rules to support structured allowedChats entries (chatId + optional threadId).
• Added full thread-aware Telegram response routing so replies stay in the originating topic/thread.
• Added Telegram delivery test action in Admin API and Admin UI (Test button in client dialog).
• Updated test action behavior to use current form values (without requiring Save), including empty-token behavior.
• Added ${ENV_VAR} expansion support in Telegram test action to match runtime secret/env resolution semantics.
• Added deduplication for repeated allowedChats rules on save.
• Added validation to reject invalid chat rules (chatId=0, non-positive threadId or invalid threadId format) with user-facing error handling.

Why

• Supergroup topics need deterministic thread routing; otherwise responses can leak to the main group feed.
• Admin users need to validate destination configuration quickly from the form while iterating.
• Secret-backed token usage (${...}) should behave the same in test action and runtime behavior.
• Legacy configs from master must continue working safely.

Scope

• Backend:
  • server/store/types.go
  • server/store/types_test.go
  • server/clients/telegram/spec.go
  • server/clients/telegram/bot.go
  • server/clients/telegram/bot_test.go
  • server/api/admin/clients.go
  • server/api/admin/clients_telegram_test.go
  • server/api/admin/handler.go
• Frontend:
  • frontend/admin-ui/src/lib/api/clients.js
  • frontend/admin-ui/src/views/clients/ClientDialog.vue
  • frontend/admin-ui/src/views/clients/allowedChatsRules.js
  • frontend/admin-ui/src/views/clients/allowedChatsRules.test.js

Behavior changes

• Telegram test toasts now include backend errors[] details (e.g. bot kicked, chat not found, invalid thread).
• Save validation now reports explicit row-level messages for invalid allowed chat rules (required/integer/non-zero/positive constraints).
• Telegram permissions now use allowedChats as the canonical field, with structured rules:
  • { chatId, threadId? }
• Legacy allowedChats integer array from master is still supported on load.
• Telegram test action:
  • uses current form config payload when provided,
  • does not silently fallback token when override token is intentionally empty,
  • resolves ${ENV_VAR} placeholders consistently with runtime behavior.
• Bot replies in supergroups now preserve message_thread_id across text, tool messages, voice, artifacts, and command responses.
• Duplicate chat rules are deduplicated before persistence.

Validation

• go test ./api/admin ./clients/telegram ./store
• node --test src/views/clients/allowedChatsRules.test.js
• npx vite build (admin-ui)
• Docker build + reload validated for local run

Manual test checklist

• Verified Telegram API errors are shown in Test toasts with detail preview and overflow count.
• Verified save shows explicit row-level validation errors for invalid allowed chat rules.
• Created/edited Telegram client with structured allowedChats rows (chatId + optional threadId).
• Verified legacy allowedChats integer-array config (from master) is migrated/loaded correctly.
• Verified commands (/start, /help, /agent, /responsemode, /showtools) respond in the same thread/topic.
• Verified normal text replies stay in the originating topic (no fallback to main group feed).
• Verified Test button works with current form values without saving first.
• Verified Test button with direct token uses that token immediately.
• Verified clearing token in form and pressing Test returns proper validation error (no hidden fallback).
• Verified Test button works with secret placeholder token format (e.g. ${TELEGRAM_BOT_API_RPI_MONITOR}).
• Verified invalid chat rules show user-visible errors on save (not only console errors).
• Verified duplicate allowedChats entries are deduplicated on save.
• Diagnosed Telegram-side 409 conflicts and confirmed single consumer behavior.
• Verified Telegram group delivery quirks resolved after bot re-add when platform cache/state was stale.

Screenshots

Admin UI — Telegram chat/thread rules editor

Admin UI — Test action result (success/error)

Telegram — thread reply behavior in supergroup topic

Disclosure

Assisted by AI for implementation and review; all changes were manually validated via tests/build and runtime checks.

[achetronic]

Hi @juanjoGonDev for this PR and contribution!

I have several questions regarding to that. Could you open a related Issue to start discussion about them? I want to merge your changes but I think PRs section is not the proper place to keep the discussion 🙂

[juanjoGonDev]

Hi @juanjoGonDev for this PR and contribution!

I have several questions regarding to that. Could you open a related Issue to start discussion about them? I want to merge your changes but I think PRs section is not the proper place to keep the discussion 🙂

Thanks! I opened issue #23 to continue the discussion and track follow-ups