@ccslabs/xtend 0.1.0-rc.1 → 0.1.2

package/docs/en/changelog.md

@@ -0,0 +1,104 @@
+# XTend Changelog
+
+This article collects the historical Epic, workpackage, handoff, and gate
+notes that previously lived in many individual developer articles. The normal
+guides can therefore stay focused on product usage and developer experience;
+this changelog is the canonical place for progress, release signals, and
+technical history.
+
+## RMT vNext and App Shell Authoring
+
+- `RMT-VNEXT-PRIM-01` through `RMT-VNEXT-PRIM-04` built the grammar, parser,
+  semantic graph, and lowering path for RMT vNext primitives.
+- `RMT-VNEXT-PRIM-05` added Fabric lane and fiber evidence for vNext-authored
+  lanes, route fibers, and component fibers.
+- `RMT-VNEXT-PRIM-06` introduced the source-to-sea gate: vNext source, kernel
+  records, Fabric telemetry, UI markers, and browser evidence are correlated by
+  primitive IDs.
+- `RMT-VNEXT-PRIM-07` completed the authoring DX: completions, hover, symbols,
+  code actions, Safe Fix-All, and the VS Code bridge work from real RMT vNext
+  sources.
+- `RMT-VNEXT-PRIM-08` completed migration and legacy backgrounding:
+  App-Platform Primitive JSON remains a mirror/compiler target while vNext is
+  the authoring path.
+- `WP-E15-18` bundled the vNext release handoff. The reference demo lives in
+  `xtendrmt/rmt-vnext-reference-demo.rmt`, and the stable core output lives in
+  `xtendrmt/rmt-vnext-reference-demo.core.json`.
+
+## RMT Tooling, LSP, and Editor Integration
+
+- `WP-E14-02` through `WP-E14-04` stabilized the source model,
+  parser/format adapter, and semantic graph for native `.rmt` documents.
+- `WP-E14-05` through `WP-E14-10` added the linter, CLI, completion, hover,
+  document symbols, definition support, and safe code actions.
+- `WP-E14-11` introduced AI-agent repair reports with `repairPlan`, `fixOrder`,
+  `confidence`, `impact`, and no-op explanations.
+- `WP-E14-12` prepared snippets, editor packaging, and the VS Code bridge.
+- `WP-E14-14` consolidated the Quick Start, linter, and Language Server docs.
+  The contract remains `xtend.rmt.tooling-docs.v1`; the local gate remains
+  `node scripts/run_xtend_tests.js rmt-tooling-docs --json`.
+- `WP-E14-15` and `WP-E14-16` completed the RMT Tooling release gates and the
+  LSP handoff.
+
+## XTendRMT Runtime, Kernel, and Fabric
+
+- Epic 05 established XTendRMT as the productive scheduler, runtime, and
+  templating path: native `.rmt` domains, Runtime Registry, XRouter Adapter,
+  XTend Component Adapter, and State/Scheduler/Diagnostics Bridge.
+- `ER-WP-08` through `ER-WP-21` built Fabric as the host core, including
+  Component Lifecycle Error Boundary, Reporter Adapter, Diagnostics Bridge,
+  component and route fibers, telemetry snapshots, performance measurements,
+  regression checks, and hydration policies.
+- `ER-WP-13` mapped Fabric lanes to host-neutral RMT schedule records. The RMT
+  kernel boundary remains framework-neutral.
+- `RKSH-WP-11` documented kernel migration, trusted output authoring, and the
+  panic/recovery incident handoff.
+
+## Component Platform and App Surfaces
+
+- Epic 10 built TypeScript-first components, Component Contract v2,
+  RMT-first apps, and platform gates.
+- Epic 11 prepared Component UX, shell styling, accessibility, visual
+  regression, enterprise UX handoff, and long-tail migration.
+- SurfaceManager packages `WP-SM-01` through `WP-SM-19` built RMT authoring,
+  controller, window runtime, side panel, workbench fixture, overlay bridge,
+  native RMT surfaces, route lifecycles, persistence, layout engines,
+  component lab, and runtime release handoff.
+- Epic 18 moved App-Platform primitives, Media Manager lessons learned,
+  vendor bugfix backports, and generic RMT App-Platform fixtures into the
+  upstream state.
+
+## Quality, Security, and Release
+
+- Epic 12 bundled RC0 hardening, visual snapshot automation, design token
+  productization, RMT DSL authoring polish, and adoption guides.
+- Epic 13 consolidated RC1 readiness, release owner acceptance, conditional
+  network evidence, package export lock, Trusted DOM, RMT production readiness,
+  visual owner artifacts, and CI handoff.
+- `DPF-WP-02` and `DPF-WP-03` productized the release report, pack dry-run
+  evidence, and conditional network evidence CI.
+- `WP-TypeExports-01` through `WP-TypeExports-09` secured package `types`
+  conditions, RMT/Loader/API/Policy/Builder/Catalog/Vendor facades, and drift
+  reports.
+
+## What No Longer Belongs in Individual Articles?
+
+Developer guides should not read like release logs. New or revised articles
+should:
+
+- explain productive usage, syntax, and architecture;
+- mention local commands only where they are needed for the workflow;
+- keep Epic, WP, status, and handoff history in this changelog;
+- link to `development/` only when an internal detail truly needs to be traced.
+
+## Related Release-Oriented Articles
+
+- [RMT vNext Release Handoff](./rmt-vnext-release-handoff.md)
+- [RMT vNext Source-to-Sea Gate](./rmt-vnext-source-to-sea-gate.md)
+- [RMT vNext Fabric Bridge Evidence](./rmt-vnext-fabric-bridge-evidence.md)
+- [RMT vNext Primitive Authoring Tooling](./rmt-vnext-primitive-authoring-tooling.md)
+- [RMT vNext Primitive Migration](./rmt-vnext-primitive-migration.md)
+- [RC1 Readiness](./rc1-readiness.md)
+- [RC1 Gate Matrix and CI Handoff](./rc1-gate-matrix-ci-handoff.md)
+- [Release Report and Pack Dry Run Evidence](./release-report-pack-dry-run-evidence.md)
+- [TypeExports](./type-exports.md)

