Repository navigation
docs: define exact-head CI evidence policy - #97
Merged
Merged
Conversation
ORESoftware
added a commit
that referenced
this pull request
Sep 18, 2026
…12 (DEN-3945) Brings the sweep branch up to current origin/main (dec94c9..8771248, 6 commits: PRs #95, #97, #98, #99, #104). Conflict-free. Created with merge-tree/commit-tree plumbing because this repo tracks both AGENTS.md and agents.md, which collide on a case-insensitive macOS working tree; both blobs verified byte-identical to origin/main in the resulting tree. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
1 participant
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.
Codifies the fleet merge-evidence rules used by the current CI hardening work: exact PR-head identity, stepful execution, zero-step runner refusals as non-evidence, stale-SHA rejection, fail-closed security/reproducibility gates, expected-head merges, TJSV evidence for TypeSpec/JSON Schema peer authorities, and equivalent evidence requirements for trusted indie/local runners.
Documentation-only; no workflow or production behavior changes.