generator-walk
A saga test that pins the order of yields instead of the outcome.
No decided findings.
Shown with --all. Never gates, even with an override.
Hidden by default
Its review dropped it: the open-source corpus has almost no tests of this shape.
It still runs: spirolo check --all shows its findings, labelled, and it never fails the build, even with an override.
What it reports
A redux-saga test steps the generator with .next() and asserts each yielded effect in sequence. It pins how the saga is written, not what it does, and breaks on a reorder that changes no behaviour.
What to do
Run the saga instead (expectSaga(saga).run(), one test per branch) and keep the effects it asserts. Do not delete the assertions.
spirolo explain generator-walk prints the same claim and status from your installed binary.