docs(www): retire present-tense 0.43 product claims from current-truth pages (#1177, B2.3)

The architecture collection described the WC SSR classification, corpus and
the Supabase x Cloudflare composition path as 'the 0.43 line' in present
tense while the current line is the compiled v0.44 line; the machinery is
CI-gated on dev (third-party-wc:smoke, fullstack qualification), so the
claims now name the current line and record the 0.43 origin as history.
comparison.md scopes its adoption caution to the stable 0.43 line explicitly.
The 0.41 migration guide gains a historical-record banner: the current line
is consumed fresh via @openelement/create, with no supported 0.43 -> 0.44
in-place upgrade (B2.5 ruling).

Author: DevBot

www/content/architecture/architecture.md

@@ -37,7 +37,7 @@ The roadmap earns WC fullstack leadership through compatibility evidence, comple
 
 ### WC SSR
 
-The 0.43 line classifies admitted standard, Lit, FAST and Stencil elements for DSD, light DOM or client-only rendering with actionable diagnostics and corpus evidence.
+The current line classifies admitted standard, Lit, FAST and Stencil elements for DSD, light DOM or client-only rendering with actionable diagnostics and corpus evidence — a contract first shipped on the 0.43 line and kept green by CI on the compiled line.
 
 ### Application loop
 

www/content/architecture/architecture.zh.md

@@ -35,7 +35,7 @@ order: 10
 
 ### WC SSR
 
-0.43 版本线会把已准入的标准、Lit、FAST 与 Stencil 元素分类为 DSD、light DOM 或仅客户端渲染，并提供可操作的诊断与语料证据。
+当前版本线会把已准入的标准、Lit、FAST 与 Stencil 元素分类为 DSD、light DOM 或仅客户端渲染，并提供可操作的诊断与语料证据——该契约最初随 0.43 线交付，并在编译型版本线上由 CI 持续验证。
 
 ### 应用闭环
 

www/content/architecture/comparison.md

@@ -47,13 +47,13 @@ order: 20
 - Choose **Astro / Enhance / Lit / Stencil** when a standards-first Web Components story matters and you want to avoid a heavy application runtime.
 - Choose **Next.js / Nuxt / SvelteKit** when your product is intentionally built around a React, Vue, or Svelte application model.
 - Choose **Fresh** when you want a Deno-native, near-zero-build Preact island experience.
-- Do not choose **openElement** when a mature ecosystem, a framework-specific UI runtime, or a ready-made enterprise design system is the main requirement. Teams adopting 0.43.x should validate the documented starter and deployment path against their own production environment.
+- Do not choose **openElement** when a mature ecosystem, a framework-specific UI runtime, or a ready-made enterprise design system is the main requirement. Teams adopting the stable 0.43 line should validate the documented starter and deployment path against their own production environment.
 
 ## The official composition path
 
 OpenElement × Supabase × Cloudflare is the verified fullstack delivery path, with explicit ownership boundaries: OpenElement owns the application UX; Supabase owns data, Auth, RLS, Storage and Realtime; Cloudflare owns edge delivery, security, cache and async execution. Supabase and Cloudflare are composed providers — never built-in framework features — and a tier-1 boundary gate keeps provider code out of the framework packages.
 
-Delivered in the 0.43 line together with Universal WC SSR. Framework-owned
+First shipped on the 0.43 line together with Universal WC SSR and carried by the current compiled line. Framework-owned
 production-runtime recovery and cache semantics remain outside the current
 contract and have no assigned release version.
 

www/content/architecture/comparison.zh.md

@@ -47,13 +47,13 @@ order: 20
 - 选择 **Astro / Enhance / Lit / Stencil** 当标准优先的 Web Components 方案很重要，且想避开沉重的应用运行时时。
 - 选择 **Next.js / Nuxt / SvelteKit** 当你的产品明确围绕 React、Vue 或 Svelte 应用模型构建时。
 - 选择 **Fresh** 当你想要 Deno 原生、近乎零构建的 Preact island 体验时。
-- 不要选择 **openElement** 当主要诉求是成熟生态、框架专属 UI 运行时或现成的企业级设计系统时。采用 0.43.x 的团队仍应在自己的生产环境中验证文档里的 starter 与部署路径。
+- 不要选择 **openElement** 当主要诉求是成熟生态、框架专属 UI 运行时或现成的企业级设计系统时。采用稳定 0.43 线的团队仍应在自己的生产环境中验证文档里的 starter 与部署路径。
 
 ## 官方组合路径
 
 OpenElement × Supabase × Cloudflare 是经过验证的全栈交付路径，所有权边界明确：OpenElement 负责应用 UX；Supabase 负责数据、Auth、RLS、Storage 与 Realtime；Cloudflare 负责边缘交付、安全、缓存与异步执行。Supabase 与 Cloudflare 是被组合的服务提供方——绝不是框架内建功能——tier-1 边界门禁保证服务提供方代码不进入框架包。
 
-随 0.43 线与 Universal WC SSR 一同交付。框架自有的生产运行时恢复与缓存语义仍在当前契约之外，尚未分配发布版本。
+最初随 0.43 线与 Universal WC SSR 一同交付，并由当前编译型版本线继承。框架自有的生产运行时恢复与缓存语义仍在当前契约之外，尚未分配发布版本。
 
 - [Supabase 配方](https://github.com/open-element/openelement/blob/main/docs/integrations/supabase.md)
 - [已验证的参考应用](https://github.com/open-element/openelement/tree/main/examples/supabase-cloudflare-starter)

www/content/architecture/package-compatibility.md

@@ -14,7 +14,8 @@ Known packages can be configured as package islands and use available CEM metada
 
 ## Current diagnostics
 
-The 0.43 line ships Universal DSD/light/client-only classification,
-hydration-mismatch diagnostics and the tracked third-party WC SSR corpus.
+The current line ships Universal DSD/light/client-only classification,
+hydration-mismatch diagnostics and the tracked third-party WC SSR corpus —
+first shipped on the 0.43 line and kept green by CI on the compiled line.
 Admission still depends on explicit package-island configuration and observed
 metadata; it is not a blanket certification of every third-party component.

www/content/architecture/package-compatibility.zh.md

@@ -14,4 +14,4 @@ order: 90
 
 ## 当前诊断
 
-0.43 版本线已经交付通用 DSD/light/client-only 分类、hydration 不匹配诊断与已跟踪的第三方 WC SSR 语料库。准入仍依赖显式 package-island 配置与已观测 metadata，并不意味着对所有第三方组件作笼统认证。
+当前版本线交付通用 DSD/light/client-only 分类、hydration 不匹配诊断与已跟踪的第三方 WC SSR 语料库——最初随 0.43 线交付，并在编译型版本线上由 CI 持续验证。准入仍依赖显式 package-island 配置与已观测 metadata，并不意味着对所有第三方组件作笼统认证。

www/content/guide/migration.md

@@ -4,6 +4,8 @@ lede: 'Every breaking change since 0.40.x, grouped by the version that shipped i
 order: 75
 ---
 
+> Historical record: this page archives the 0.40.x → 0.41/0.42 migrations, written for the retired runtime-authoring line. The current line ({{OPENELEMENT_VERSION}}) is consumed fresh through `@openelement/create` — there is no supported 0.43 → 0.44 in-place upgrade. New projects start from the current starter and the [getting-started guide](/guide/getting-started).
+
 ## 0.41.x → 0.42
 
 The stable 0.42 line added request-time surfaces — loaders, actions, progressive-enhancement forms, redirects and Nitro server output. Static-first sites upgraded without a breaking change to the frozen 0.41 surface. ADR-0122 records the accepted 0.42.0 contract.

www/content/guide/migration.zh.md

@@ -4,6 +4,8 @@ lede: '自 0.40.x 以来的全部 breaking change，按发布版本分组。'
 order: 75
 ---
 
+> 历史档案：本页归档 0.40.x → 0.41/0.42 的迁移记录，面向已退役的运行时创作线。当前版本线（{{OPENELEMENT_VERSION}}）通过 `@openelement/create` 全新接入——不提供 0.43 → 0.44 的原位升级路径。新项目请从当前 starter 与[上手指南](/zh/guide/getting-started)开始。
+
 ## 0.41.x → 0.42
 
 稳定的 0.42 版本线新增 request-time 面——loader、action、渐进增强表单、redirect 与 Nitro 服务端输出。静态面升级没有破坏 0.41 冻结面；ADR-0122 记录了已接受的 0.42.0 契约。