[beta.2.3] Admit 1.0.0-alpha.1 from a verified real application slice

[SisyphusZheng]

Goal

Timebox the convergence sprint to three working days from implementation start, then enter real application work. This is an execution target, not a promise of green gates or permission to rename unfinished work as complete.

Admission checklist

• Element/Router core boundaries and UI reference scope and both Router modes are reviewable; no mandatory package-renaming campaign.
• URLPatternList differential corpus and HTTP semantics pass; any conservative matching path is explicit and preserves ordered results.
• Real list/detail/form/error flow passes direct access, refresh, navigation, cancellation, SSR/SSG and Element claim.
• Cloudflare, Node and Deno pass the agreed support contract; Bun/Nitro smoke and browser matrix evidence are explicit. Missing evidence is not a pass.
• Fresh packed consumer install/dev/build/run succeeds; no server code in client artifacts.
• Cleanup diagnostics record removed owners/scripts/tasks/paths and every justified survivor; superseded executable paths are retired with their replacements.
• Public API and migration/limitations docs match actual code. Carry nonblocking work to the 1.0 Alpha milestone with owners and acceptance criteria.
• Release planning/automation supports beta.2.N -> 1.0.0-alpha.1 and distinguishes public 1.0 Alpha from historic unpublished v0.44 alpha workspaces ([beta.2.1] Generalize prerelease version semantics for Beta.2 patch releases #1323/[beta.2.3] Establish one release-state authority #1334).
• Exact candidate evidence and existing release GO requirements pass before any tag/publish. Alpha uses npm alpha; latest remains stable.

No-go

Incorrect routing, stale navigation overwriting a newer page, server/client boundary failures, broken required runtime or install path block release. Beta.2.3 may deliver a clearly labeled preview for real application work if release admission is still blocked; incomplete Beta work stays open. No automatic Beta.2.4 or deadline waiver.

Part of #1322. Depends on #1320/#1321 and required cleanup slices. Authority: maintainer-approved 2026-09-07 plan, ADR-0152 and docs/current/VERSION_PLAN.md (documentation PR linked on the train root). Planning is not implementation or release evidence.

Two-core-product refinement (2026-09-07)

• Standalone Element author -> compile -> pack -> plain HTML passes without Router or private workspace imports.
• Compiler artifacts are versioned; browser JS and declaration graphs exclude compiler/Vite/Node-only dependencies.
• Framework tooling reuses Element compilation. Foreign CE host behavior is proven without claiming universal SSR/hydration compatibility.
• UI and reference applications validate the two core products; no separate UI completeness/replacement gate.
  Do not confuse two core products with a mandatory two-package release. No new public compiler API or broad integration matrix is required for this admission.

Accepted refinement — 2026-09-08 (supersedes conflicting earlier scope)

• Admit only after beta.2.1 foundation/fork/repairs, beta.2.2 Native/Lit flow and beta.2.3 dual-mode qualification.
• Both formal integrations have SSR/client continuation/action/navigation evidence and truthful support matrices.
• Four independent consumer modes from [beta.2.3] Consolidate framework fixtures and consumer qualification #1333 pass; documentation/migration/sitemap match qualified outputs.
• Final SHA full CI, ACTUAL review, fresh verifier and release GO. Insufficient-balance wrapper success is not review evidence.
  No automatic beta.2.4 or deadline waiver; remain at the failed checkpoint.

Governing plan (2026-09-08)

Maintainer-approved: ADR-0152, docs/current/VERSION_PLAN.md and #1341. Execution: https://github.com/orgs/open-element/projects/3. Acceptance checkpoints replace the three-day schedule. No automatic beta.2.4. Native/Lit are formal Framework Mode targets, not already-shipped support. Existing release records/versions remain unchanged; no closure without final-SHA evidence. examples/** stays frozen.

Approved executable maturation — 2026-09-09

alpha.1 is the public independently consumable integrated baseline. Existing real-slice/packed/runtime/correctness gates stay intact. Oxc production migration, TS7 full takeover and successful optional experiments are NOT new admission prerequisites. Carry explicit experiment results and unresolved work into Alpha; existing correctness/security failures remain severity-gated.

Scope: docs/architecture/alpha-maturation.md and VERSION_PLAN (planning PR #1342). Upstream contribution potential can justify bounded extra integration cost; no invented defects, PR quota or upstream-response release dependency. This update changes planned work, not implementation status.

Current supplemental review policy — confirmed 2026-09-09

Supersedes earlier AI-review availability merge prerequisites in this issue. Third-party AI review is supplemental and non-blocking. Report provider/API errors visibly; wrapper SUCCESS is not completed review and provider failure contributes zero independent review evidence. Required CI, fresh verifier and human review remain the merge gates. Retain #1343 (comment) as historical evidence. No provider/model switch or billing action is authorized.