fix: keep ci gate clean-checkout safe#136
Merged
Merged
Conversation
Co-authored-by: Codex <codex@users.noreply.github.com>
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
localbefore directory layer classificationlocaltests from the fast CI gateRoot cause
Local verification was not equivalent to GitHub Actions. The workstation checkout has private B1/Agibot assets and live host state, while Actions checks out without submodule contents or local private data. Some private-asset tests were still classified as
contractbecause the directory layer won before the newlocalchecks. Two operator-console tests also read the real default MCP port and changed result based on whatever was running locally.Verification
just agent::verify ci-required.venv:uv sync --extra dev && just agent::verify ci-required