package/docs/en/component-catalog-coverage.md

@@ -0,0 +1,104 @@
+# Component Catalog Coverage
+
+- Contract: `xtend.docs.component-catalog-coverage.v1`
+- Matrix Contract: `xtend.catalog.component-coverage-matrix.v1`
+- Gate Contract: `xtend.catalog.component-coverage-gate.v1`
+- Workpackage: `ER-WP-31`, continued by `ER-WP-32`, `ER-WP-33`,
+  `ER-WP-34`, `ER-WP-35`, `WP-E11-12`, `WP-E11-17`, `WP-E12-02`,
+  `WP-E12-03`, `WP-E12-04`, `WP-E12-05`, `WP-E12-06`, `WP-E12-07`,
+  `WP-E12-08`, `WP-E12-09`, `WP-E13-12A`, `WP-SM-03`, `WP-SM-04`, and
+  `RC1TB-WP-03`
+
+The Component Catalog Coverage Matrix shows how mature each component from
+`components/manifest.json` currently is. It combines source, documentation,
+component-level suite, fixture, types, accessibility, and performance into one
+status model.
+
+## Check Locally
+
+```bash
+npm run test:catalog-coverage
+node scripts/run_xtend_tests.js catalog-coverage --json
+```
+
+The gate is green when all manifest sources resolve locally and the matrix
+report is structurally valid. Missing suites, fixtures, types, a11y profiles,
+and performance profiles appear as warnings. This lets the catalog harden step
+by step without hiding follow-up work.
+
+## Status Model
+
+| Status | Meaning |
+|--------|---------|
+| `enterprise-ready` | complete source, docs, suite, fixture, types, a11y, and performance coverage |
+| `typed-contract-gated` | types and a11y exist, performance is still missing |
+| `contract-gated` | source, docs, component suite, and fixture exist |
+| `documented` | source and docs exist |
+| `source-only` | source exists, docs or gates are missing |
+| `missing-source` | manifest points to no local source; this state blocks |
+
+## Current State
+
+The snapshot after `RC1TB-WP-03` shows:
+
+- 44 manifest components
+- 44 local source files
+- 44 component docs
+- 44 component-level suites and fixtures
+- 44 public type artifacts for prioritized components
+- 43 components with a recognizable a11y surface
+- 42 components with an explicit runtime/UI performance profile
+
+`x-input`, `x-select`, `x-checkbox`, `x-radio`,
+`x-rmt-lifecycle-demo-build`, `x-textarea`, `x-form`, `x-calendar`,
+`x-writer`, `x-status`, `x-progress`, `x-tooltip`, `x-popover`, `x-drawer`,
+`x-surface-manager`, `x-surface-portal`, `x-surface-region`,
+`x-surface-window`, `x-side-panel`, `x-modal`,
+`x-dialog`, `x-alert`, `x-toast`, `x-spinner`, `x-router`, `x-link`,
+`x-tabs`, `x-theme`, `x-button`, `x-icon`, `x-menu`, `x-footer`,
+`x-lightbox`, `x-masonry`, `x-code`, `x-header`, `x-hero`, `x-type`,
+`x-summary`, `x-section`, `x-cards`, and `x-player` form the current
+`enterprise-ready` line: source, docs, component suite, fixture, public types,
+a11y, and performance profile are complete. Since
+[Known Residual Triage](./known-residual-triage.md), `xstate` is closed as a
+runtime boundary and `x-utils` is closed as a utility boundary. Both
+intentionally remain outside the visual `enterprise-ready` component class.
+
+Since `ER-WP-35`, the regression priority plan
+`xtend.catalog.component-regression-priority-plan.v1` also exists. It
+prioritizes all 44 manifest entries for `desktop-1280`, `mobile-390`, `light`,
+`dark`, `forced-colors`, `reduced-motion`, browser smokes, and performance
+profile derivation. The 42 visible runtime/UI components bring their
+performance profiles; `xstate` and `x-utils` are evaluated through their
+boundary contracts instead.
+
+## Handoff
+
+| Package | Responsibility |
+|---------|----------------|
+| `ER-WP-32` | completed: close docs and naming gaps |
+| `ER-WP-33` | completed: add component-level suites and fixtures for prioritized components |
+| `ER-WP-34` | completed: complete public types and event contracts for prioritized components |
+| `ER-WP-35` | completed: prioritize long-tail suites, performance profiles, visual and browser-near regression |
+| `WP-E11-12` | completed: bring layout, display, and media shell maturity into catalog, types, suites, and performance profiles |
+
+`WP-E11-17` combines this matrix with the regression priority plan in
+`xtend.epic11.legacy-long-tail-migration.v1`. After `WP-E12-09`, `x-tabs`,
+`x-theme`, `x-button`, and `x-menu` are closed from this long tail. Since
+`WP-E13-05`, `xstate` and `x-utils` are also closed as boundary contracts:
+`xstate` as a runtime boundary with suite, fixture, types, lifecycle events,
+Fabric diagnostics, and RMT state adapter; `x-utils` as a utility boundary with
+utility contract, import policy, fixture, and public types. The gate
+`node scripts/run_xtend_tests.js component-long-tail-migration --json`
+continues to check this closed long-tail line against plan, package, scaffold,
+references, and handoff.
+
+The complete matrix lives in
+`development/XTend-Component-Catalog-Coverage-Matrix.md`. The naming
+convention lives in `development/XTend-Component-Catalog-Naming-Konvention.md`.
+Public types are documented in `docs/public-component-types.md`.
+Visual/browser regression is documented in `docs/visual-browser-regression.md`.
+The machine-readable coverage module lives in
+`catalog/component-catalog-coverage.js`; the regression priority plan lives in
+`catalog/component-regression-priority.js`; the long-tail migration plan lives
+in `catalog/component-long-tail-migration.js`.

