What problem does it solve? Verifying that a migrated page behaves identically to its legacy counterpart requires running end-to-end scenarios against both applications, which is error-prone to coordinate manually. This Skill acts as the functional gatekeeper between verification and route flip, ensuring no page goes live without passing E2E parity checks. ## Core Features & Use Cases - Playwright E2E Gate: Launches an e2e-test-runner sub-agent that realizes planned scenarios from the migration plan, including MSW-mocked and staging-gateway transactional flows. - Legacy Dual-Run Parity: Runs scenarios against both the legacy app and the migrated app to confirm behavior parity before any route flip. - Gate Evidence Accounting: Records tamper-aware evidence (commit SHA plus tree hash over watched paths) in tracker.json, detecting concurrent file changes during the run. - Use Case: After fm-verify marks a migrated hotel booking page as verified, run this gate to execute the planned E2E scenarios against both the legacy and new apps, then record a pass that unblocks the parity and route-flip stages. ## Quick Start Run the fm-e2e gate on the migrated checkout page with the pc app profile to execute its Playwright scenarios and record the gate result.