docs(roadmap): adopt Beta.2 product convergence and public Alpha (ADR-0152)

Author: DevBot

README.md

@@ -10,7 +10,8 @@ and interactive regions activate selectively.
 The published stable line remains the 0.43 series on npm `latest`.
 `v0.44.0-beta.2` is the current public v0.44 prerelease — Beta.2,
 Productization + Governance Offload (ADR-0151) — published under dist-tag
-`beta`. The next stage is Beta.3 (`v0.44.0-beta.3`).
+`beta`. The accepted next work is Beta.2.1–Beta.2.3 convergence, followed by public
+`v1.0.0-alpha.1` after admission ([roadmap](docs/roadmap/ROADMAP.md)).
 The `1.0.0` target remains unscheduled and requires separate evidence and approval.
 
 ```text
@@ -21,6 +22,11 @@ current proven scope = static-first applications with fullstack output paths
 Source package line: `0.44.0-beta.2` (`v0.44.0-beta.2`).
 npm registry line: `v0.44.0-beta.2` (prerelease, dist-tag `beta`); npm `latest` remains the stable `0.43.3` line.
 
+The accepted product direction is **Element / UI / Router**, with Route Mode
+and Framework Mode sharing one core. [Product boundaries](docs/architecture/product-model.md)
+and [the active plan](docs/current/VERSION_PLAN.md) distinguish planned convergence
+from the currently shipped package surface.
+
 ## Why
 
 OpenElement lets one Custom Element contract work in a standalone library and

README.zh.md

@@ -12,6 +12,12 @@ DOM 是默认服务端表示；交互区域按需升级。
 npm registry 行为 `v0.44.0-beta.2`——预发布版本(dist-tag `beta`)；npm `latest` 仍为
 已发布的稳定 0.43 线。
 
+已确认的产品方向是 **Element / UI / Router**。Route Mode 接受显式路由记录，
+Framework Mode 默认由文件路由生成记录，两者共用内核。自维护 URLPatternList
+是核心技术资产；每次替换同步清理旧实现。下一步为 Beta.2.1–Beta.2.3，验收后
+进入公开 `1.0.0-alpha.1`。详见[产品边界](docs/architecture/product-model.md)和
+[路线图](docs/roadmap/ROADMAP.md)；以下包图描述当前已发布能力。
+
 ## 当前产品
 
 ```text

deno.json

@@ -42,8 +42,7 @@
     "www:apply-seo": "deno run --allow-read --allow-write tools/apply-www-seo.ts",
     "www:pagefind": "cd www && deno run --config ../deno.json --allow-read --allow-write --allow-run --allow-env --allow-net --allow-ffi --allow-sys build-pagefind.ts",
     "preview": "cd www && deno run --allow-read --allow-write --allow-net --allow-env --allow-ffi npm:vite preview --config vite.config.ts",
-    "workflow:check": "deno run --allow-read --allow-run=git tools/check-project-workflow.ts && deno task v044:orchestration:check",
-    "v044:orchestration:check": "deno run --allow-read tools/check-v044-orchestration.ts",
+    "workflow:check": "deno run --allow-read --allow-run=git tools/check-project-workflow.ts",
     "v044:executor:check": "deno run --allow-read --allow-run=kimi tools/check-v044-executor.ts",
     "v044:role": "deno run --allow-read --allow-run tools/run-v044-role.ts",
     "docs:check-role-neutral": "deno run --allow-read tools/check-role-neutral-docs.ts",

docs/adr/ADR-0151-v044-release-train-retopology.md

@@ -1,5 +1,7 @@
 # ADR-0151: v0.44 release train retopology
 
+> Future release scheduling is superseded by [ADR-0152](../adr/ADR-0152-product-router-and-alpha-convergence.md). Historical execution and release evidence below are retained; they do not schedule public 1.0 Alpha.
+
 - Status: ACCEPTED (2026-09-02, maintainer directive)
 - Date: 2026-09-02
 - Supersedes: the Beta-topology portion of ADR-0149 — the five-Beta mapping is

docs/adr/ADR-0152-product-router-and-alpha-convergence.md

