regression-check

To verify past hardening actions and catch regressions early, run static analysis on tests, branded types, and error boundaries to produce evidence-backed pass or fail reports. This validates that historical security measures remain effective without executing the full application.

Static regression analysis for error boundaries and tests is an invariant checking mechanism that enforces test specifications, branded type integrity, and boundary conditions. It detects drift from verified hardening actions by analyzing code structure and generating file and line level evidence reports.

To run regression checks on all resolved PMRs, invoke the regression check command to load target PMRs and perform static verification. You can filter the verification scope using the dash dash scope flag to target specific modules or limit the analysis to a single PMR.

Yes, static regression checking flags a needs ci run status when tests are modified during the analysis. This ensures that any changes to test specifications or error boundaries trigger continuous integration validation to maintain hardening integrity and prevent silent drift.

The best way to generate evidence-backed regression reports is to perform static analysis on resolved PMRs and output pass fail results with file and line evidence. This provides actionable drift detection data directly integrated into PMR regression reporting workflows.

Yes, you can scope regression verification to a specific module or single PMR by applying scope-based filtering. This limits the static analysis of test specs, types, and error boundaries to the defined boundaries, generating targeted pass fail evidence without checking unrelated code.