docs(alpha.7): publish hardening and adoption task train

Author: DevBot

README.md

@@ -4,7 +4,8 @@ English | [Simplified Chinese](./README.zh.md)
 
 **Web Components-native fullstack framework with a JSX-first Basic Element
 authoring layer. Package line: `0.41.0-alpha.6` (`v0.41.0-alpha.6` release).
-Active execution: v0.41.0-alpha.7 Mac Mastodon Desktop Incubation.**
+Active execution: v0.41.0-alpha.7 Dogfood, Architecture Convergence, and
+Adoption Readiness.**
 
 openElement treats Web Components as the application's native component model.
 It builds static-first applications with JSX/VNode rendering, progressive
@@ -42,15 +43,16 @@ supporting packages = Protocols + UI + official stack adapters
 Supporting packages such as `@openelement/core`, `@openelement/adapter-vite`,
 `@openelement/signal`, `@openelement/router`, `@openelement/content`, and
 `@openelement/ssg` are advanced or implementation surfaces. `@openelement/protocol`
-is the runtime-free contract foundation. `@openelement/ui` is the Open
+is the contract foundation with tiny host-API-free runtime values. `@openelement/ui` is the Open
 Props-backed reference component library and dogfood surface. These packages
 support the two products; they are not separate first-class product lines.
 
 Dogfood apps validate openElement; they do not define it. The Deno Desktop
-Reader and alpha.7 Mastodon Desktop line are evidence surfaces for the framework
-contract, not additional product lines. AutoFlow3, docs truth, release evidence,
-and workflow gates are project infrastructure; they stay out of the Framework
-product story.
+Reader and Mastodon Desktop are completed foundation evidence for the alpha.7
+hardening train, not additional product lines. Alpha.7 now closes architecture,
+browser, security, distribution, adoption, and release-truth gaps exposed by
+that dogfood. AutoFlow3, docs truth, release evidence, and workflow gates are
+project infrastructure; they stay out of the Framework product story.
 
 The active workspace is the 11-package v0.41 line. Hub, RPC, CEM,
 compat-check, Lit/React/vanilla interop adapters, and standalone
