docs: converge Element/Router cores and UI dogfood toward 1.0 Alpha - #1342
Open
SisyphusZheng wants to merge 2 commits into
Open
docs: converge Element/Router cores and UI dogfood toward 1.0 Alpha#1342SisyphusZheng wants to merge 2 commits into
SisyphusZheng wants to merge 2 commits into
Conversation
Contributor
|
APIError: Insufficient Balance |
Deploying openelement with
|
| Latest commit: |
0d82695
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d36ed5c7.lessjs.pages.dev |
| Branch Preview URL: | https://codex-beta2-product-roadmap.lessjs.pages.dev |
This was referenced Sep 7, 2026
SisyphusZheng
changed the title
Contributor
|
APIError: Insufficient Balance |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
The roadmap, issues and release policy still assigned qualification to Beta.3 and treated URLPatternList as upstream-owned. Adopt the maintainer-approved ADR-0152 direction: Element and Router as core products with UI dogfood/reference, explicit and file-generated records on one core, owned URLPatternList, continuous cleanup through Beta.2.1–Beta.2.3, then evidence-gated public 1.0 Alpha.
Replace obsolete current Alpha execution instructions with links to the active plan. Retire the historical orchestration checker/task/test that required completed workspace IDs and withdrawn Beta scheduling in current documents. Existing workflow, version/release truth, protected promotion and release GO requirements remain. Update planning constants and synchronized anchors without changing any source/published package version.
Target and tracking
docs/current/VERSION_PLAN.mdValidation
deno task workflow:checkafter retiring the obsolete Alpha-topology dependency.git diff --check, and lint for the updated planning constants.Release impact
No package bump, tag, publication, dist-tag change or release-history rewrite. Three working days from implementation start is a target, never an admission waiver. Upcoming public 1.0 Alpha is explicitly distinct from historic unpublished v0.44 Alpha workspaces. RC/Stable stay unscheduled and evidence-gated.
Refs #1341. Remaining cleanup and product issues stay open until their own acceptance evidence exists.
Core-product refinement
Element and Router are the two core products; Framework Mode belongs to Router. UI stays dogfood/reference and may retain its existing package. The same Beta.2.x issues now cover standalone Element author/build/pack/plain-HTML delivery, private compiler distribution, versioned artifacts, browser/type dependency isolation and explicit foreign CE SSR boundaries. No forced two-package consolidation, public compiler API or wholesale UI replacement. Project 3 retains its 44 items and existing stages/statuses.