diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 48c4062d9..98bdf692d 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "b98a6a46fb54145a33e753101c02f0d7d7e0bc3b",
-  "syncedAt": "2026-04-24T04:52:59.932Z"
+  "sha": "63653f51d82d0bf2a5ce17eb678c6702b37f0054",
+  "syncedAt": "2026-04-24T04:55:01.811Z"
 }
diff --git a/docs/help/testing.md b/docs/help/testing.md
index c103d0d2f..7a8dda01b 100644
--- a/docs/help/testing.md
+++ b/docs/help/testing.md
@@ -106,6 +106,13 @@ runs the same lanes before release approval.
     endpoint.
   - Use `OPENCLAW_NPM_ONBOARD_CHANNEL=discord` to run the same packaged-install
     lane with Discord.
+- `pnpm test:docker:npm-telegram-live`
+  - Installs a published OpenClaw package in Docker, runs installed-package
+    onboarding, configures Telegram through the installed CLI, then reuses the
+    live Telegram QA lane with that installed package as the SUT Gateway.
+  - Defaults to `OPENCLAW_NPM_TELEGRAM_PACKAGE_SPEC=openclaw@beta`.
+  - Uses the same Telegram env credentials or Convex credential source as
+    `pnpm openclaw qa telegram`.
 - `pnpm test:docker:bundled-channel-deps`
   - Packs and installs the current OpenClaw build in Docker, starts the Gateway
     with OpenAI configured, then enables bundled channel/plugins via config
diff --git a/docs/reference/RELEASING.md b/docs/reference/RELEASING.md
index 829b96795..3df429a05 100644
--- a/docs/reference/RELEASING.md
+++ b/docs/reference/RELEASING.md
@@ -88,6 +88,9 @@ OpenClaw has three public release lanes:
   `node --import tsx scripts/openclaw-npm-postpublish-verify.ts YYYY.M.D`
   (or the matching beta/correction version) to verify the published registry
   install path in a fresh temp prefix
+- After a beta publish, run `OPENCLAW_NPM_TELEGRAM_PACKAGE_SPEC=openclaw@YYYY.M.D-beta.N pnpm test:docker:npm-telegram-live`
+  to verify installed-package onboarding, Telegram setup, and real Telegram E2E
+  against the published npm package.
 - Maintainer release automation now uses preflight-then-promote:
   - real npm publish must pass a successful npm `preflight_run_id`
   - the real npm publish must be dispatched from the same `main` or