docs(plan): focus Element and Router cores with UI dogfood (ADR-0152)

Author: DevBot

README.md

@@ -22,8 +22,9 @@ 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)
+The accepted core products are **Element / Router**, with Route Mode
+and Framework Mode sharing one Router core. UI is dogfood and a reference
+implementation, not a third core product. [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.
 

README.zh.md

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

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

@@ -1,4 +1,4 @@
-# ADR-0152: Three products, owned routing core and public 1.0 Alpha
+# ADR-0152: Element / Router cores, reference UI and public 1.0 Alpha
 
 - Status: ACCEPTED (2026-09-07, explicit maintainer direction)
 - Supersedes: ADR-0151's future release topology; upstream-only URLPatternList
@@ -20,9 +20,10 @@ This is a timebox target, not proof that implementation or publication is comple
 
 ### 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:
+The core products are Element and Router. UI is dogfood and a reference implementation. Element owns compiled Web Components
+execution, serialization and DOM claim/update. UI is a selected component reference
+built on Element, independent of Router. It validates authoring, interoperability
+and real application use; it does not promise a comprehensive design system. Router has two modes:
 
 - Route Mode consumes explicit records; its matching core is independent of
   Element, Hono, Vite and filesystem access.
@@ -41,6 +42,29 @@ Products are not package counts. Existing `app`, `adapter-vite` and `create` rem
 implementation/distribution/tooling surfaces until a justified migration changes
 exports. No mandatory package renaming or new broad UI design system is implied.
 
+### Maintainer refinement: two core products and independent Element delivery
+
+The 2026-09-07 follow-up refines the earlier three-product wording: Element and
+Router are the core products; Framework Mode belongs to Router. UI is dogfood and
+reference implementation, alongside the website/representative consumer application.
+Its current package may remain available without an independent design-system
+roadmap. Do not force two physical npm packages or replace all UI in this sprint.
+
+The private compiler has an explicit distribution path through Element tooling;
+published artifacts cannot depend on unpublished workspaces. Compiler and runtime
+meet at versioned generated artifacts. Router tooling reuses Element's build path,
+never defines component semantics or ships a duplicate compiler. Separate build,
+browser, server and declaration entry graphs; preserve source maps and compiler
+source diagnostics. Public tooling subpaths are permitted without publishing a
+stable compiler API or hiding Vite behind a second configuration system.
+
+Standalone qualification means author -> compile -> pack -> ordinary HTML consumer,
+without Router or a workspace alias. A lightweight Element runtime dependency is
+allowed; compiler/Node/Vite code must not leak into browser output or browser types.
+Foreign CE property/attribute/event/upgrade boundaries need real browser evidence.
+Internal foreign SSR/hydration remains component-specific, not a universal DSD
+promise. Broader React/Vue/etc. integration matrices are Alpha follow-up work.
+
 ### URLPatternList is an owned core asset
 
 Start from Justin Fagnani's `url-pattern-list` v0.5.0, source commit

docs/architecture/product-model.md

@@ -1,13 +1,14 @@
 # Product model
 
-OpenElement has three products: **Element**, **UI** and **Router**. This is the
+OpenElement has two core products: **Element** and **Router**. UI is dogfood
+and a reference implementation, not a third core product. 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                                        |
+| UI (reference)         | Dogfood components demonstrating 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                      |
 
@@ -28,6 +29,26 @@ not extra product lines. Current packages remain `element`, `app`, `adapter-vite
 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,
+forms and local interactive components. UI stays a selected dogfood/reference surface; a full design system,
 generic RPC/ORM/cache/queue framework and comprehensive offline application data
 layer are outside this convergence sprint.
+
+## Standalone delivery and reference applications
+
+Element must be independently authored, built, packed and consumed from plain HTML
+without Router or private workspace dependencies. Its compiler remains private,
+with a versioned artifact contract; build integration delivers the compiler through
+an explicit tooling entry. Runtime/browser/type entry graphs must exclude Vite,
+TypeScript compiler and Node-only implementation. Framework tooling reuses the same
+Element compilation path; it does not own Element language semantics.
+
+UI supplies selected dogfood components. The website and a representative consumer
+supply reference application evidence. Their defects can reveal core blockers, but
+component count, UI redesign, replacement with Web Awesome, and reference-site
+expansion are not independent Beta.2.x release objectives. The existing ui package
+may remain published; product demotion is not a package removal or migration claim.
+
+Foreign Custom Elements are opaque browser-standard boundaries. OE binds host
+properties/attributes/events/slots without compiling their internals. Foreign SSR
+and hydration require an explicit supported integration; DSD alone is not a shared
+hydration protocol. No mandatory Web Awesome dependency or wrapper library.

docs/current/VERSION_PLAN.md

@@ -23,7 +23,7 @@ and immutable release records; this plan describes intended work, not release pr
 
 ## Objective and scope
 
-Converge Element / selected UI / Router, with Route Mode explicit records and
+Converge Element and Router, with UI as dogfood/reference, with Route Mode explicit records and
 Framework Mode file-generated records sharing one routing core. Own URLPatternList
 as a strategic asset; reuse existing Element/app/Vite implementation. Continuously
 remove displaced semantic owners and operational machinery. Enter real application
@@ -34,11 +34,11 @@ work through an evidence-gated public `1.0.0-alpha.1`.
 Three working days from implementation start, not three elapsed days from this
 planning PR. An elapsed deadline does not complete an issue or authorize release.
 
-| Checkpoint       | Target                          | Work and evidence                                                                                                                 |
-| ---------------- | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
-| Beta.2.1 / Day 1 | Router/core + cleanup           | #1320: records/products #1338, owned fork #1324, resolution #1325, release semantics #1323; early Cloudflare/Vite page/form spike |
-| Beta.2.2 / Day 2 | Framework/Document + cleanup    | #1321: real flow #1339, resolved Document #1326, public metadata projections #1327                                                |
-| Beta.2.3 / Day 3 | Remaining cleanup and admission | #1322: #1328-#1334, #1156, #1188/#1189 residual scope; Alpha admission #1340                                                      |
+| Checkpoint       | Target                          | Work and evidence                                                                                                                                                |
+| ---------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Beta.2.1 / Day 1 | Router/core + cleanup           | #1320: core products/records/Element delivery contract #1338, owned fork #1324, resolution #1325, release semantics #1323; early Cloudflare/Vite page/form spike |
+| Beta.2.2 / Day 2 | Framework/Document + cleanup    | #1321: standalone Element + reference application flow #1339, resolved Document #1326, public metadata projections #1327                                         |
+| Beta.2.3 / Day 3 | Remaining cleanup and admission | #1322: #1328-#1334, #1156, #1188/#1189 residual scope; Alpha admission #1340                                                                                     |
 
 Every replacement removes its obsolete path and dependent wrappers/checkers/docs
 with regression evidence. Day 3 does not postpone cleanup from earlier changes.
@@ -47,13 +47,22 @@ Examples remain frozen in this sprint; #1311 is carried to public Alpha.
 
 ## Non-goals
 
-UI expansion, a complete design system, full URLPattern reimplementation,
+UI expansion or wholesale replacement, a complete design system, public compiler API,
+mandatory two-package consolidation, full URLPattern reimplementation,
 speculative matcher acceleration, native/WASM ports, complex incremental table
 mutation, generic bundler/platform expansion, RPC/ORM/queue/cache frameworks,
 comprehensive offline data handling, arbitrary directory/filename refactoring.
 
 ## Acceptance
 
+- Element independently compiles/packs and runs in a plain HTML consumer without
+  Router or private workspace imports. The private compiler is delivered through
+  tooling; its versioned artifacts work with the admitted runtime. Browser JS and
+  type graphs exclude compiler/Vite/Node-only dependencies.
+- UI and the representative application provide dogfood/reference evidence, not a
+  third product-release checklist. Existing UI remains usable; no forced replacement.
+- Foreign CE host binding/upgrade behavior is tested; internal foreign SSR/hydration
+  is supported only through an explicit integration, not inferred from DSD.
 - Both route sources use one table; deterministic composition and conflict rules.
 - URLPatternList agrees with the ordered reference oracle; safe conservative
   matching is allowed, silent false negatives are not.

docs/governance/PROJECT_WORKFLOW.md

@@ -20,7 +20,7 @@ Current execution direction is owned by
 convergence -> public 1.0 Alpha -> evidence-gated RC/Stable. Actual version and
 publication facts remain in `docs/release/release-state.json`.
 
-The products are Element, UI and Router. Supporting packages are not additional
+The core products are Element and Router. UI is dogfood and a reference implementation. Supporting packages are not additional
 product lines. Cleanup is part of every replacement, beginning in Beta.2.1.
 Historic v0.44 Alpha workspace instructions do not govern public 1.0 Alpha.
 

docs/roadmap/ROADMAP.md

@@ -12,17 +12,19 @@ Stable `1.0.0` remains unscheduled.
 
 Execution follows [PROJECT_WORKFLOW.md](../governance/PROJECT_WORKFLOW.md).
 
-OpenElement's products are **Element / UI / Router**. See the
+OpenElement's core products are **Element / Router**; UI is dogfood and a reference implementation. See the
 [product model](../architecture/product-model.md) and accepted
 [ADR-0152](../adr/ADR-0152-product-router-and-alpha-convergence.md).
 
 ## Active direction
 
 The published Beta.2 baseline is followed by three convergence checkpoints:
 
-1. **Beta.2.1:** general Router core, self-maintained URLPatternList, explicit and
+1. **Beta.2.1:** core product boundaries and standalone Element delivery contract,
+   general Router core, self-maintained URLPatternList, explicit and
    file-generated records, shared resolution and immediate cleanup.
-2. **Beta.2.2:** Framework Mode page/form/navigation lifecycle, Document, Element
+2. **Beta.2.2:** standalone Element packed-consumer proof, Framework Mode
+   page/form/navigation lifecycle, Document, Element
    and Vite integration, with replacement-time cleanup.
 3. **Beta.2.3:** remaining repository/governance reduction and real-application
    admission evidence.

docs/roadmap/v0.44.0-ISSUES.md

@@ -11,8 +11,8 @@ not a manually duplicated completion ledger.
 
 | Phase              | Parent | Work                                                                                                                                                                   |
 | ------------------ | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Beta.2.1           | #1320  | #1338 products/record model; #1324 owned URLPatternList; #1325 shared resolution; #1323 version and channel semantics                                                  |
-| Beta.2.2           | #1321  | #1339 Framework application flow; #1326 Document; #1327 public metadata projections                                                                                    |
+| Beta.2.1           | #1320  | #1338 core products/record model/standalone Element contract; #1324 owned URLPatternList; #1325 shared resolution; #1323 version and channel semantics                 |
+| Beta.2.2           | #1321  | #1339 standalone Element + Framework reference flow; #1326 Document; #1327 public metadata projections                                                                 |
 | Beta.2.3           | #1322  | #1328 lifecycle census; #1329 debris; #1330 tools; #1331 tasks; #1332 CI; #1333 fixtures; #1334 release-state authority; #1340 Alpha admission                         |
 | Continuous cleanup | #1322  | #1156 mature tooling; #1188 governance/docs; #1189 repository weight; #1192 distinct residual closure obligations                                                      |
 | 1.0 Alpha          | #1155  | #1179 real SaaS; #1234-#1242 artifact/benchmark/performance/error/consumer/runtime/lifecycle qualification; #1187 release-hardening remainder; #1311 deferred examples |

packages/ui/README.md

@@ -1,6 +1,11 @@
 # @openelement/ui
 
-First-party reference UI package for the OpenElement framework.
+First-party dogfood and reference UI package for OpenElement.
+
+Element and Router are the two core products; Router includes Framework Mode.
+UI demonstrates and tests those products rather than defining a third core product
+or a comprehensive design-system roadmap. The existing package remains available;
+this positioning does not remove components or force migration to another library.
 
 The components are first-party `open-*` Web Components. They are designed to
 prove the OpenElement authoring model with shadow/DSD output, explicit light DOM