@@ -84,16 +86,19 @@ deno run -A npm:@openelement/create my-app
 cd my-app && deno task dev
 ```
 
-**Why it beats the adjacent options**
+**How it differs from adjacent options**
 
 - **vs. Next.js / Nuxt / SvelteKit:** native Web Components instead of a
   framework runtime; the output stays portable and inspectable, not bound to one
   meta-framework.
-- **vs. Astro / Fresh:** islands are first-class OpenElement contracts with
-  shared route and package graphs, not an afterthought wrapper around arbitrary
-  components.
-- **vs. Lit / Enhance / Stencil:** a full app framework — routing, data, deploy,
-  desktop — on top of the same standards, not just a component library.
+- **vs. Astro / Fresh:** OpenElement makes native Custom Elements and DSD the
+  application component contract rather than one possible UI integration.
+- **vs. Lit / Stencil:** OpenElement adds application routing, SSG, deployment,
+  and islands around a Web Components authoring layer. Lit also has an
+  experimental Labs SSR package; alpha.7 will keep this comparison sourced.
+- **vs. Enhance:** both are standards-first full-stack choices; Enhance is
+  HTML/MPA-first, while OpenElement explores JSX, Shadow/DSD, islands, SPA, and
+  desktop targets.
 
 If you want components that outlive the current framework cycle and an app story
 that works with the platform instead of fighting it, openElement is the lane.
@@ -102,17 +107,19 @@ that works with the platform instead of fighting it, openElement is the lane.
 
 All 11 current workspace packages are aligned at **0.41.0-alpha.6**
 (`v0.41.0-alpha.6`) under
-[`@openelement`](https://www.npmjs.com/org/openelement). The alpha.7 release
-proves a read-only, accountless networked desktop app. The active next line is
-**v0.41.0-alpha.7 Mac Mastodon Desktop Incubation**. ADR-0101 keeps
+[`@openelement`](https://www.npmjs.com/org/openelement). The alpha.7 dogfood
+foundation proves a read-only, accountless networked desktop app. The active
+line is **v0.41.0-alpha.7 Dogfood, Architecture Convergence, and Adoption
+Readiness**. Its 21-task exit train turns that evidence into a production build
+path, smaller authoring surface, explicit browser/security truth, five-minute
+starter, reproducible evidence, and external adopter proof. ADR-0101 keeps
 AutoFlow3 as the single workflow/gate control plane while reserving minor/major
 product decisions for human-approved ADR and version-plan evidence.
 
-The next staged lines are **v0.41.0-beta.1 Adoption Freeze**
-and **stable v0.41.0**. Alpha.7 proves a read-only,
-accountless networked desktop app; beta.1 freezes the five-minute starter path,
-API docs, website positioning, logo/brand rendering, npm metadata, and release
-truth before stable v0.41.0.
+The next staged lines are **v0.41.0-beta.1 release-candidate validation** and
+**stable v0.41.0**. Beta.1 re-runs and verifies the alpha.7-frozen starter,
+public API, website, package, evidence, and release surfaces; it does not own a
+new implementation train.
 
 v0.40.x removes Hub, RPC, CEM, compat-check, Lit/React/vanilla interop
 adapters, and standalone runtime/style-sheet/i18n packages from the current

README.zh.md

@@ -3,7 +3,7 @@
 [English](./README.md) | 简体中文
 
 **以 Web Components 为原生组件模型的全栈框架，并内置 JSX-first Basic Element
-authoring layer。当前包线：`0.41.0-alpha.6`（`v0.41.0-alpha.6` 发布）。当前执行线：v0.41.0-alpha.7 Mac Mastodon Desktop incubation。**
+authoring layer。当前包线：`0.41.0-alpha.6`（`v0.41.0-alpha.6` 发布）。当前执行线：v0.41.0-alpha.7 Dogfood、架构收口与采用准备。**
 
 openElement 把 Web Components 当作应用的原生组件模型，使用 JSX/VNode 渲染、渐进式 islands、API routes，以及 Vite + Nitro 输出，构建静态优先的全栈应用。Shadow/DSD 是默认组件渲染模式；light DOM 是显式 opt-in。
 
@@ -29,16 +29,20 @@ supporting packages = Protocols + UI + official stack adapters
 | Web Components Fullstack Framework | `@openelement/app`, `@openelement/create` | Pages、layouts、routes、islands、app targets，以及官方 stack adapters。 |
 | Basic Element                      | `@openelement/element`, `OpenElement`     | JSX-first 原生 Web Components authoring layer，面向 Shadow/DSD 输出。   |
 
-支持包包括 `@openelement/core`、`@openelement/adapter-vite`、`@openelement/signal`、`@openelement/router`、`@openelement/content` 和 `@openelement/ssg`。`@openelement/protocol` 是 runtime-free 契约基础，`@openelement/ui` 是 Open Props-backed 参考组件库和 dogfood surface。它们支撑两个主产品，但不是独立的一线产品。
+支持包包括 `@openelement/core`、`@openelement/adapter-vite`、`@openelement/signal`、`@openelement/router`、`@openelement/content` 和 `@openelement/ssg`。`@openelement/protocol` 是带少量 host-API-free 运行时值的契约基础，`@openelement/ui` 是 Open Props-backed 参考组件库和 dogfood surface。它们支撑两个主产品，但不是独立的一线产品。
 
 Dogfood apps 用来验证 openElement，不能定义 openElement。Deno Desktop Reader
-和 alpha.7 Mastodon Desktop 是框架契约的证据面，不是额外产品线。AutoFlow3、
-docs truth、release evidence 和 workflow gates 是项目基础设施，不进入
-Framework 产品叙事。
+和 Mastodon Desktop 是 alpha.7 hardening train 已完成的基础证据，不是额外
+产品线。alpha.7 当前负责关闭 dogfood 暴露的架构、浏览器、安全、分发、采用和
+release-truth 问题。AutoFlow3、docs truth、release evidence 和 workflow gates
+是项目基础设施，不进入 Framework 产品叙事。
 
 当前 workspace 是 v0.41 的 11 包线。Hub、RPC、CEM、compat-check、Lit/React/vanilla interop adapters，standalone runtime/style-sheet/i18n 包已退出当前包图；`@openelement/protocol` 和 `@openelement/ssg` 保留为 support packages。`@preact/signals-core` 是默认 signal engine。
 
-下一阶段是 v0.41.0-beta.1 Adoption Freeze 和稳定版 v0.41.0。alpha.7 证明只读、无账号的网络桌面 app；beta.1 冻结五分钟 starter 路径、API 文档、官网定位、logo/brand 呈现、npm metadata 和 release truth。
+alpha.7 的 21 项退出任务将只读、无账号网络桌面 dogfood 转换成生产构建路径、
+更小的 authoring surface、明确的浏览器/安全事实、五分钟 starter、可复现证据和
+外部 adopter proof。下一阶段 v0.41.0-beta.1 只重新验证这些已冻结结果，再进入
+稳定版 v0.41.0；它不再承接新的实现任务。
 
 v1.0 目标是稳定的 Web Components fullstack framework 和 Basic Element authoring layer，并冻结 supporting UI、Protocols、official adapter contracts。
 

docs/current/DENO_DESKTOP_TARGET.md

@@ -1,8 +1,9 @@
 # Deno Desktop Target Contract
 
-v0.41 alpha.6 treats Deno Desktop as a first-party OpenElement app target for
-local-first dogfood applications. It is not a localhost browser preview and it
-does not make Reader a separate product line.
+Introduced in v0.41 alpha.6 and retained as alpha.7 dogfood evidence, Deno
+Desktop is a first-party OpenElement app target for local-first applications.
+It is not a localhost browser preview and it does not make Reader or Mastodon
+Desktop a separate product line.
 
 ## Framework Boundary
 

docs/current/STACK_CONTRACT.md

@@ -1,6 +1,6 @@
 # First-Party Stack Contract
 
-This page defines the v0.41 alpha.6 stack vocabulary. OpenElement owns the
+This page defines the current v0.41 alpha.7 stack vocabulary. OpenElement owns the
 framework concepts; the official tools implement those concepts as drivers or
 adapters.
 
@@ -18,8 +18,9 @@ adapters.
 - `DeploymentTarget` names the runtime shape before a concrete deploy adapter
   writes platform output.
 
-These contracts are exported from `@openelement/app/model` and re-exported from
-`@openelement/app`.
+OpenElement App owns the semantics. Dependency-neutral route and asset contracts
+are carried by `@openelement/protocol/app-model`, then re-exported through
+`@openelement/app/model` and `@openelement/app` for authors.
 
 `@openelement/app/hono` is the official default request-driver bridge. It maps a
 Hono-like context into `RequestContext` before OpenElement framework code sees
@@ -66,6 +67,21 @@ decision, not a silent partial render.
 adapter bridge. The adapter-vite root keeps a temporary alpha compatibility
 re-export, but stack docs and new proof code should use the explicit subpath.
 
+These are the current proven implementations, not evidence of unlimited
+replaceability. Alpha.7 makes BuildPlan the production owner (#380), converges
+the adapter-vite interface (#272), separates build/deploy/resolver ownership
+(#273), and resolves whether SignalEngine is fixed or genuinely replaceable
+(#387). Until those slices close, public claims should name the implemented
+Vite/Hono/Nitro/Preact path directly.
+
+## Browser Baseline
+
+Declarative Shadow DOM is available in current Chromium, Firefox, and WebKit.
+The project still carries a legacy injected fallback, so alpha.7 #386 must turn
+the browser target into an executable contract and either remove the default
+fallback or make legacy support explicit. Current output must not claim that
+modern Firefox lacks `shadowrootmode`, and strict CSP behavior must be tested.
+
 ## Boundary Rules
 
 - App model tests must run without booting Hono.
@@ -83,3 +99,5 @@ re-export, but stack docs and new proof code should use the explicit subpath.
   browser preview.
 - Dogfood apps prove the framework contract; they do not create extra product
   lines.
+- Generic SPA navigation belongs to app/router, not the reusable OpenLayout;
+  #381 migrates the current implementation and #274 layers the remaining UI.

docs/current/VERSION_PLAN.md

@@ -29,14 +29,14 @@ The release is staged through alpha lines with explicit execution plans:
   architecture hardening, official stack contracts, Deno Desktop target
   contract, and Reader regression-grade dogfood. Published to npm as
   `0.41.0-alpha.6` with provenance.
-- **alpha.7** (active next): Networked desktop dogfood. A read-only/accountless
-  Mastodon/GoToSocial desktop app that stress-tests SPA mode, Deno Desktop,
-  third-party Web Components interop, render pipeline performance, local
-  state/cache, and error boundaries. Design source:
-  `docs/dogfood/mastodon-desktop/README.md`.
-- **beta.1**: Adoption Freeze. Starter, docs, API reference, website,
-  package metadata, release notes, and visual brand polish must agree before
-  stable v0.41.0.
+- **alpha.7** (active): Dogfood, Architecture Convergence, and Adoption
+  Readiness. The completed read-only/accountless Mastodon/GoToSocial desktop
+  foundation feeds a 21-slice train that closes production build ownership,
+  navigation/UI seams, browser and security truth, package adoption, evidence,
+  and external pilot gaps without adding new product primitives.
+- **beta.1** (planned validation): Re-run the alpha.7-frozen starter, API,
+  website, package, evidence, and release surfaces as a release candidate. It
+  owns no new implementation train.
 
 ## Context
 
@@ -162,13 +162,14 @@ The active work is tracked in per-alpha plan files:
 - `docs/release/v0.41.0-alpha.4-plan.md` — OpenElement components inside Fresh
 - `docs/release/v0.41.0-alpha.5-plan.md` — SPA Mode + Deno Desktop Reader Proof
 - `docs/release/v0.41.0-alpha.6-plan.md` — Front-half cleanup audit, App/protocol architecture hardening, CodeQL cleanup, and Reader dogfood
-- `docs/release/v0.41.0-alpha.7-plan.md` — Networked Desktop Dogfood
-- `docs/release/v0.41.0-beta.1-plan.md` — Adoption Freeze
+- `docs/release/v0.41.0-alpha.7-plan.md` — Dogfood, Architecture Convergence, and Adoption Readiness
+- `docs/release/v0.41.0-beta.1-plan.md` — Release-candidate validation
 
-Alpha.7 starts only after alpha.6 closes the framework architecture loop. The
-beta.1 stabilization phase does not add a new product surface. It freezes
-starter, docs, API reference, website, package metadata, release notes, and
-visual brand polish so v0.41.0 can be adopted without maintainer context.
+Alpha.7 started after alpha.6 closed the first framework architecture loop. Its
+dogfood foundation is complete; the active A7.01–A7.21 issue train in the
+alpha.7 release plan must close before beta.1. Beta.1 does not add product
+surface or absorb alpha architecture debt; it validates the frozen result
+before stable v0.41.0.
 
 ## Governance Rules
 
@@ -190,6 +191,9 @@ visual brand polish so v0.41.0 can be adopted without maintainer context.
 - Package Graph Collapse: reduced from 20 to 11 packages (ADR-0105 cleanup train).
 - AutoFlow3 remains the single CI/release gating plane.
 - Preact + SignalEngine: default reactive stack is `@preact/signals-core` via `@openelement/signal`.
+- Moving package topology in #273 or changing the default signal engine in
+  #387 still requires the normal ADR and approved version-plan authority;
+  inclusion in alpha.7 is not independent permission for a public reset.
 - `docs/current/PACKAGE_SURFACE.md` defines the current 11-package surface.
 - `docs/current/STACK_CONTRACT.md` defines the first-party stack roles for
   Vite, Hono, Nitro, Deno Desktop, Open Props, Preact islands, and third-party
@@ -249,6 +253,11 @@ Build/test gates: `deno task test`, `deno task test:coverage:check`,
 - Deno toolchain truth is explicit: `.dvmrc` pinned to stable `2.9.0`, CI and
   consumer monitor aligned, canary reserved only for Deno Desktop preview
   features outside the main gate matrix.
+- Alpha.7 exit additionally requires all 21 hardening/adoption slices, native
+  browser-baseline evidence, production BuildPlan artifacts, app/router-owned
+  navigation, risk-weighted critical-path tests, auditable dependencies,
+  a clean five-minute npm starter, reproducible performance reports, and the
+  external adopter pilot.
 
 ## Verification