docs: add maturity docs routes (#91483) · openclaw/openclaw@4a503ed
RomneyDa
·
2026-06-24
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -118,6 +118,7 @@
|
118 | 118 | - any-glob-to-any-file: |
119 | 119 | - "extensions/qa-lab/**" |
120 | 120 | - "qa/scenarios/**" |
| 121 | + - "docs/maturity/**" |
121 | 122 | - "docs/concepts/qa-e2e-automation.md" |
122 | 123 | - "docs/concepts/personal-agent-benchmark-pack.md" |
123 | 124 | - "docs/channels/qa-channel.md" |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -24,6 +24,14 @@ This directory owns docs authoring, Mintlify link rules, and docs i18n policy.
|
24 | 24 | - `scripts/docs-sync-publish.mjs` excludes and prunes `docs/internal/**` from the public `openclaw/docs` publish repo if a page is force-added later. |
25 | 25 | - Internal docs may mention repo paths, private app names, 1Password item names, and runbooks, but never include secret values. |
26 | 26 | |
| 27 | +## Maturity Scorecard Editing |
| 28 | + |
| 29 | +`taxonomy.yaml` and `qa/maturity-scores.yaml` are the source inputs; generated maturity docs under `docs/maturity/` are projections and should not be hand-edited for score, LTS, taxonomy, QA profile, or evidence tables. |
| 30 | +`scripts/qa/render-maturity-docs.ts` owns generation; use `pnpm maturity:render` to refresh committed docs and `pnpm maturity:check` to verify them. |
| 31 | +`.github/workflows/maturity-scorecard.yml` renders artifact previews and can open generated-doc PRs; `.github/workflows/openclaw-release-checks.yml` dispatches it for release QA. |
| 32 | +Keep deterministic `qa-evidence.json.scorecard` data in GitHub Actions artifacts unless a maintainer explicitly asks for a sanitized committed projection. |
| 33 | +Human overrides must change source state in a PR and explain the reason plus public or redacted evidence. |
| 34 | + |
27 | 35 | ## Docs i18n |
28 | 36 | |
29 | 37 | - Foreign-language docs are not maintained in this repo. The generated publish output lives in the separate `openclaw/docs` repo (often cloned locally as `../openclaw-docs`). |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -966,6 +966,7 @@ output and whose artifact paths are resolved relative to that producer
|
966 | 966 | `qa run --qa-profile`, the same `qa-evidence.json` also includes the profile |
967 | 967 | scorecard summary for the selected taxonomy categories. |
968 | 968 | Treat it as a discovery aid, not a gate replacement; the selected scenario still needs the right provider mode, live transport, Multipass, Testbox, or release lane for the behavior under test. |
| 969 | +For scorecard context, see [Maturity scorecard](/maturity/scorecard). |
969 | 970 | |
970 | 971 | For character and style checks, run the same scenario across multiple live model |
971 | 972 | refs and write a judged Markdown report: |
@@ -1023,6 +1024,7 @@ When no `--judge-model` is passed, the judges default to
|
1023 | 1024 | ## Related docs |
1024 | 1025 | |
1025 | 1026 | - [Matrix QA](/concepts/qa-matrix) |
| 1027 | +- [Maturity scorecard](/maturity/scorecard) |
1026 | 1028 | - [Personal agent benchmark pack](/concepts/personal-agent-benchmark-pack) |
1027 | 1029 | - [QA Channel](/channels/qa-channel) |
1028 | 1030 | - [Testing](/help/testing) |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -20,6 +20,7 @@ of Docker runners. This doc is a "how we test" guide:
|
20 | 20 | |
21 | 21 | - [QA overview](/concepts/qa-e2e-automation) - architecture, command surface, scenario authoring. |
22 | 22 | - [Matrix QA](/concepts/qa-matrix) - reference for `pnpm openclaw qa matrix`. |
| 23 | +- [Maturity scorecard](/maturity/scorecard) - how release QA evidence supports stability and LTS decisions. |
23 | 24 | - [QA channel](/channels/qa-channel) - the synthetic transport plugin used by repo-backed scenarios. |
24 | 25 | |
25 | 26 | This page covers running the regular test suites and Docker/Parallels runners. The QA-specific runners section below ([QA-specific runners](#qa-specific-runners)) lists the concrete `qa` invocations and points back at the references above. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
