Implement proactive preflight planning#229
Merged
pengfei-threemoonslab merged 2 commits intoJun 18, 2026
Merged
Conversation
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 Phase 3 proactive Shipgate planning without adding a second release verdict engine.
PreflightResultV2,PreflightPlanV1, andHostPermissionRequestV1, including deterministicsignals[], verify routing, plan summaries, and optional host-grant drift.agents-shipgate preflight --workspace . --plan <path|-> --jsonwhile preserving legacy preflight flags as compatibility shorthands.core.host_grantsand keepsaudit --hostas a thin CLI wrapper.shipgate.preflighttool to acceptplan..well-known, agent instructions, skills, Cursor rules, and adoption harness criteria around the new plan-native proactive flow.Validation
ruff check .python scripts/generate_schemas.py --checkpytest -qNotes
report.json.release_decision.decisionremains the only merge/release gate. Preflight remains a routing/projection surface and does not emit a competing pass/mergeable verdict.