docs: clarify release validation and consumer flows

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
2026-03-24 18:00:20 +08:00
parent 50c1e14303
commit c177fbefa4
3 changed files with 128 additions and 7 deletions
@@ -43,7 +43,7 @@ The generated index includes transitive local helpers, not just component entryp
 component starts importing a shared file such as `packages/ui/src/lib/icons.tsx`, rebuild the
 index before merge so source-copy consumers receive the full dependency graph.

-To validate the end-to-end consumer flow locally:
+To validate the end-to-end source-copy consumer flow locally:

 ```bash
 pnpm test:registry:consumer
@@ -52,6 +52,15 @@ pnpm test:registry:consumer
 That smoke test creates a temporary app, runs the registry installer, installs the
 required dependencies, and verifies that the copied source both typechecks and builds.

+For the broader release path, the canonical release gate also includes registry validation and
+both consumer smoke suites:
+
+```bash
+pnpm harness:validate:release
+```
+
+Use that gate before release work that changes package, docs, or consumer-facing behavior.
+
 ## Consumer install flow

 Choose this flow when: