Update repository front page - #62
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.
What changed
>=22.13.0 <25and npm11.9.0.Why
The previous front page functioned mainly as a setup guide and contained stale toolchain requirements. It did not prominently identify the public beta or explain the repository's current governance, verification, and restricted-use boundaries.
Impact
This is a documentation-only change. It does not alter application code, workflows, release controls, or security boundaries.
Validation
The content was checked against the current
README.md, rootpackage.json,config/ross-brand.json, and the repository's documented release and exact-head verification model. Exact-head Baseline verification remains required before merge.