docs(release): record npm telegram beta e2e

.agents/skills/openclaw-release-maintainer/SKILL.md

@@ -287,6 +287,10 @@ node --import tsx scripts/openclaw-npm-postpublish-verify.ts <published-version>
     coverage or a failure needs local debugging.
 - Post-published beta verification roster:
   - `node --import tsx scripts/openclaw-npm-postpublish-verify.ts <beta-version>`
+  - experimental published npm Telegram lane: dispatch
+    `.github/workflows/npm-telegram-beta-e2e.yml` after the beta is visible on
+    npm, using `package_spec=openclaw@<beta-version>`; if it fails from workflow
+    or infrastructure instability, record it as experimental and continue
   - install/update smoke against the published beta channel
   - Docker install/update coverage that exercises the published beta package
   - Parallels published beta install/update coverage with both OpenAI and

docs/reference/RELEASING.md

@@ -94,6 +94,11 @@ 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 npm publish, the experimental `NPM Telegram Beta E2E` workflow
+  (`.github/workflows/npm-telegram-beta-e2e.yml`) can be dispatched with
+  `package_spec=openclaw@YYYY.M.D-beta.N` after npm sees the package. Treat it
+  as extra signal; ignore workflow/infrastructure failure unless it exposes a
+  concrete release bug.
 - 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