Add concurrentRunners property to configuration schema for parallel execution

[Copilot]

This PR adds the concurrentRunners property to the config_v3.schema.json to support parallel test execution configuration.

Changes Made

• Added concurrentRunners property to the configuration schema with the following validation rules:

  • Accepts integer values ≥ 1 for specifying exact number of runners
  • Accepts boolean true to use CPU core count (capped at 4)
  • Rejects boolean false and invalid values (0, negative numbers, strings, etc.)
  • Defaults to 1 when property is omitted

• Added validation examples covering valid usage patterns:

  • { "concurrentRunners": 1 } - explicit single runner
  • { "concurrentRunners": true } - auto-detect CPU cores
  • { "concurrentRunners": 4 } - multiple runners

Schema Definition

{
  "concurrentRunners": {
    "type": ["integer", "boolean"],
    "default": 1,
    "minimum": 1,
    "description": "Number of concurrent test runners. Set to true to use CPU core count (capped at 4).",
    "not": {
      "const": false
    }
  }
}

Validation Results

All acceptance criteria have been verified:

• ✅ Schema accepts "concurrentRunners": 1
• ✅ Schema accepts "concurrentRunners": true
• ✅ Schema accepts "concurrentRunners": 8 (any integer ≥ 1)
• ✅ Schema rejects "concurrentRunners": 0
• ✅ Schema rejects "concurrentRunners": -1
• ✅ Schema rejects "concurrentRunners": false
• ✅ Schema rejects "concurrentRunners": "invalid"
• ✅ Default value is 1 when property omitted

The implementation follows existing schema patterns and maintains backward compatibility. All existing tests continue to pass (258 total tests).

Fixes #123.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[promptless]

📝 Documentation updates detected!

New suggestion: Add concurrentRunners configuration property documentation