Repository navigation
Verify priority agents against complete installation identity - #74
Merged
Merged
Conversation
Pitot coding-agent E2EIntelligence Flow is the verification source; Pitot's public README carries the latest
Runtime capabilities
Source commit: |
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.
Change contract
When: CI verifies an installed Codex, Qwen or DeepSeek release.
Before: An unchanged launcher and version banner could conceal changes to delegated package code or the Node runtime.
After: Verification records the complete owned installation tree and selected Node binary, then invokes the recorded Node/JavaScript pair and rechecks identity around execution. Qwen's managed-update selection is pinned to the recorded package, with an unpinned positive control to validate the test.
Boundaries preserved
Evidence
Failure and recovery
Changed installation identity rejects verification. Failed probes retain bounded streams locally and publish only diagnostic metadata. A capture refresh must come from a complete successful workflow run for the reviewed source commit; partial or stale results cannot authorize it. Revert this PR to restore the previous verification contract.
Remaining limits
These are observations on trusted runners, not publisher authentication or an atomic filesystem snapshot. Windows ACLs, operating-system libraries and changes between observations remain outside the identity scope.