docs(release): close v0.42.0-alpha.10 — registry line advances to alpha.10

- npm: all five packages published at 0.42.0-alpha.10, dist-tag alpha;
  latest stays on 0.41.2 (stable)
- registry-line prose updated across STATUS/VERSION_PLAN/README(zh)/
  PROJECT_WORKFLOW; www PUBLISHED_PACKAGE_VERSION = v0.42.0-alpha.10
- release note gains the train summary (97/97 issues, milestone #17) and
  the first-dispatch refusal note (#684 guard working as designed)

Author: DevBot

README.md

@@ -10,7 +10,7 @@ interactive regions upgrade selectively.
 Source package line: `0.42.0-alpha.10` (`v0.42.0-alpha.10`) — the in-flight
 five-package source line under ADR-0119's scoped interface freeze; the
 abandoned beta naming is not an active line.
-npm registry line: `v0.42.0-alpha.9` — the published five-package release.
+npm registry line: `v0.42.0-alpha.10` — the published five-package release.
 The registry line is allowed to lag the source line by one alpha.
 
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

README.zh.md

@@ -8,7 +8,7 @@ Declarative Shadow DOM 是默认服务端表示；交互区域按需升级。
 
 源码包行为 `0.42.0-alpha.10`（`v0.42.0-alpha.10`）——ADR-0119 范围化接口冻结下的
 在途五包源码行；已放弃的 beta 命名不再是当前版本线。
-npm registry 行为 `v0.42.0-alpha.9`——已发布的五包版本；registry 行允许比
+npm registry 行为 `v0.42.0-alpha.10`——已发布的五包版本；registry 行允许比
 源码行滞后一个 alpha。
 
 ## 当前产品

docs/current/VERSION_PLAN.md

@@ -1,8 +1,8 @@
 # v0.42.0 — WC Application Loop (light fullstack) release plan
 
 > Current source package line: `v0.42.0-alpha.10`\
-> Current npm registry line: `v0.42.0-alpha.9` (alpha.10 is the in-flight source line, unpublished)\
-> Next alpha train: `v0.42.0-alpha.10` (post-TP-5.7 remediation)\
+> Current npm registry line: `v0.42.0-alpha.10` (published 2026-08-01, dist-tag `alpha`)\
+> Next alpha train: `v0.42.0-alpha.10` (post-TP-5.7 remediation — shipped; next is TP-6)\
 > Active release target: `v0.42.0-alpha.10`\
 > Planning release target: `v0.42.0` (WC light fullstack / Application Loop)\
 > Next release line: `v0.43.0` (Universal WC SSR)\

docs/governance/PROJECT_WORKFLOW.md

@@ -12,7 +12,7 @@ complete only when the repository contains the decision, the execution package,
 the implementation, and the gates that prove the claim.
 
 Current execution anchor: source package line `v0.42.0-alpha.10`,
-npm registry line `v0.42.0-alpha.9` (published), active train
+npm registry line `v0.42.0-alpha.10` (published), active train
 `v0.42.0-alpha.10` (TP-5.7), and `0.42.0` WC light fullstack planning
 under ADR-0120 and `docs/current/VERSION_PLAN.md`.
 OpenElement is one Web Components-native,

docs/release/v0.42.0-alpha.10.md

@@ -31,3 +31,34 @@ AutoFlow3 patch release evidence: `publish-existing-v0.42.0-alpha.10-2026-08-01T
 - Final completed evidence commit: `c960c2912dbcb0d803e8b8f7e20a4724cb252ab3`
 - Successful release run: https://github.com/open-element/openelement/actions/runs/30708860014
 - GitHub release: https://github.com/open-element/openelement/releases/tag/v0.42.0-alpha.10
+
+## Train summary
+
+Milestone `v0.42.0-alpha.10` (#17) closed **97/97 issues** (open count 0):
+
+- Evidence-chain batch (#646–#653, 2026-07-30): release evidence repair
+  (`persistFailedReleaseEvidence` + version-hole guard), ISR demoted to
+  `@experimental`, CHANGELOG holes, nested-WC submit e2e, silent-catch logging.
+- Round-4 audit remediation (#654–#752, 2026-08-01): the fourth
+  consistency/reliability/redundancy audit
+  ([`docs/audit/2026-08-01-round4-hygiene.md`](../audit/2026-08-01-round4-hygiene.md))
+  plus the same-day audit backlog — P1 correctness (prepare-record publish
+  gate #684, SPA error channels #676/#731, ui a11y/escaping #666/#726,
+  generated-data fail-closed #671, docs truth dual-lining #730), P2 (dead
+  codegen/protocol surface #741, start/fixture unification #732), P3/P4
+  (barrel collapse #739, dead exports, archive conventions #751).
+- Post-train CI repair: clean-tree build evidence (`writeBuildEvidence`
+  creates `.openElement` on ENOENT).
+
+No new product surface; the ADR-0119 freeze surface and the ADR-0120
+Application Loop scope are untouched. Breaking changes on the unfrozen alpha
+surface (`@openelement/app` export drops, `OPEN_PROPS_TOKEN_CSS`,
+open-tabs manifest slot correction) and the new `@experimental` element
+exports (ISR cache types, `hydrateOpenElement`/`disposeOpenElement`) are
+detailed in `CHANGELOG.md` (`0.42.0-alpha.10`).
+
+Release-flow note: the first dispatch (run 30708860014, attempt 1) refused at
+`verify prepare record` because the prepare record lived only on `dev` — the
+#684 guard working as designed; failure evidence was persisted by the #647
+mechanism (`2d46974e`). The record was merged to main (`605c829a`) and the
+rerun completed the full chain.

docs/status/STATUS.md

@@ -1,8 +1,8 @@
 # OpenElement Status
 
-> Updated: 2026-07-28\
+> Updated: 2026-08-01\
 > Repository package line: `v0.42.0-alpha.10`\
-> npm registry line: `v0.42.0-alpha.9` (alpha.10 is the in-flight source line, unpublished)\
+> npm registry line: `v0.42.0-alpha.10` (published 2026-08-01, dist-tag `alpha`)\
 > Active release target: `v0.42.0-alpha.10`\
 > Next release line: `v0.42.0` (WC light fullstack)\
 > Product graph: five packages\
@@ -79,19 +79,19 @@ cache/ISR, auth packages (0.44 or recipes).
 
 ## Release direction
 
-| Version           | Focus                                                             |
-| ----------------- | ----------------------------------------------------------------- |
-| `0.41.0-alpha.17` | First audit remediation baseline (ADR-0116)                       |
-| `0.41.0-alpha.18` | Second audit sweep (ADR-0117)                                     |
-| `0.41.0-alpha.19` | Third audit cleanup sweep (ADR-0118)                              |
-| `0.41.0`          | Separate stable decision after alpha.19 evidence                  |
-| `0.42.0-alpha.8`  | Version hole: TP-5.7 cut failed npm publish; carried into alpha.9 |
-| `0.42.0-alpha.9`  | TP-5.7: light-fullstack floor + audit round 3 + hygiene #619–#623 |
-| `0.42.0-alpha.10` | In-flight source line (bump committed, unpublished)               |
-| `0.42.0`          | WC light fullstack (Application Loop freeze)                      |
-| `0.43.0`          | Universal WC SSR + diagnostics + recipes (#624–#631)              |
-| `0.44.0`          | Production runtime (session/cache/OTel/streaming)                 |
-| `1.0.0`           | Stable five-package product                                       |
+| Version           | Focus                                                                    |
+| ----------------- | ------------------------------------------------------------------------ |
+| `0.41.0-alpha.17` | First audit remediation baseline (ADR-0116)                              |
+| `0.41.0-alpha.18` | Second audit sweep (ADR-0117)                                            |
+| `0.41.0-alpha.19` | Third audit cleanup sweep (ADR-0118)                                     |
+| `0.41.0`          | Separate stable decision after alpha.19 evidence                         |
+| `0.42.0-alpha.8`  | Version hole: TP-5.7 cut failed npm publish; carried into alpha.9        |
+| `0.42.0-alpha.9`  | TP-5.7: light-fullstack floor + audit round 3 + hygiene #619–#623        |
+| `0.42.0-alpha.10` | Audit round 4 + remediation trains (#646–#752); milestone #17 issue-zero |
+| `0.42.0`          | WC light fullstack (Application Loop freeze)                             |
+| `0.43.0`          | Universal WC SSR + diagnostics + recipes (#624–#631)                     |
+| `0.44.0`          | Production runtime (session/cache/OTel/streaming)                        |
+| `1.0.0`           | Stable five-package product                                              |
 
 > **Version hole — `0.42.0-alpha.8` is skipped / npm-unpublished.** Its git tag
 > (`0ec10568`) and GitHub release exist, but the npm publish never completed, so

www/app/data/version.ts

@@ -6,4 +6,4 @@ export const OPENELEMENT_VERSION = 'v0.42.0-alpha.10';
 // Current npm registry line — the newest actually published five-package
 // release. Published/stable copy must use this constant; OPENELEMENT_VERSION
 // is reserved for source-line context.
-export const PUBLISHED_PACKAGE_VERSION = 'v0.42.0-alpha.9';
+export const PUBLISHED_PACKAGE_VERSION = 'v0.42.0-alpha.10';