(cherry picked from commit 1b31ede)

(cherry picked from commit 1d99401)

(cherry picked from commit 2cd1a4b)

(cherry picked from commit 34a5523)

(cherry picked from commit 377be13)

(cherry picked from commit 3e8d9bc)

(cherry picked from commit 5197171)

(cherry picked from commit 5f78057)

(cherry picked from commit 60dc46a)

(cherry picked from commit 66aabf5)

(cherry picked from commit 833d0df)

(cherry picked from commit 9780e99)

(cherry picked from commit 9ecd189)

(cherry picked from commit a57c590)

(cherry picked from commit ba1d7b2)

(cherry picked from commit bc1cc2e)

(cherry picked from commit bd8ca6d)

(cherry picked from commit d78b7b3)

(cherry picked from commit d886ca6)

…enclaw#41932)

Merged via squash.

Prepared head SHA: 2f50c51
Co-authored-by: hougangdev <[email protected]>
Co-authored-by: obviyus <[email protected]>
Reviewed-by: @obviyus

(cherry picked from commit e37e1ed)

(cherry picked from commit f201bad)

(cherry picked from commit fbdea7f)

(cherry picked from commit 0672156)

(cherry picked from commit 3cc1c7b)

* feat(telegram): auto-rename DM topics on first message

fix(telegram): use bot.api for topic rename to avoid SecretRef resolution

* fix(telegram): address security + test review feedback

- Fix test assertion: DEFAULT_PROMPT_SUBSTRING matches 'very short'
- Use RawBody instead of Body (no envelope metadata to LLM)
- Truncate user message to 500 chars for LLM prompt
- Remove user-derived content from verbose logs
- Remove redundant threadSpec.id null check
- Fix AutoTopicLabelParams type to match generateTopicLabel

* fix(telegram): use effective dm auto-topic config

* fix(telegram): detect direct auto-topic overrides

* fix: auto-rename Telegram DM topics on first message (openclaw#51502) (thanks @Lukavyi)

---------

Co-authored-by: Ayaan Zaidi <[email protected]>
(cherry picked from commit 466debb)

(cherry picked from commit 55ad5d7)

(cherry picked from commit 5fb7a13)

(cherry picked from commit 60104de)

(cherry picked from commit 9a34a60)

(cherry picked from commit a4047bf)

)

* fix: increase shutdown timeout to avoid SIGTERM hang

* fix(telegram): abort polling fetch on shutdown to prevent SIGTERM hang

* fix(gateway): enforce hard exit on shutdown timeout for SIGTERM

* fix: tighten gateway shutdown watchdog

* fix: harden gateway SIGTERM shutdown (openclaw#51242) (thanks @juliabush)

---------

Co-authored-by: Ayaan Zaidi <[email protected]>
(cherry picked from commit e94ebfa)

- Remove duplicate renameForumTopicTelegram function in send.ts
- Restore tts.test.ts to fork version (upstream version has gutted pi-ai deps)

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- monitor.test.ts: upstream version references tagTelegramNetworkError not in fork
- send.test.ts: upstream version references missing test helpers and unexported functions

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Use direct proxyTls spread instead of upstream's withPinnedLookup helper
which was removed during fork restructuring.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- Add missing GetReplyOptions/MsgContext imports to bot test
- Fix warn parameter typing in draft-stream test

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Upstream versions have deeply entangled barrel import paths that don't
exist in the fork's restructured module layout.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- Rename createNativeCommandTestParams -> createNativeCommandsHarness
- Widen matchPluginCommand mock return type for test flexibility

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Upstream harness refactoring changed return types incompatible with
the test's existing assertions.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

The upstream refactoring of test helpers is incompatible with the fork's
existing test patterns.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Upstream version uses telegramDeps injection pattern not in fork.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- Restore test files overwritten by upstream full-gate commit
- Fix OpenClawConfig -> RemoteClawConfig in extension files
- Fix barrel import paths in extension test files

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- Remove setup/shared files that depend on upstream barrel exports
- Move extension test files to src/telegram/ where their modules live
- Restore channel.ts to fork version

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

- Restore types.plugin.ts to fork version (setup-wizard removed)
- Remove normalize/status-issues tests (modules at extension paths)
- Fix readonly array spread in allowed-updates test
- Add explicit types for dm-access test callback parameters

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Upstream test changes reference infrastructure patterns (gateway injection,
plugin runtime seams) not available in the fork.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

The upstream sendTelegramPayloadMessages refactor may have side effects
on channel registration in tests.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>