package/docs/en/component-lab.md

@@ -0,0 +1,103 @@
+# XTend Component Lab
+
+Contract: `xtend.docs.component-lab.v1`
+
+Starting with `WP-E10-12`, the Component Lab is the local preview and inspection path for TypeScript-first XTend components. It brings together Component Contract v2, RMT metadata, Fabric/Lane context, lifecycle telemetry, accessibility profiles and performance profiles in a shell-first RMT pilot.
+
+## Pilot Artifacts
+
+- Plan module: `xtend-builder/preview/component-lab.js`
+- RMT fixture: `tests/fixtures/rmt-component-lab-pilot.rmt`
+- Contract: `development/XTend-Component-Lab-und-RMT-Inspector-Pilot.md`
+- Gate: `node scripts/run_xtend_tests.js component-lab-rmt-inspector --json`
+
+## Preview Targets
+
+The lab starts with the nine `enterprise-ready` components from Epic 10:
+
+- `x-select`
+- `x-checkbox`
+- `x-radio`
+- `x-textarea`
+- `x-status`
+- `x-progress`
+- `x-tooltip`
+- `x-popover`
+- `x-drawer`
+
+Each target entry points to runtime, TypeScript source, RMT metadata, contract, accessibility, performance, fixture data, browser fixture, docs, public types and component suite.
+
+## RMT Inspector
+
+In the pilot, the RMT Inspector exposes these domains:
+
+- `manifest`
+- `adapters`
+- `components`
+- `routes`
+- `schedules`
+- `templates`
+- `diagnostics`
+
+RMT remains host-neutral. The kernel imports no XTend classes and no XTend types. Execution, DOM materialization, XRouter registration and the Fabric runtime remain adapter responsibilities.
+
+## Panels
+
+| Panel | Purpose |
+|-------|---------|
+| `component-preview` | Show preview target, fixture and component contract |
+| `rmt-inspector` | Inspect the RMT document, routes, schedules and templates |
+| `telemetry` | Make component lifecycle records and Fabric snapshots visible |
+| `a11y` | Show roles, keyboard behavior, screen-reader signals and required assertions |
+| `performance` | Show budget class, lane, hydration policy and measurement points |
+| `source-links` | Link runtime, TS, RMT, docs, types and suite paths |
+
+## Local Gate
+
+```bash
+node scripts/run_xtend_tests.js component-lab-rmt-inspector --json
+```
+
+The gate validates the plan, the RMT fixture, the nine preview targets, all panels, inspector domains, package metadata, runner registration and reference paths.
+
+## Epic 11 UX Inspector
+
+Starting with `WP-E11-13`, the UX Inspector `xtend.epic11.component-lab-ux-inspector.v1` is available as an additional layer.
+
+Artifacts:
+
+- Plan module: `xtend-builder/preview/component-lab-ux-inspector.js`
+- RMT fixture: `tests/fixtures/rmt-component-lab-ux-inspector.rmt`
+- Contract: `development/XTend-Component-Lab-UX-Inspector.md`
+- Gate: `node scripts/run_xtend_tests.js component-lab-ux-inspector --json`
+
+The UX Inspector covers 31 `enterprise-ready` components from the five Epic 11 families:
+
+- Form Controls
+- Feedback and Status
+- Navigation and Routing
+- Overlay and Interaction
+- Layout, Display and Media
+
+The panels extend the earlier pilot with `ux-family-matrix`, `state`, `styling` and `component-network`. The inspector domains are `shell`, `style`, `a11y`, `performance`, `state`, `componentNetwork`, `rmtAuthoring`, `fabricTelemetry`, `diagnostics` and `sourceLinks`.
+
+```bash
+node scripts/run_xtend_tests.js component-lab-ux-inspector --json
+```
+
+This layer is also shell-first, local and host-neutral. RMT describes shell, routes, templates and schedules; XTend components run through adapters outside the kernel.
+
+## SurfaceManager Component Lab
+
+Starting with `WP-SM-09`, there is a Surface-specific lab fixture:
+
+- Docs: [SurfaceManager Component Lab](./surface-manager-component-lab.md)
+- Fixture: `tests/fixtures/rmt-surface-manager-component-lab.rmt`
+- Contract: `xtend.surface.component-lab-fixture.v1`
+- Gate: `node scripts/run_xtend_tests.js surface-release-handoff --json`
+
+The panels `surface-preview`, `native-rmt-inspector`, `migration-diff`, `quality-gates` and `source-links` present the SurfaceManager line as an app-shell lab: native `surfaces[*]`, compatible `components[*].metadata.surface` records, `x-surface-manager`, windows, side panels and the overlay bridge remain testable together without claiming a production `xtend.surface` runtime.
+
+## Handoff
+
+The lab is not a production browser lab server yet. It is the gateable pilot for `WP-E10-13`, where the RMT-first demo app is built without manual shell-specific logic.

