docs(status,changelog,roadmap): close 0.41.0 stable gates and record the line

Author: DevBot

CHANGELOG.md

@@ -12,6 +12,29 @@ Current truth lives in:
 Historical changelog details remain available through git history and release
 evidence.
 
+## 0.41.0
+
+- Stable five-package release (ADR-0119): the interface freeze covers
+  `defineElement`, `definePage`, `buildApp`, the package graph, the supported
+  subpaths and the static/SPA semantics of `defineApp`; request-time data,
+  forms, sessions and cache stay explicitly unfrozen until 0.42/0.44.
+- Adapter-vite internal subpaths pruned at the freeze (`app-vite`,
+  `build-context`, `head-injection`, `i18n-plugin`, `plugin`,
+  `generated-data-resolver`, `plugin-mdx`, `route-manifest`,
+  `cli/build-client`, `cli/build-ssg`) — use the root, `nitro-mount`,
+  `cli/build` and `sitemap` instead (breaking; see the migration guide).
+- The #390 external adopter pilot is retired by maintainer decision after
+  zero recruitment (recorded exception, not replaced with internal evidence);
+  the seven-day P0 watch on the 0.41.x patch line starts at this release.
+- Aggregate migration guide from 0.40.x and every alpha line release:
+  `docs/release/v0.41.0-migration.md` and the site's `/guide/migration` page.
+- ui control geometry is squared (`--btn-radius`, `--badge-radius`,
+  `--ui-control-radius`: `--radius-round` → `--radius-1`, 6px) — visual
+  breaking change; update screenshots and custom control CSS.
+- The release verifier now supports stable `x.y.z` versions
+  (prerelease-only before), and the version guards stay honest on a stable
+  current line.
+
 ## 0.41.0-alpha.19
 
 - Third audit round cleanup sweep (ADR-0118, issues #481-#506); no new

docs/roadmap/ROADMAP.md

@@ -122,8 +122,8 @@ Alpha.17 completed the first audit remediation (test credibility, convergence,
 release tooling). Alpha.18 completed the second audit sweep (ADR-0117):
 sibling-path closures, evidence honesty, reflect-prop correctness and
 redundancy cleanup. Alpha.19 completed the third audit cleanup sweep
-(ADR-0118). Stable `0.41.0` is planned under ADR-0119 as a scoped interface
-freeze with the #390 pilot requirement retired by maintainer decision.
+(ADR-0118). Stable `0.41.0` is published under ADR-0119 as a scoped interface
+freeze; the #390 pilot requirement was retired by maintainer decision.
 
 ## Historical record
 

docs/status/STATUS.md

@@ -1,20 +1,22 @@
 # OpenElement Status
 
-> Updated: 2026-07-24\
+> Updated: 2026-07-26\
 > Repository package line: `v0.41.0`\
 > npm registry line: `v0.41.0`\
 > Active release target: `v0.41.0`\
-> Next stability candidate: `v0.41.0`\
+> Next release line: `v0.42.0`\
 > Product graph: five packages\
-> Current maturity stage: alpha
+> Current maturity stage: stable (0.41.x)
 
 ## Current position
 
-OpenElement is a Web Components-native, static-first application framework.
-Alpha.19 completed the third audit cleanup sweep (ADR-0118). The stable
-`0.41.0` release plan is active under ADR-0119: a scoped interface freeze
-over the proven static-first contract and SPA chain, with the #390 pilot
-requirement retired by maintainer decision after zero recruitment.
+OpenElement is a Web Components-native, static-first application framework,
+stable at `0.41.0` under ADR-0119: the interface freeze covers `defineElement`,
+`definePage`, `buildApp`, the five-package graph, the supported subpaths and
+the static/SPA semantics of `defineApp`; request-time semantics stay unfrozen
+until 0.42/0.44. Alpha.19 completed the third audit cleanup sweep (ADR-0118)
+and the #390 pilot requirement was retired by maintainer decision after zero
+recruitment.
 
 Custom Elements are the application component contract; JSX and Basic Element
 are authoring modes; Declarative Shadow DOM is the default server output;
@@ -31,21 +33,20 @@ and output path.
 | `@openelement/create`       | Current  | Installed starter and consumer entrypoint           |
 | `@openelement/ui`           | Optional | Proven primitives; stable scope decided at v0.46    |
 
-## Alpha.19 active gates
+## 0.41.0 stable gates
 
-| Condition                                                            | State                            |
-| -------------------------------------------------------------------- | -------------------------------- |
-| ADR-0118, alpha.19 plan and sweep issues #481-#506                   | Completed                        |
-| Runtime combination-path fixes (reflect, popstate, For token)        | Completed                        |
-| Export-star seam closure and surface pruning                         | Completed                        |
-| Gate mechanization (anchors, www truth, assertions, graph, deno-api) | Completed                        |
-| Dead-code and config hygiene batch                                   | Completed                        |
-| External adopter pilot #390                                          | Launched; pending human evidence |
-| Alpha.19 npm, tag, prerelease and final evidence                     | Completed                        |
+| Condition                                                          | State               |
+| ------------------------------------------------------------------ | ------------------- |
+| ADR-0119 freeze scope (defineApp boundary + adapter subpath prune) | Completed           |
+| #37 gate text refresh (0.41.0 subset, seven-day P0 watch)          | Completed           |
+| Aggregate alpha-line migration guide + ui geometry note            | Completed           |
+| 0.41.0 npm, tag, GitHub release and two-stage evidence             | Completed           |
+| Seven-day P0 watch on the 0.41.x patch line                        | Started 2026-07-26  |
+| External adopter pilot #390                                        | Retired by ADR-0119 |
 
 ## Current risks
 
-1. External adoption remains the primary product risk.
+1. External production adoption is now the primary proof the 0.41.x line needs.
 2. Current-document version drift keeps reappearing at gate edges; alpha.18
    package B makes the anchor gates reject stale claims.
 3. WC SSR compatibility still needs broader adopter evidence.