docs: clarify --pwc-batch-size vs --workers (ENG-775)

[maxigimenez]

Summary

Clarifies how --pwc-batch-size and --workers actually behave in Playwright orchestration, to remove the surprises reported in ENG-775:

• --pwc-batch-size is a count of parallel lanes, not a hard limit on spec files — with batch size >= 2 the orchestrator weight-packs the heaviest spec plus lighter ones, so a machine can claim more files than the batch size (1 claims exactly one).
• The orchestrator is machine-unaware, so an early/fast machine can over-claim and a late-joining machine can get nothing.
• How the two settings interact in file-level vs fully-parallel suites, and guidance for even distribution.

Files: guides/ci-optimization/playwright-orchestration.md, resources/reporters/currents-playwright/configuration.md, resources/reporters/currents-playwright/pwc-p-run.md.

Draft for team review of wording before publishing.

Made with Cursor

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5b5edc8f-89af-4671-bf9f-fc75cead4890

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch maxi/eng-775-docs-batch-size-workers

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}