```text

full-release-validation openclaw/openclaw <run-id> blocking

package-acceptance openclaw/openclaw <run-id> blocking

private-cross-os openclaw/releases-private <run-id> advisory

release-checks openclaw/openclaw <run-id> blocking

```

Store summaries, run URLs, artifact metadata, timings, pass/fail state, and

live Matrix profile and Telegram QA lane before release approval. The live

lanes use the `qa-live-shared` environment; Telegram also uses Convex CI

credential leases. Run the manual `QA-Lab - All Lanes` workflow with

`matrix_profile=all` when you want full Matrix transport, media, and E2EE

inventory; the workflow always shards that full Matrix selection in parallel.

- Cross-OS install and upgrade runtime validation is dispatched from the

private caller workflow

`openclaw/releases-private/.github/workflows/openclaw-cross-os-release-checks.yml`,

which invokes the reusable public workflow

`.github/workflows/openclaw-cross-os-release-checks-reusable.yml`

`matrix_profile=all` and `matrix_shards=true` when you want full Matrix

transport, media, and E2EE inventory in parallel.

- Cross-OS install and upgrade runtime validation is part of public

`OpenClaw Release Checks` and `Full Release Validation`, which call the

reusable workflow

`.github/workflows/openclaw-cross-os-release-checks-reusable.yml` directly

- This split is intentional: keep the real npm release path short,

deterministic, and artifact-focused, while slower live checks stay in their

own lane so they do not stall or block publish