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@5e27993cbe

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-05-08 10:47:37 +00:00
parent c7672431c9
commit c080c99e94
3 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.openclaw-sync/source.json
View File

@ -1,15 +1,15 @@
{
"repository": "openclaw/openclaw",
"sha": "baffa57c004e361435da81e5e583151e349b2d43",
"sha": "5e27993cbec9bcfa23bebb082f4dda2cd46b63fe",
"sources": {
"openclaw": {
"repository": "openclaw/openclaw",
"sha": "baffa57c004e361435da81e5e583151e349b2d43"
"sha": "5e27993cbec9bcfa23bebb082f4dda2cd46b63fe"
},
"clawhub": {
"repository": "openclaw/clawhub",
"sha": "38c21345906ab1f107a91b33bb86b63667d96643"
}
},
"syncedAt": "2026-05-08T10:34:45.501Z"
"syncedAt": "2026-05-08T10:46:08.319Z"
}

9
docs/concepts/qa-e2e-automation.md
View File

@ -278,7 +278,7 @@ Optional:
- `OPENCLAW_QA_TELEGRAM_CAPTURE_CONTENT=1` keeps message bodies in observed-message artifacts (default redacts).
Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime.ts:44`):
Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime.ts`):
- `telegram-canary`
- `telegram-mention-gating`
@ -287,10 +287,17 @@ Scenarios (`extensions/qa-lab/src/live-transports/telegram/telegram-live.runtime
- `telegram-commands-command`
- `telegram-tools-compact-command`
- `telegram-whoami-command`
- `telegram-status-command`
- `telegram-other-bot-command-gating`
- `telegram-context-command`
- `telegram-current-session-status-tool`
- `telegram-reply-chain-exact-marker`
- `telegram-stream-final-single-message`
- `telegram-long-final-reuses-preview`
- `telegram-long-final-three-chunks`
The implicit default set always covers canary, mention gating, native command replies, command addressing, and bot-to-bot group replies. `mock-openai` defaults also include deterministic reply-chain and final-message streaming checks. `telegram-current-session-status-tool` remains opt-in because it is only stable when threaded directly after canary, not after arbitrary native command replies. Use `pnpm openclaw qa telegram --list-scenarios --provider-mode mock-openai` to print the current default/optional split with regression refs.
Output artifacts:
- `telegram-qa-report.md`

1
docs/help/testing.md
View File

@ -311,6 +311,7 @@ gh workflow run package-acceptance.yml --ref main \
- Runs the Telegram live QA lane against a real private group using the driver and SUT bot tokens from env.
- Requires `OPENCLAW_QA_TELEGRAM_GROUP_ID`, `OPENCLAW_QA_TELEGRAM_DRIVER_BOT_TOKEN`, and `OPENCLAW_QA_TELEGRAM_SUT_BOT_TOKEN`. The group id must be the numeric Telegram chat id.
- Supports `--credential-source convex` for shared pooled credentials. Use env mode by default, or set `OPENCLAW_QA_CREDENTIAL_SOURCE=convex` to opt into pooled leases.
- Defaults cover canary, mention gating, command addressing, `/status`, bot-to-bot mentioned replies, and core native command replies. `mock-openai` defaults also cover deterministic reply-chain and Telegram final-message streaming regressions. Use `--list-scenarios` for optional probes such as `session_status`.
- Exits non-zero when any scenario fails. Use `--allow-failures` when you
want artifacts without a failing exit code.
- Requires two distinct bots in the same private group, with the SUT bot exposing a Telegram username.