Dry-run validation skipping plugin suite hooks during upgrade verification

Goal

Validate a Cucumber upgrade using --dry-run while confirming that plugin beforeSuite/afterSuite hooks — intended for migration rollback or configuration revert — are exercised during the verification pass.

Constraints and uncertainty

The --dry-run flag loads configuration and step definitions but avoids executing step bodies. Documentation does not explicitly state whether suite-level plugin hooks run during a dry run. If they are skipped, teams cannot verify that rollback logic embedded in those hooks will activate correctly when a real upgrade fails mid-run.

Questions

1. Does cucumber --dry-run invoke beforeSuite and afterSuite plugin hooks, or are they treated as side effects and omitted?
2. If suite hooks are skipped, what is the recommended pattern for validating rollback logic without executing the full scenario suite?