fix(plan): keep planner runtime off fleet workers - #44
Merged
Conversation
Member
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. Keep them coming! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
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
2 participants
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.
Run the shared task-plan expander in a pinned, network-disabled Python container instead of requiring Python on the runner. This preserves runtime-free fleet workers and supports private repositories that cannot use paid GitHub-hosted runners.
The container receives only a tar stream containing plan.py and the project plan, uses a read-only root filesystem with dropped capabilities and bounded resources, and emits GitHub outputs through stdout.
Live evidence: downstream consumer run 30011012524 reached docker-ci but actions/setup-python failed because no Python distribution is available for Debian 13.
Validation: 9 plan tests; fast/full expansion; Python compilation; secret scan; git diff --check. Full Docker execution awaits GitHub CI because Docker is unavailable locally.