feat: add sovereign-ci.yml reusable workflow (§2.1.1) - #1
Open
noahgift wants to merge 1 commit into
Open
Conversation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
noahgift
added a commit
that referenced
this pull request
Jun 25, 2026
…stem audit gap #1) The strongest quality signal (line coverage) was purely advisory: the coverage job runs `cargo llvm-cov` but never enforced a floor, and the codecov upload is continue-on-error. A coverage regression therefore merged SILENTLY despite the 95% / ZERO-tolerance rule. This adds two OPT-IN inputs to the fleet-shared reusable workflow: - coverage_min (default '') — line-coverage floor - coverage_baseline_file (default .pmat/coverage-baseline.txt) — ratchet baseline path When coverage_min is EMPTY (the default for all 72 non-pilot callers), a new `if: inputs.coverage_min != ''` guard SKIPS the enforcement step entirely — coverage stays exactly as advisory as before. Zero behavior change for every repo that does not opt in. When coverage_min is set, the new step derives line coverage from the just-produced lcov.info (no extra compile/test cost), computes an effective floor = max(coverage_min, committed baseline), and FAILS the coverage job on a drop below it. The coverage job result is already wired into the top-level `gate` (needs: [...coverage...]), so a regression now blocks merge. It is a RATCHET, not an absolute jump: a repo green today records its current % as the baseline, so enabling the gate can never break the currently-green state. Pilot: aprender only (paiml/aprender PR). NOT enabled fleet-wide. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
noahgift
added a commit
that referenced
this pull request
Jun 25, 2026
…stem audit gap #1) (#37) The strongest quality signal (line coverage) was purely advisory: the coverage job runs `cargo llvm-cov` but never enforced a floor, and the codecov upload is continue-on-error. A coverage regression therefore merged SILENTLY despite the 95% / ZERO-tolerance rule. This adds two OPT-IN inputs to the fleet-shared reusable workflow: - coverage_min (default '') — line-coverage floor - coverage_baseline_file (default .pmat/coverage-baseline.txt) — ratchet baseline path When coverage_min is EMPTY (the default for all 72 non-pilot callers), a new `if: inputs.coverage_min != ''` guard SKIPS the enforcement step entirely — coverage stays exactly as advisory as before. Zero behavior change for every repo that does not opt in. When coverage_min is set, the new step derives line coverage from the just-produced lcov.info (no extra compile/test cost), computes an effective floor = max(coverage_min, committed baseline), and FAILS the coverage job on a drop below it. The coverage job result is already wired into the top-level `gate` (needs: [...coverage...]), so a regression now blocks merge. It is a RATCHET, not an absolute jump: a repo green today records its current % as the baseline, so enabling the gate can never break the currently-green state. Pilot: aprender only (paiml/aprender PR). NOT enabled fleet-wide. Co-authored-by: Claude Opus 4.8 <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.
Single reusable workflow for all per-repo CI. Change once, applies to all 31 repos.