package/docs/en/component-long-tail-migration.md

@@ -0,0 +1,41 @@
+# Component Long-Tail Migration
+
+- Contract: `xtend.docs.component-long-tail-migration.v1`
+- Plan contract: `xtend.epic11.legacy-long-tail-migration.v1`
+- Gate contract: `xtend.epic11.legacy-long-tail-migration-gate.v1`
+- Workpackage: `WP-E11-17`
+
+This page describes how XTend handles the last components that are not fully `enterprise-ready` after Epic 11. The plan is intentionally incremental: visible custom elements are hardened against shell, styling, a11y, performance, browser smokes and theme matrix; infrastructure and utility modules receive integration probes instead of artificial UI shells.
+
+Update after `WP-E13-05`: `x-tabs` has an explicit performance profile and is no longer part of the open long-tail plan. `x-theme` has a11y, reduced-motion, forced-colors, performance, theme-propagation and density coverage. `x-button` has performance, interaction-budget, Fabric-measurement and RMT metadata. `x-menu` has performance, keyboard, routing, Fabric and RMT metadata. `xstate` has suite, fixture, public types, lifecycle events, Fabric diagnostics and RMT state adapter and is classified by [Known Residual Triage](./known-residual-triage.md) as `closed-as-runtime-boundary`. `x-utils` has utility contract, import policy, fixture and public types and is classified as `closed-as-utility-boundary`. No open long-tail or boundary-profile decisions remain from this plan.
+
+## Check Locally
+
+```bash
+node scripts/run_xtend_tests.js component-long-tail-migration --json
+npm run test:component-long-tail-migration
+```
+
+## Migration Waves
+
+| Wave | Components | Goal |
+|------|------------|------|
+| `wave-1-p0-routing-interaction` | closed: `x-tabs` | performance profile, browser smoke and theme matrix are complete |
+| `wave-2-p1-theme-and-interaction` | closed: `x-theme`, `x-button`, `x-menu` | performance, a11y, interaction and routing hardening are complete |
+| `wave-3-infrastructure-and-utility-probes` | closed: `xstate`, `x-utils` | suite, fixture, type and boundary decisions are complete; both remain documented as non-visual runtime/utility boundaries |
+
+## Rules for Component Authors
+
+- No long-tail component is rewritten to TypeScript or new shells in a big bang.
+- Custom elements must first close their missing profiles in `components/*`, docs, types and component suites.
+- Non-custom elements such as `xstate` and `x-utils` are tested as infrastructure or utility boundaries.
+- Browser smokes and theme matrix are required only when the surface is genuinely visual or interactive.
+- RMT continues to describe adapter data; the kernel imports no XTend types.
+
+## Source
+
+The migration plan is generated from `catalog/component-catalog-coverage.js` and `catalog/component-regression-priority.js`. The accepted specification is in `development/XTend-Epic11-Legacy-Long-Tail-Migrationsplan.md`.
+
+## RC0 Adoption Update
+
+Since `WP-E12-15`, the [RC0 Adoption Guide](./rc0-adoption-guide.md) summarizes this long-tail status as a migration note for component authors and app authors. For RC0, `xstate` and `x-utils` counted as known, accepted residuals from the Known Residual Policy; they did not block local RC0 review and did not open a publish boundary. Since `WP-E13-05`, both scopes are closed for RC1: `xstate` as a runtime boundary, `x-utils` as a utility boundary.

