Enforce the 80% Cobertura line-coverage gate - #551
Merged
Merged
Conversation
drmoisan
changed the title
drmoisan
force-pushed
the
bug/coverage-threshold-policy-reconciliation-494
branch
from
August 15, 2026 02:15
d5e4a99 to
36daf03
Compare
- Capture three corrected-arithmetic coverage runs with 6,435 tests passing in each run - Record the absent upstream release receipt and leave all ten acceptance criteria unresolved - Add policy, code, and feature audits with a scoped remediation plan Refs: #494
- Add canonical policy, code, and feature review artifacts - Capture prompt-contract and receipt-gate evidence for the absent upstream release validation receipt - Complete Phase 0 and Phase 1 checklist items and halt before receipt-dependent Phase 2 Refs: #494
- Establish spec.md acceptance criteria as the sole check-off source - Document local-only scope, protected-path classification, and historical scenarios - Record scoped validation evidence for the remediation plan Refs: #494
- Mark the approved zero-delta analyzer baseline as no-regression evidence - Record PASS readiness and defer exact-head CI as post-review work Refs: #494
drmoisan
force-pushed
the
bug/coverage-threshold-policy-reconciliation-494
branch
from
August 15, 2026 02:26
36daf03 to
b8b4b16
Compare
drmoisan
added a commit
that referenced
this pull request
Aug 15, 2026
docs(epic): refresh epic-status projection from git and gh Wave 2 closed: feature 494 merged via PR #551 (merge commit 85ff0c3) on 2026-08-15T02:27Z. The projection had it at worktree_created. Also corrects the "Issues Closed" claim. All nine issues are still open on GitHub because every child PR targeted the integration branch, and GitHub auto-closes only on merge into the default branch. Renamed the section to "Issues - Pending Closure" and recorded that the integration PR body carries the closing keywords. Records that the tree has moved past the last green workflow_dispatch run (31493339489 @ c7d398c): feature 494 and the main merge fb8eff9 (CI parallel job split #553/PR #556) are both uncovered by it, and the job split renamed the check runs. Regenerated from git and gh; artifacts/orchestration/epic-orchestrator-state.json is absent from this worktree and the commands are authoritative per the cache doctrine. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> @
drmoisan
added a commit
that referenced
this pull request
Aug 15, 2026
Wave 2 closed: feature 494 merged via PR #551 (merge commit 85ff0c3) on 2026-08-15T02:27Z. The projection had it at worktree_created. Also corrects the "Issues Closed" claim. All nine issues are still open on GitHub because every child PR targeted the integration branch, and GitHub auto-closes only on merge into the default branch. Renamed the section to "Issues - Pending Closure" and recorded that the integration PR body carries the closing keywords. Records that the tree has moved past the last green workflow_dispatch run (31493339489 @ c7d398c): feature 494 and the main merge fb8eff9 (CI parallel job split #553/PR #556) are both uncovered by it, and the job split renamed the check runs. Regenerated from git and gh; artifacts/orchestration/epic-orchestrator-state.json is absent from this worktree and the commands are authoritative per the cache doctrine. Co-Authored-By: Claude Opus 5 (1M context) <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.
Summary
Why
The repository had incompatible always-loaded coverage-policy surfaces and no enforced local boundary for Cobertura line coverage. This change establishes the required local 80% gate while preserving the upstream reconciliation work as a deferred, externally owned deliverable.
What Changed
Verification
31749877507ford5e4a99687f22ecf14b88a206db623d85fe9a97fsucceeded afterworkflow_dispatch, including actionlint and Format, build, analyze, and test.git diff --check; no TaskMasterCLAUDE.md, non-memory.claude/**, or.agents/skills/**runtime-policy path changed.Scope and Follow-up
The upstream coverage-policy reconciliation remains deferred; the retained prompt defines the future upstream deliverable without changing local runtime policy paths. Re-run workflow-dispatch CI for any later head commit.
GitHub Auto-close