docs: rewrite README against current project state - #2282
Open
MarcosBrendonDePaula wants to merge 1 commit into
Open
docs: rewrite README against current project state#2282MarcosBrendonDePaula wants to merge 1 commit into
MarcosBrendonDePaula wants to merge 1 commit into
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.
Summary
This PR rewrites the project README against the current repository state and removes claims from the deleted engine architecture.
The new README:
rts-cliinstead of the removedrts apiscommand;The README is intentionally shorter and more operational. Detailed architectural rules remain in the crate READMEs and
docs/engine/.Validation
git diff --checkbash -n scripts/cross_runtime_check.shcrates/rts-cli/src/cli/mod.rs.Cargo.toml.A Rust build/test run was not possible in this environment because
cargois not installed. This PR changes documentation only.Review requested
Please review the factual accuracy of the current-status, AOT, Node compatibility, and cross-runtime sections, with particular attention to the intended public onboarding path.