Description

• Closes test.tags options doesn't overwrite inherited suite options #10199
• Closes fix(runner): tag options should override inherited suite options #10203 (supersedes)

I was reviewing #10203 and it looks like grabbing collectorContext.currentSuite?.options seems like a right fix. Here is why:

This fixes suite option merging during test collection. Tests now merge options in the intended priority order:

inherited suite options < then tag-derived options < explicit task options.

This ensures tag options can override inherited suite defaults while still allowing the test’s own options to win.

By using collectorContext.currentSuite?.options inside task function, this also makes the advanced raw task API consistent with normal test() collection: tasks registered through TestRunner.getCurrentSuite().task(...) now inherit options from the current suite. This matches the documented custom task collector behavior that should act like a test collector. Notably some properties are already inherited based on context such as task.meta.

A regression test was added for custom task collectors using the raw task API to verify inherited concurrent, repeats, retry, and timeout options.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.