Repository navigation
Clarify current v2 status and remaining stable release gates - #9
Merged
Merged
Conversation
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
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.
v2 is already the default framework on main, but the public status still described the completed native application follow-up as pending and omitted the owner's successful Cursor, VS Code and Codex use.
Clarify current-main versus the fixed preview tag, correct the completed deployment status, and record the host feedback explicitly as owner-reported use. VS Code's agent/extension identity and detailed host trial evidence remain unspecified. Add the concrete remaining checklist for a stable 2.0.0 release while preserving historical records and release identities.
Validation:
The update covers README.md, docs/v2/FIELD_TRIALS.md and docs/v2/ROADMAP.md. Framework identity remains 2.0.0-preview.5; the existing immutable preview tag is retained. Stable release promotion remains subject to the documented field, migration and final release checks.