package/docs/en/component-platform.md

@@ -0,0 +1,243 @@
+# XTend Component Platform
+
+Contract: `xtend.docs.component-platform.v1`
+
+This page describes the current Epic 10 state for new XTend components. New
+components are planned TypeScript-first, shipped locally as ESM artifacts, and
+prepared as RMT-first authoring targets. RMT remains framework-agnostic: XTend
+components are `xtend.component` records, but the RMT kernel imports no XTend
+classes or types.
+
+Since `WP-E10-16`, Epic 10 is complete. The release handoff is documented in
+[Epic 10 Release Handoff](./epic10-release-handoff.md), and complete app
+authoring rules live in [RMT-first XTend Apps](./rmt-first-xtend-apps.md).
+Since `WP-E11-17`, the visible UX rules have been consolidated in
+[Component UX Authoring](./component-ux-authoring.md),
+[Component UX App Authoring](./component-ux-app-authoring.md),
+[Component UX Gates](./component-ux-gates.md), and
+[Component Long-Tail Migration](./component-long-tail-migration.md).
+
+## Platform Layers
+
+- TypeScript source lives under `src/components/<tag>/`
+- Runtime artifacts remain local ESM files under `components/`
+- Public types remain `.d.ts` artifacts under `components/`
+- RMT metadata exists as a separate `ts-rmt` artifact
+- Fabric, telemetry, lanes, a11y, and performance are required domains in
+  `xtend.component.contract.v2`
+- The builder creates contract, source, RMT, a11y, performance, and fixture
+  artifacts as a dry run
+
+## RMT vNext Component Capability Registry
+
+The current RMT vNext line extends this platform with
+`xtend.rmt.component-capability-registry.v1`. The registry is the generic RMT
+interface for XTend UI: it reads `components/manifest.json`,
+`xtend.component.contract.v2`, `xtendRmtMetadata`, `observedAttributes`,
+events, slots, parts, form association, accessibility profiles, and performance
+profiles.
+
+The result is one matrix for all 44 public manifest entries and 40 renderable UI
+components. RMT can build DOM descriptors from it, bind events and state
+bridges, and lazy import components through manifest paths. The RMT kernel stays
+framework-neutral and imports no XTend classes or types.
+
+See [RMT vNext Component Primitives and XTend UI](./rmt-vnext-component-primitives.md).
+
+## P0 Component Wave
+
+WP-E10-08 defines the first P0 component wave as
+`xtend.epic10.p0-component-wave.v1`.
+
+| Component | Package | Focus |
+|-----------|---------|-------|
+| `x-select` | `WP-E10-09` | select control, option slots, value events |
+| `x-checkbox` | `WP-E10-09` | binary input, checked/indeterminate state |
+| `x-radio` | `WP-E10-09` | radio group coordination and keyboard navigation |
+| `x-textarea` | `WP-E10-10` | long-form input, validation, counter |
+| `x-status` | `WP-E10-10` | live region, validation feedback, scheduler status |
+| `x-progress` | `WP-E10-10` | async progress, hydration/task feedback |
+| `x-tooltip` | `WP-E10-11` | lightweight overlay help and describedby mapping |
+| `x-popover` | `WP-E10-11` | interactive anchored overlay |
+| `x-drawer` | `WP-E10-11` | app shell navigation and side panels |
+
+`x-select`, `x-checkbox`, `x-radio`, `x-textarea`, `x-status`, `x-progress`,
+`x-tooltip`, `x-popover`, and `x-drawer` are implemented as the TypeScript-first
+reference line and form the first P0 wave with `enterprise-ready` catalog
+status.
+
+## Component Lab and RMT Inspector
+
+`WP-E10-12` introduces the Component Lab as a shell-first RMT pilot. The lab
+uses `tests/fixtures/rmt-component-lab-pilot.rmt` and the plan module
+`xtend-builder/preview/component-lab.js` to make all nine `enterprise-ready`
+components locally inspectable.
+
+The pilot surface contains:
+
+- component preview for fixture, docs, types, and contract paths
+- RMT Inspector for `manifest`, `adapters`, `components`, `routes`,
+  `schedules`, `templates`, and `diagnostics`
+- telemetry panel for `snapshot.componentTelemetry`
+- a11y and performance notes from Component Contract v2
+- source links to runtime, TS source, RMT metadata, fixture, docs, and suite
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js component-lab-rmt-inspector --json
+```
+
+## RMT-First Demo App
+
+`WP-E10-13` provides the first productive RMT-first demo app without a manual
+shell through `tests/browser/fixtures/rmt-first-demo-app-smoke.html` and
+`xtendrmt/rmt-first-demo-app.rmt`. The host page provides only a
+`data-rmt-host="rmt-first-demo"` root, the local XTend Loader, the local
+manifest, and the RMT runtime.
+
+The app shell, navigation, routes, page templates, component records,
+schedules, Fabric lanes, and diagnostics are rendered from the RMT document.
+The demo uses the full Epic 10 P0 wave: `x-select`, `x-checkbox`, `x-radio`,
+`x-textarea`, `x-status`, `x-progress`, `x-tooltip`, `x-popover`, and
+`x-drawer`.
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js rmt-first-demo-app --json
+```
+
+## Existing Component Metadata
+
+`WP-E10-14` brings existing prioritized components into the RMT/Fabric line as
+a `js-legacy` contract overlay. The machine-readable catalog lives in
+`catalog/epic10-existing-component-metadata.js` and uses the migration strategy
+`js-legacy-contract-overlay-no-runtime-rewrite`.
+
+The target components are `x-router`, `x-link`, `x-input`, `x-form`, `x-modal`,
+`x-dialog`, `x-tabs`, `x-toast`, and `x-alert`. Each component receives
+Contract v2, RMT, Fabric, telemetry, lane, a11y, and performance metadata
+without requiring this package to rewrite the runtime.
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js existing-component-metadata --json
+```
+
+## Epic 10 Platform Gates
+
+`WP-E10-15` bundles the platform rules as `xtend.epic10.platform-gates.v1`.
+The machine-readable plan lives in `catalog/epic10-platform-gates.js` and
+connects Component Contract v2, Existing Component Metadata, the RMT-first demo
+app, browser smokes, a11y, performance, and visual regression.
+
+The fast PR path contains `component-contract-v2`, `epic10-p0-component-wave`,
+`component-lab-rmt-inspector`, `rmt-first-demo-app`,
+`existing-component-metadata`, `browser`, `a11y-hydration`,
+`screenreader-signals`, `motion-contrast`, `regression-priority`, and
+`references`. Release-only performance stays separate through
+`fabric-performance-measurements`, `performance-regression`, and
+`hydration-policy`.
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js epic10-platform-gates --json
+```
+
+## Epic 10 Release Handoff
+
+`WP-E10-16` finalizes the canonical guide structure and the completion contract
+`xtend.epic10.release-handoff.v1`. The machine-readable plan lives in
+`catalog/epic10-release-handoff.js`.
+
+The canonical Component/Fabric boundary is
+`adapter-injection-via-xtend-component-resolveFabricContext`.
+`window.XTendFabric` remains a host convenience and enterprise integration
+surface, but components receive Fabric, lane, and fiber context through the
+`xtend.component` adapter.
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js epic10-release-handoff --json
+```
+
+## Epic 11 Enterprise UX Handoff
+
+`WP-E11-18` finalizes visible Component UX maturity as
+`xtend.epic11.enterprise-ux-handoff.v1`. The machine-readable plan lives in
+`catalog/epic11-enterprise-ux-handoff.js`.
+
+The completion mode is `completed-with-accepted-long-tail-handoff`: shell,
+styling, runtime a11y, performance, component network, RMT shell authoring,
+component lab, browser smokes, theme matrix, and authoring guides are accepted
+as a product line. After `WP-E12-09`, `x-tabs`, `x-theme`, `x-button`, and
+`x-menu` are runtime-closed; `xstate` has suite, fixture, types, and adapter
+boundary probe; `x-utils` has utility contract, import policy, fixture, and
+types. Since `WP-E13-05`, `xstate` is closed as a runtime boundary and
+`x-utils` as a utility boundary for RC1.
+
+The local gate is:
+
+```bash
+node scripts/run_xtend_tests.js epic11-enterprise-ux-handoff --json
+```
+
+## RMT First-Class Support
+
+Every new component must be authorable as an RMT component record:
+
+- Adapter: `xtend.component`
+- Template mode: `dom_descriptor`
+- Event binding: `dom-event-to-rmt-command`
+- Required schedules: `component.visible.mount`, hydration schedule, and
+  `diagnostics.snapshot`
+- Kernel boundary: `no-rmt-kernel-import-of-xtend-types`
+
+RMT therefore describes the component, props, attributes, slots, events,
+hydration, and schedule. XTend executes the Custom Elements locally.
+
+## Fabric, Telemetry, and Lanes
+
+New components must be able to receive Fabric context. This includes:
+
+- `@xtend-fabric` boundary
+- lifecycle operations `mount`, `hydrate`, `render`, `update`, `event`,
+  `error`, `unmount`
+- telemetry snapshot `xtend.fabric.telemetry-snapshot.v1`
+- backpressure-capable measurement points
+- deterministic lane precedence from RMT, component metadata, Fabric override,
+  and blueprint default
+
+## A11y and Performance
+
+A11y is not a downstream test. Form controls need labels, error regions,
+keyboard behavior, and screen reader signals. Feedback components need live
+regions and non-color status signals. Overlays need Escape, focus return, and
+reduced motion.
+
+Performance is also part of the contract. Every component must declare budget
+class, lane, hydration policy, and critical measurement points.
+
+## Local Gates
+
+```bash
+node scripts/run_xtend_tests.js component-ux-authoring-docs --json
+node scripts/run_xtend_tests.js rmt-vnext-component-primitives --json
+node scripts/run_xtend_tests.js component-long-tail-migration --json
+node scripts/run_xtend_tests.js epic11-enterprise-ux-handoff --json
+node scripts/run_xtend_tests.js component-shell-theme-matrix --json
+node scripts/run_xtend_tests.js component-ux-browser-smokes --json
+node scripts/run_xtend_tests.js epic10-p0-component-wave --json
+node scripts/run_xtend_tests.js component-lab-rmt-inspector --json
+node scripts/run_xtend_tests.js rmt-first-demo-app --json
+node scripts/run_xtend_tests.js existing-component-metadata --json
+node scripts/run_xtend_tests.js epic10-platform-gates --json
+node scripts/run_xtend_tests.js epic10-release-handoff --json
+node scripts/run_xtend_tests.js builder-typescript-blueprint --json
+node scripts/run_xtend_tests.js component-contract-v2 --json
+node scripts/run_xtend_tests.js references --json
+```