- `node --import tsx scripts/openclaw-npm-postpublish-verify.ts <beta-version>`

- install/update smoke against the published beta channel

- Docker install/update coverage that exercises the published beta package

- published npm Telegram proof: dispatch Actions > `NPM Telegram Beta E2E`

from `main` with `package_spec=openclaw@<beta-version>` and

`provider_mode=mock-openai`, approve `npm-release`, and require success.

This is the default button path for installed-package onboarding,

Telegram setup, and real Telegram E2E against the published npm package.

Use the local `pnpm test:docker:npm-telegram-live` lane with the matching

`OPENCLAW_NPM_TELEGRAM_PACKAGE_SPEC` and Convex CI env only as a fallback

or debugging path.

- Parallels published beta install/update coverage with both OpenAI and

Anthropic provider keys available

- targeted QA reruns only for areas touched by fixes after the full pre-npm

23. Run the post-published beta verification roster. If any lane fails after

the beta tag/package is pushed or published, fix, commit/push/pull,

increment to the next beta tag, and restart at the full pre-npm beta test

roster for the new beta. If a pre-npm lane fails before any tag/package

leaves the machine, fix and rerun the same intended beta attempt. Repeat up

to the operator's authorized beta-attempt limit, normally 4.

roster for the new beta. The roster includes the manual Actions >

`NPM Telegram Beta E2E` workflow against the exact published beta package.

If a pre-npm lane fails before any tag/package leaves the machine, fix and

rerun the same intended beta attempt. Repeat up to the operator's

authorized beta-attempt limit, normally 4.

24. Announce the beta/stable release on Discord best-effort using Peter's bot

token from `.profile`.

25. If the operator requested beta only, stop after beta verification and the