regression-detection

Detect Pact 5 regressions by running full test suites against migrated schemas to identify interface drift and cross-module impact. The workflow validates schema migrations, interface changes, and deployment order to ensure module boundaries remain intact.

Interface drift in Pact 5 modules occurs when schema migrations or deploy order changes alter module boundaries. The detection workflow identifies this drift by validating cross-module calls and verifying deployment order consistency after applying interface modifications.

Verify cross-module call integrity and gas usage by deploying Pact 5 modules in production order and running end-to-end validation. The workflow measures gas consumption and validates cross-module calls to detect regressions after interface or schema changes.

Check deploy order consistency for Pact 5 modules by running the regression detection workflow, which deploys modules in production order and validates cross-module dependencies. This ensures deployment sequence integrity before releasing schema or interface changes.

Document Pact 5 regressions for Admin review by using the structured checklist provided by the workflow, which reproduces and records regressions found across schema migrations, interface drift, cross-module changes, and deploy order modifications.

Cross-module test suites fail after interface changes due to regressions in Pact 5 module boundaries. The detection workflow identifies these regressions by running full test suites and validating cross-module calls, exposing interface drift caused by schema or deployment modifications.