Unify Pitot adapter verification under one supervisor - #108
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.
What changed
Pitot E2EworkflowWhy
Kimi demonstrated a boundary gap: a supported adapter could pass source tests while remaining absent from GitHub Actions, the PR report, and README status. The old system maintained separate allowlists with no invariant joining them.
The new supervisor requires the set of built-in adapters to equal the set receiving scripts, Ubuntu/macOS/Windows execution, report rows, and public visibility.
Trust boundary
The privileged
workflow_runreporter continues executing frommain. The PR workflow uploads a bounded, strictly validated data-only adapter inventory, allowing future adapters to appear in their first PR report without executing untrusted PR code.Verification
python3 labs/15-pitot/scripts/pitot_adapter_supervisor.py checkGOWORK=off go test ./...Rollout note
This is the one-time bootstrap of the stable unified workflow and reporter trigger. The new matrix runs on this PR, while the new
workflow_runreporter becomes the default-branch reporter after merge. Future adapter PRs then receive their report row on the first run.