fix: move Codex to provider-owned standalone install - #14
Open
rudijetson wants to merge 1 commit into
Open
Conversation
Reject RUDI-owned Codex binaries, migrate legacy installs only after standalone verification, and keep system registration working through Registry rollout or outage. Preserve current private automation behavior and regenerate the CLI bundle.
This was referenced Aug 19, 2026
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
Closes #13.
Coordinated Registry PR: learnrudi/registry#24.
Verification
pnpm test— 647 passed, 0 failedpnpm build— passed and reproduced tracked bundle output with a clean worktreenode scripts/agent-debt-runner.mjs --changed-since origin/main --no-log— 0 findingsnpm pack --dry-run— passed; 6 expected package filesgit diff --check origin/main...HEAD— passedorigin/mainDeployment boundary
This PR changes source contracts only. It does not install Codex, remove a legacy installation, change credentials, or mutate this follower host. Any host migration remains an explicit post-merge operation after standalone binary verification.