openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@0fc3032325

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-29 04:28:28 +00:00
parent 18815a0390
commit cb1de88bb1
3 changed files with 27 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "34ef403cb2a21a8013cb4bcef3d319c8b26a31cf",
"syncedAt": "2026-04-29T04:03:23.259Z"
"sha": "0fc303232506cdcce42306ff71a2b3c657fe2d31",
"syncedAt": "2026-04-29T04:27:03.103Z"
}

17
docs/ci.md
View File

@ -52,6 +52,14 @@ The native live media shards run in
live suites on normal Blacksmith runners, because container jobs are the wrong
place to launch nested Docker tests.
Docker-backed live model/backend shards use a separate shared
`ghcr.io/openclaw/openclaw-live-test:<sha>` image per selected commit. The live
release workflow builds and pushes that image once, then the Docker live model,
gateway, CLI backend, ACP bind, and Codex harness shards run with
`OPENCLAW_SKIP_DOCKER_BUILD=1`. If those shards rebuild the full source Docker
target independently, the release run is misconfigured and will waste the wall
clock on duplicate image builds.
`OpenClaw Release Checks` uses the trusted workflow ref to resolve the selected
ref once into a `release-package-under-test` tarball, then passes that artifact
to both the live/E2E release-path Docker workflow and the package acceptance
@ -216,9 +224,12 @@ manual dispatch; it fans out the mock parity gate, live Matrix lane, and live
Telegram and Discord lanes as parallel jobs. The live jobs use the
`qa-live-shared` environment, and Telegram/Discord use Convex leases. Release
checks run Matrix and Telegram live transport lanes with the deterministic mock
provider so the channel contract is isolated from live model latency; provider
connectivity is covered by the separate live model, native provider, and Docker
provider suites. Matrix uses `--profile fast` for scheduled and release gates,
provider and mock-qualified models (`mock-openai/gpt-5.5` and
`mock-openai/gpt-5.5-alt`) so the channel contract is isolated from live model
latency and normal provider-plugin startup. The live transport gateway also
disables memory search because QA parity covers memory behavior separately;
provider connectivity is covered by the separate live model, native provider,
and Docker provider suites. Matrix uses `--profile fast` for scheduled and release gates,
adding `--fail-fast` only when the checked-out CLI supports it. The CLI default
and manual workflow input remain `all`; manual `matrix_profile=all`
dispatch always shards full Matrix coverage into `transport`, `media`,

12
docs/help/testing.md
View File

@ -110,7 +110,17 @@ parallel jobs. Scheduled QA and release checks pass Matrix `--profile fast`
explicitly, while the Matrix CLI and manual workflow input default remain
`all`; manual dispatch can shard `all` into `transport`, `media`, `e2ee-smoke`,
`e2ee-deep`, and `e2ee-cli` jobs. `OpenClaw Release Checks` runs parity plus
the fast Matrix and Telegram lanes before release approval.
the fast Matrix and Telegram lanes before release approval, using
`mock-openai/gpt-5.5` for release transport checks so they stay deterministic
and avoid normal provider-plugin startup. These live transport gateways disable
memory search; memory behavior stays covered by the QA parity suites.
Full release live media shards use
`ghcr.io/openclaw/openclaw-live-media-runner:ubuntu-24.04`, which already has
`ffmpeg` and `ffprobe`. Docker live model/backend shards use the shared
`ghcr.io/openclaw/openclaw-live-test:<sha>` image built once per selected
commit, then pull it with `OPENCLAW_SKIP_DOCKER_BUILD=1` instead of rebuilding
inside every shard.
- `pnpm openclaw qa suite`
- Runs repo-backed QA scenarios directly on the host.