vrr/openclaw
2
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-10-03 17:53:39 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 31
openclaw/docs/reference/full-release-validation.md
Vincent Koc 375f69237a
docs(reference): split the full release validation guide by reader job (#142774) 
The single page was 68,812 characters and mixed a dispatch how-to, two
rerun procedures, three reference matrices, and policy prose. It is now a
short index over seven child pages, one per reader job, so a reader can
complete one validation pass on one page.

Children under docs/reference/full-release-validation/:

- dispatch.md - Code SHA and Tooling SHA selection, helper inputs, the
  immutable execution plan
- continuation.md - continuing a failed parent, attempt adoption, the
  post-merge continuation proof
- extended-stable.md - extended-stable dispatch, changelog-only reuse,
  coverage policies, Telegram deferrals and waivers
- stages.md - the umbrella stage matrix and decision states
- release-checks.md - the OpenClaw Release Checks matrix and the Docker
  release-path chunks
- profiles.md - profile coverage, full-only additions, focused reruns
- evidence.md - evidence to keep and the backing workflow files

Anchor strategy: per-anchor routes are impossible (a path is not a
fragment, and redirectSource() throws on any source containing [?#]), so
all 11 heading ids from the previous single-page version stay alive on
the parent index as authored <a id="..." /> stubs that link to the child
holding the content. Ids were computed with parseDocsDocument, not a slug
approximation; none collide with an id the index publishes itself. The
pinned .agents/skills/release-openclaw-ci/SKILL.md deep link to
#post-merge-continuation-proof still resolves.

Losslessness: the concatenated child bodies diff against the previous
body in exactly two hunks, both declared cross-reference repairs. Two
"above" references whose antecedent moved to a different child became
real links; a third ("the main-lineage requirement above") keeps its
antecedent on the same child and is unchanged.

Before: 68,812 chars, 7,534 words, 3 code fences, 71 table rows,
11 H2/H3 ids, 1 outbound link.
After: 4,251-char index + 70,728 chars of children; body words
7,491 -> 7,499 (+8, the two link repairs); fences 3 -> 3 with identical
sha256 (46ba930f1d5d9b5a, 611794bc89f9bfb9, f0f2c050f4ef935a), so every
command, workflow input, and SHA-pinning instruction is character-
identical; table rows 71 -> 71; H2/H3 ids 11 -> 11; links 1 -> 3.

Both tests that pin this page are updated: docs-sync-publish gains the
seven child routes in its exact release-tab route list, and
package-acceptance-workflow now reads the index plus its children,
mirroring the ciDocs pattern already used in the same assertion.
docs.json gains a nested group following the reference/test precedent;
zh-Hans-navigation.json needs no change because the locale nav is cloned
from English and that file is only a label overlay.

Closes audit findings: r3-0701
2026-09-09 10:18:22 +08:00

4.2 KiB
Raw Blame History

doc-schema-version summary title read_when
1 Index of the Full Release Validation reference, one page per reader job Full release validation
Running or rerunning Full Release Validation
Comparing stable and full release validation profiles
Debugging release validation stage failures

Full Release Validation is the release product-validation umbrella. Most work happens in child workflows so a failed box can be rerun without restarting the whole release.

This page is an index. The reference is documented on seven pages, one per reader job. Open the page that matches your task and complete that validation pass there.

Page Read it when
Dispatch a validation run Starting a run: Code SHA, Tooling SHA, helper inputs, and the immutable execution plan.
Continue a failed validation Rerunning failed child jobs on an existing parent, and the post-merge continuation proof.
Extended-stable and changelog-only validation Extended-stable dispatch, changelog-only reuse, coverage policies, and Telegram waivers.
Top-level stages The umbrella stage matrix, evidence reuse, artifact producers, and decision states.
Release checks stages The OpenClaw Release Checks stage matrix and the Docker release-path chunks.
Release profiles and focused reruns Comparing profile coverage and picking a focused rerun_group or suite filter.
Evidence to keep Recording evidence after a pass, and the backing workflow files.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /reference/full-release-validation#post-merge-continuation-proof still resolves. Each entry points at the page that now holds the content.

Related