feat(onboarding): manage platform prerequisites#3931
Merged
Conversation
CompleteDotTech
force-pushed
the
feat/onboarding-prerequisites-3922-3923
branch
from
July 26, 2026 22:34
b12c6dd to
5235094
Compare
CompleteDotTech
marked this pull request as ready for review
July 26, 2026 22:49
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
Implements the complete onboarding prerequisite and installation flow for #3922 and #3923.
User impact
Onboarding now distinguishes launch blockers, the managed local runtime toolchain, and optional capability tools. Users can review source, exact version/digest, scope, privilege, restart, and manual-recovery information before consenting to managed installation.
Validation
pnpm buildpnpm typecheckpnpm lintpnpm check:tests-wiredpnpm test:conformancepnpm test:mobilecargo check --lockedinsrc-tauripnpm test:appandpnpm test:apieach reached existing Windows filesystem-policyEPERMfailures (symlink creation and temporary-directory cleanup respectively). Their full Linux executions are required CI coverage and will be monitored here.Closes #3922
Closes #3923