run: --flows is ignored, all 8 flows always execute (causes launch-phase timeouts)

[igoramf]

Version

@decocms/parity@0.29.1, run via npx

Repro command

parity run --prod https://www.montecarlo.com.br/ --cand https://montecarlo-tanstack.deco.site/ --profile commerce --flows plp --viewports mobile --no-auto-selectors

Expected behavior

Only the plp flow should run.

Actual behavior

The resulting report.json lists flows [plp, purchase-journey, search, cart-interactions, login, pdp, spa-navigation, homepage] — the full set. Tried --viewports mobile and --max-viewport-concurrency 1, neither reduced the flow count.

Impact

With all 8 flows launching in parallel, the run reliably times out in the "launch" phase (30-min and 15-min budgets both exhausted). The result is a misleading partial: true report showing verdict.score: 100 / status: pass with zero checks executed.

Note: A partial run should never emit a passing score (100/pass is contradictory).

Workaround observed

--flows homepage and the smoke preset DO complete, isolating the bug to flow filtering logic.

Two asks

1. Make --flows flag actually filter which flows execute
2. Never emit score 100/pass when partial is true