cli-parallel-tests

Parallel test execution for CLI repositories is handled by discovering canonical validation scripts from package.json and CI workflows, then coordinating separate test suites across workers when documented scripts allow it.

Repository-aware test discovery identifies canonical validation scripts by reading package.json, Turbo configuration, and CI workflows directly, ensuring only documented commands are executed rather than inventing ad hoc test commands.

Yes, the workflow aligns directly with your existing setup by reading package.json scripts and Turbo configuration to identify the correct package manager and documented validation commands to execute.

The best way to triage test failures is to capture the validation output and connect the failure results with technical analysis workflows, enabling structured debugging and follow-up analysis for the CLI codebase.

Worker coordination is required during parallel execution to manage separate test suites across workers safely, ensuring that documented scripts and authorizations permit parallel runs without conflicting.

The limitation is that CI-equivalent script execution strictly requires repository script discovery and package manager alignment; it cannot invent commands or run parallel workflows without explicit documented authorization.