Currently, there is a risk that merging new PRs will create a silent regressions in our test collection logic. We need an automated gatekeeper to detect these discrepancies before they reach the main branch.

The goal of this spike is to thoroughly investigate the problem and design a CI check/GitHub Action solution that captures these issues.

Action Items

1. Investigation & Prototype: Investigate how to implement a CI check that triggers on every PR, iterates over all lanes using a --collect-only flag, and strictly verifies that the collected fixtures are accurate to the markers defined on each lane.

1. Team Alignment: The final proposed solution must be reviewed and accepted by the team.