Repository navigation
fix(rds): re-derive family ProjectedCoverage after cap, override and dedupe - #2287
Conversation
|
Warning Review limit reached
This review includes 6 billable files and costs up to $1.50.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 20 minutes for your next included review. View limit details
Comment |
…dedupe --target-coverage sizes RDS recs by family normalized units and writes a family-wide ProjectedCoverage. --max-instances, --count-override and the duplicate-RI check then change Count, leaving that value stale. Call RederiveFamilyCoverage once on the final set in scoreLimitAndDisplay, only for --target-coverage runs (the legacy --coverage path writes a per-pool value it would overwrite) and never on the CSV path (no coverage map). Closes #2214 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gate note (claude-cc-libs)Rebased onto main after #2286 merged. The only conflict was CHANGELOG.md, resolved by keeping both entries. Excluding CHANGELOG.md, |
57960c1 to
1065362
Compare
Merge gate verdict (claude-cc-libs)Every gate holds at head 1065362:
CodeRabbit is waived as a merge gate under the 2026-10-19 decision. Squash-merging. |
Summary
Re-derives family ProjectedCoverage after cap, override and dedupe for RDS. Single commit of about 105 lines, replacing two commits where the first carried a stray backup file.
Supersedes the stacked branch fix/2214-rederive-rds-coverage, now that its base (#2284) is squash-merged.
Verification
go vet, go test -count=1 ./..., golangci-lint and scripts/test-git-secrets-allowlist.sh all pass.
Closes #2214
🤖 Generated with Claude Code