run over dispatching a duplicate. If you accidentally dispatch a stale duplicate,

cancel it and monitor the current run.

### Release Evidence

After release-candidate validation or before a release decision, record the

important run ids in the private `openclaw/releases-private` evidence ledger.

Use the manual `OpenClaw Release Evidence`

(`openclaw-release-evidence.yml`) workflow there. It writes durable summaries

under `evidence/<release-id>/` and commits:

- `release-evidence.md`

- `release-evidence.json`

- `index.json`

- `runs/<label>.json`

Use one run per line:

```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

```

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

short release-manager notes there. Do not store raw logs, provider

prompts/responses, channel transcripts, signing material, or secret-bearing

config in git; raw logs stay in Actions artifacts.

### Release Checks

`OpenClaw Release Checks` (`openclaw-release-checks.yml`) is the release child