@@ -0,0 +1,131 @@
+# ADR-0152: Three products, owned routing core and public 1.0 Alpha
+
+- Status: ACCEPTED (2026-09-07, explicit maintainer direction)
+- Supersedes: ADR-0151's future release topology; upstream-only URLPatternList
+  policy in #1324; cleanup-only-at-Beta.2.3 sequencing; previous file-only Router
+  proposal. Historical release evidence remains unchanged.
+- Preserves: ADR-0148 compiler/Vite boundary, exact-SHA release evidence,
+  protected promotion and release GO requirements, human RC/Stable authority.
+- Tracking: [#1341](https://github.com/open-element/openelement/issues/1341).
+
+## Context
+
+Current package/tool boundaries obscure product responsibilities. Repeated route,
+request, document and governance owners increase maintenance work. The maintainer
+approved a three-working-day convergence target using existing implementations,
+with continuous deletion and a real application slice before public Alpha admission.
+This is a timebox target, not proof that implementation or publication is complete.
+
+## Decision
+
+### Products and dependencies
+
+The products are Element, UI and Router. Element owns compiled Web Components
+execution, serialization and DOM claim/update. UI is a selected component library
+built on Element, independent of Router. Router has two modes:
+
+- Route Mode consumes explicit records; its matching core is independent of
+  Element, Hono, Vite and filesystem access.
+- Framework Mode defaults to file routing and adds page data, forms, Document,
+  Element rendering, navigation, SSR/SSG and official Vite integration. UI is optional.
+
+Explicit and generated records converge on one RouteTable/RouteResolution.
+File paths own generated route paths; no duplicate `route.path` declaration.
+Composition declares mount boundaries, deterministic order and collision behavior.
+Explicit order is preserved; file generation owns its documented ordering policy.
+A selected URL record owns its method map: unsupported methods return 405 rather
+than falling through to a different URL pattern. Query parameters and path captures
+stay separate. Public browser projections exclude server handlers and host bindings.
+
+Products are not package counts. Existing `app`, `adapter-vite` and `create` remain
+implementation/distribution/tooling surfaces until a justified migration changes
+exports. No mandatory package renaming or new broad UI design system is implied.
+
+### URLPatternList is an owned core asset
+
+Start from Justin Fagnani's `url-pattern-list` v0.5.0, source commit
+`4911e649cc11860c7da90c9d0d9b05626c5cbb83`, with verified MIT attribution and a
+compact provenance/divergence record. Own list indexing, ordered traversal,
+differential tests and measured performance. Luca Casonato's proposals inform
+structured matching and conservative fallback; they are not merged production
+Deno implementations to transplant.
+
+URLPattern remains the platform/polyfill single-pattern grammar and capture
+owner. Candidate pruning must not discard a valid earlier match; final `exec`
+cannot recover a candidate already discarded by an incorrect index. Unproven
+optimizations use a conservative candidate path merged in the same sequence order.
+The linear reference oracle belongs in tests. No global API injection, claimed
+standard polyfill, public tree/parser contract, or full replacement URLPattern
+engine. Initial route tables may be rebuilt and atomically replaced; complex
+incremental mutation and speculative native/WASM optimization are deferred.
+
+References: [Justin's source](https://github.com/justinfagnani/url-pattern-list),
+[Luca's proposal](https://github.com/whatwg/urlpattern/pull/166),
+[Deno experiment](https://github.com/denoland/deno/pull/14502).
+
+### Framework responsibility
+
+Hono owns HTTP Context/middleware/Response integration without a second page
+winner. Useful page-data/form abstractions share one request lifecycle; preserve
+validation errors, status, redirects and serialization boundaries. Document owns
+resolved page meaning; Element serializes it. Layouts compose presentation without
+a second data scheduler. Vite owns the official build/development integration.
+
+SSG may read external build-time data; personalized results must not become public
+static output. Sitemap/search use eligible public route identity/catalog data,
+not an enumeration of private request-specific Documents. Navigation coordinates
+abort, stale results, history and required browser fallbacks.
+
+### Continuous reduction
+
+Every replacement retires its displaced implementation, callers, compatibility
+layers, duplicated facts and obsolete checks/docs in the same verified change.
+Cleanup begins in Beta.2.1, continues in Beta.2.2 and closes in Beta.2.3. Measure
+owners, execution hops, custom scripts/tasks/checkers and retained obligations;
+line deletion is not a quota. Preserve required behavior with regression evidence,
+not permanent duplicate paths. Git is the default operational-history archive.
+
+The obsolete `check-v044-orchestration` script/test/task is retired with this
+planning change: it pins current documents to completed Alpha workspace IDs and
+withdrawn Beta scheduling. Current workflow, version/release truth and exact-SHA
+release gates remain; no replacement historical-topology checker is introduced.
+
+### Release topology and timebox
+
+```text
+published v0.44.0-beta.2
+  -> beta.2.1 Router/core + continuous cleanup
+  -> beta.2.2 Framework/Document + continuous cleanup
+  -> beta.2.3 cleanup closure + application admission
+  -> public v1.0.0-alpha.1 and subsequent Alpha iterations
+  -> evidence-gated v1.0.0-rc.1
+  -> separately admitted Stable
+```
+
+The former Beta.3 lane becomes 1.0 Alpha; its unfinished work remains tracked.
+Historic v0.44 alpha workspace IDs remain internal/unpublished. Public 1.0 Alpha
+uses npm `alpha`; npm `latest` stays on the last admitted stable release.
+
+Target three working days from implementation start: Day 1 core plus a minimal
+Cloudflare/Vite spike, Day 2 representative Framework flow, Day 3 remaining cleanup
+and admission evidence. Intermediate public Beta checkpoints retain release gates;
+development may proceed on an accepted contract without waiting for publication.
+No automatic deadline waiver or Beta.2.4. A preview may enter real application work
+while release blockers remain explicitly open; it is not a completed Beta release.
+
+## Acceptance and consequences
+
+[#1340](https://github.com/open-element/openelement/issues/1340) owns Alpha admission:
+matching/HTTP correctness, a packed real-app flow, SSR/SSG/claim/navigation/forms,
+server/client separation, required runtime/browser coverage, cleanup and exact
+candidate release evidence. Cloudflare is the first integration target; Node and
+Deno retain full qualification in their agreed contract, Bun/Nitro their smoke
+scope, Chromium/Firefox/WebKit their required browser coverage. Missing evidence
+is never a pass. Broader benchmarks, prolonged application qualification and UI
+expansion do not block entry unless they expose a core correctness failure.
+
+Release automation must implement the new successor/channel distinction (#1323,
+#1334) before publication. This ADR and its documentation PR do not change package
+versions, publish artifacts, grant Stable readiness, or claim runtime migration
+has already happened. Planning may change now while code still implements the
+published baseline; outstanding implementation is visible in the issue graph.

docs/architecture/product-model.md

@@ -1,6 +1,33 @@
 # Product model
 
-OpenElement is a Web Components-native application framework. A standard Custom
-Element is the durable component boundary. JSX is compiled authoring input, not a
-public runtime virtual-DOM contract. The supported package graph contains `element`,
-`app`, `adapter-vite`, `create`, and optional `ui`.
+OpenElement has three products: **Element**, **UI** and **Router**. This is the
+accepted target under [ADR-0152](../adr/ADR-0152-product-router-and-alpha-convergence.md);
+Beta.2.x issues track implementation. It does not claim all target APIs already ship.
+
+| Product                | Responsibility                                                                                                        | Dependency boundary                                             |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
+| Element                | Compiled Web Components, reactivity, lifecycle, server serialization, fresh DOM and existing-DOM claim/update, styles | Independent component execution foundation                      |
+| UI                     | Selected reusable components, interaction, accessibility, themes and composition                                      | Element; Router optional                                        |
+| Router: Route Mode     | Explicit records, matching/resolution, HTTP and browser integration entry points                                      | Matching core independent of Element, Hono, Vite and filesystem |
+| Router: Framework Mode | File routing by default, page data/forms/errors, layouts, Document, SSR/SSG, navigation and Vite integration          | Same Router core plus Element; UI optional                      |
+
+A standard Custom Element is the durable component boundary. JSX is compiled
+input, not a public runtime virtual-DOM contract. Element's compiler semantics
+remain separate from Vite integration under ADR-0148.
+
+Explicit routes and file-generated routes share one RouteTable/RouteResolution.
+File routes never require a second handwritten path declaration. The Router owns
+composition/order/collision and HTTP policy; its self-maintained URLPatternList
+owns candidate indexing and ordered matching. URLPattern owns single-pattern
+syntax and captures. Public browser records exclude server-only code and bindings.
+
+Element execution and URLPatternList are strategic technical assets. Vite adapter,
+CLI/create, deployment integration and compiler tooling are supporting surfaces,
+not extra product lines. Current packages remain `element`, `app`, `adapter-vite`,
+`create` and optional `ui` until an explicit export migration is implemented.
+Product count is not npm package count.
+
+The initial application target is HTML-first content and dynamic business pages,
+forms and local interactive components. UI stays selected; a full design system,
+generic RPC/ORM/cache/queue framework and comprehensive offline application data
+layer are outside this convergence sprint.

docs/current/DENO_DESKTOP_TARGET.md

@@ -67,7 +67,7 @@ plain modules is mechanical, but the `render()` bodies then fail OEC9007
 re-authoring of nine large renders against the compiled grammar with no
 browser E2E safety net — not a bounded fix. The ruling: the desktop examples
 are **excluded from qualifying consumer evidence** and the re-authoring is
-carried to Beta.3 (B3.8).
+carried to public 1.0 Alpha (#1311); examples remain frozen during Beta.2.x.
 
 `deno task check` and `deno task smoke` stay green and CI-gated
 (`examples:check`), so the examples still qualify the SPA runtime, loaders,