`OpenClaw Release Checks` for install smoke, package acceptance, Docker

release-path suites, live/E2E, OpenWebUI, QA Lab parity, Matrix, and Telegram

lanes. Provide `npm_telegram_package_spec` only after a package has been

published and the post-publish Telegram E2E should run too. Example:

published and the post-publish Telegram E2E should run too. Provide

`evidence_package_spec` when the private evidence report should prove that the

validation matches a published npm package without forcing Telegram E2E.

Example:

`gh workflow run full-release-validation.yml --ref main -f ref=release/YYYY.M.D`

- Run the manual `Package Acceptance` workflow when you want side-channel proof

for a package candidate while release work continues. Use `source=npm` for

--ref main \

-f ref=release/YYYY.M.D \

-f provider=openai \

-f mode=both

-f mode=both \

-f evidence_package_spec=openclaw@YYYY.M.D-beta.N

```

The workflow resolves the target ref, dispatches manual `CI` with

-f ref=release/YYYY.M.D \

-f provider=openai \

-f mode=both \

-f evidence_package_spec=openclaw@YYYY.M.D-beta.N \

-f npm_telegram_package_spec=openclaw@YYYY.M.D-beta.N \

-f npm_telegram_provider_mode=mock-openai

```