Skip to content

fix(baseline): make pruning evidence-based and safe by default - #30

Merged
styayur merged 1 commit into
mainfrom
fix/baseline-prune-safety
Oct 19, 2026
Merged

styayur merged 1 commit into
mainfrom
fix/baseline-prune-safety

Conversation

@styayur

@styayur styayur commented Oct 19, 2026

Copy link
Copy Markdown
Owner

Summary

Makes baseline pruning evidence-based and safe by default.

  • baseline prune now re-evaluates current diagnostics rather than removing entries based only on a persisted lifecycle field.
  • Dry run is the default; --apply is required to write.
  • Reports inspected, removable, removed and retained counts plus per-entry rule/path/lifecycle details.
  • Refuses the entire write when structural/context matching is ambiguous, leaving the baseline unchanged.
  • Keeps --include-fixtures available for reviewed baselines containing fixture findings.
  • Adds unit coverage for dry-run behavior, explicit application, and ambiguity refusal.

Compatibility

  • Baseline schema remains version 1.
  • The command becomes safer: scripts that expected an implicit write must add --apply.
  • Ambiguous matching is now a hard refusal instead of an unsafe cleanup.

Verification

  • cargo fmt --all -- --check
  • cargo clippy --workspace --all-targets --all-features -- -D warnings
  • cargo test --workspace --lib --bins --tests
  • Release CLI manual dry-run and --apply round trip
  • Changed-file self-review with zero diagnostics

@styayur
styayur merged commit 4c73d37 into main Oct 19, 2026
7 checks passed
@styayur
styayur deleted the fix/baseline-prune-safety branch October 19, 2026 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant