[ops]: harden trusted pilot routing outputs#2077
Open
svelderrainruiz wants to merge 2 commits into
Open
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
Out-File -Encoding utf8output writes withAdd-ContentfromJSON(...)Why
The direct operator proof on the mounted integration baseline showed that
workflow_dispatchreachedtrust-contextbut still admitted theskippedjob instead of thepilotjob. The integration proving rail also showed the additive pilot disappearing on the trusted PR surface even after mounting the evidence fix. This slice makes the routing contract observable and removes two likely sources of silent false negatives: path filtering and fragile string-based output handling.Evidence
node --test tools/priority/__tests__/pester-service-model-workflow-contract.test.mjsgit diff --check