fix: make cloud setup reproducible and report missing capabilities - #11
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
Fresh cloud sessions can install the repository's locked dependencies and missing tools, retain the pinned package manager in later shells, and load the shared command context. Previously setup could silently do nothing or leave commands unavailable.
Downloads are checksum-verified. Missing prerequisites remain unavailable; setup does not claim provider authentication or application readiness. Sending, spending, migrations, financial ingestion and production E2E are excluded. Existing environment permissions are preserved.
Validation
The shared 16-case regression suite passed, including wrong-source rejection, pinned manager resolution in a fresh shell, checksum failures and credential separation. Shell syntax passed and manifests/lockfiles were checked against this repository's remote default branch. Linux-host activation remains to be verified after publication.
Post-Deploy Monitoring & Validation
During this audit, Codex will update the saved cloud setup and inspect a fresh session for verified tools/dependencies and explicit unavailable capabilities. Revert the setup configuration if new sessions cannot launch; a successful setup is not a production application check.