… steps in parallel mode as in sequential mode

With parallelMode, the step path only converted the Cucumber status:

- an undefined step was reported as passed, with no error
- an ambiguous step was skipped with no reason, and
  failAmbiguousDefinitions was ignored for steps
- a failed step had the whole Cucumber message as error message, so
  reporters showed `Error: Error: ...` and internal stack lines

The parallel step path now uses getStepResult(), as the sequential
formatter does, and lists the matching step definitions of an ambiguous
step from Cucumber's support code messages.

Real-browser check (Chrome, sequential vs parallel run of the same
specs): the spec, dot, concise, JUnit and JSON reporters now give the
same step results, also with ignoreUndefinedDefinitions and
failAmbiguousDefinitions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Parallel mode ran the scenarios in file order and ignored
cucumberOpts.order. It now orders them with Cucumber's own
orderPickles, as Cucumber does in a sequential run: `random:<seed>`
gives the same order as a sequential run, `random` logs its seed, and
an unknown order fails before any window opens.

Real-browser check (Chrome, 2 feature files, order random:7, 1 slot):
sequential and parallel runs start the scenarios in the same order.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…itle in parallel mode

In parallel mode a Before/After hook had an empty title. Sequential
mode titles it with the hook name and tag expression, for example
`@beforeFails`, which the spec reporter shows for a failing hook and
the JSON reporter writes as the hook title.

The hook titles now come from the same support code messages as the
step definitions.

Real-browser check (Chrome, sequential vs parallel run of the same
specs): the spec, dot, concise, JUnit and JSON reporters give the same
result.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…os in parallel mode as in sequential mode

With scenarioLevelReporter, the parallel scenario result kept its own
rules and collected an ambiguous step result before its message was
added:

- with failAmbiguousDefinitions, an ambiguous scenario failed with no
  error, and when skipped it had no pendingReason
- with ignoreUndefinedDefinitions, the scenario title had no
  ` (undefined step)` suffix
- the undefined scenario message had quotes and no scenario location

The scenario result now uses getStepResult(), as the sequential
formatter does, with the ambiguous message added first.

Real-browser check (Chrome, scenarioLevelReporter, also with
failAmbiguousDefinitions and ignoreUndefinedDefinitions): the spec,
dot, concise and JSON reporters give the same result in sequential and
parallel runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…rror that shows it

getStepResult() took the feature stack as a string, so every step
result scanned the feature children, also a passing step. It now takes
a function and calls it only for the undefined and ambiguous failures,
as the formatter did before the shared rule.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…n parallel mode

With tagsInTitle, a parallel feature suite had no tags in its title
(`Statuses in parallel` instead of `@feat: Statuses in parallel`), and
its start had no description and keyword. Reporters such as JUnit and
spec then named the feature differently than in a sequential run.

Real-browser check (Chrome, tagsInTitle, step and scenario level): the
JUnit testsuite names and the spec failure titles are the same as in a
sequential run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…stop as Cucumber does

After a failFast stop, parallel mode reported each scenario that did
not run as plain skipped steps. Cucumber runs these scenarios in skip
mode: their hooks are reported as skipped, an undefined step stays
failed, and an ambiguous step keeps its reason.

They now run through Cucumber's test case runner with `skip: true`,
with no window, so the reporters get the same events as in a
sequential run. The failFast tests use a defined failing step, because
in skip mode an undefined step stays failed.

Real-browser check (Chrome, failFast, step and scenario level, 2
slots): the spec, dot, concise, JUnit and JSON reporters and the
framework events are the same as in a sequential run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>