docs(rfc): move installation out of runtime CLI - #1408
Open
PsiACE wants to merge 4 commits into
Open
Conversation
PsiACE
marked this pull request as ready for review
August 31, 2026 11:20
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.
Which issue or RFC does this PR close?
N/A. This PR proposes a new RFC.
Ref #1406
Rationale for this change
PowerContext currently installs the Runtime first, then asks the Runtime CLI to clone, build, and install each host integration. This couples release packaging to the CLI and leaves version coordination to users.
What changes are included in this PR?
The RFC defines a distribution-owned installer based on an immutable release manifest, explicit Runtime profiles, and explicit host selection. It also specifies adapter ownership, partial failure, upgrades, conformance, and the migration away from
powercontext setup.English and Chinese RFCs are included.
Are there any user-facing changes?
No immediate behavior changes. If accepted and implemented, installation moves to a standalone installer while Runtime configuration and diagnostics stay in the CLI.
How was this change tested?
make docs-testuv run prek run --files docs/en/rfcs/1408_installation_architecture.md docs/zh/rfcs/1408_installation_architecture.mdAI usage statement
OpenAI Codex (GPT-5) was used to research prior art, draft the RFC, and edit both language versions.