Summary of the test map: project/class/method counts, class-kind breakdown, endpoints, and edge tallies.

Blast radius of a change: the test scenarios affected by changing a class, method, step definition, or endpoint. Returns the affected scenarios (feature + the connecting step text), plus step-definition and feature counts.

Full-text search over step definitions (expression text + method + class name). Returns matching step definitions. Use this instead of grepping binding classes.

Find the tests for a topic: full-text search over scenarios (feature name + scenario name + step text + tags). Returns matching scenarios with feature and file:line. Use this instead of grepping .feature files when asked to find, list or count tests.

The HTTP endpoints/operations the suite calls, each with verb, route (real path when known), and its scenario blast radius. Highest-reach first.

Resolve a Gherkin step phrase to the EXISTING step definition(s) that would bind it — the same way the runner does (regex/cucumber expression, keyword-agnostic). Use this BEFORE writing a new step so an agent reuses what already exists instead of authoring a duplicate. status is 'exact' (one binding — reuse it), 'ambiguous' (several match — a conflict to resolve), or 'none' (nothing binds — returns existing step definitions ranked by shared terms, to adapt rather than duplicate). Each match returns the expression, the C# class/method, the method parameters, the argument values captured from the phrase, and file:line.

Full detail of scenario(s) whose name contains the given text: feature, tags, kind, example-row count, file:line, and the ordered steps (keyword + text + doc-string/data-table flags). Use to read an existing scenario before writing a similar one.

Full detail of step definition(s) whose expression contains the given text: keyword, expression kind, method parameters, C# class/method/signature, file:line, and the scenarios that currently use it (usage count). Use to inspect a step before reusing or changing it.

The tag taxonomy across the suite — every scenario tag (e.g. @smoke, @regression, ticket ids) with the number of scenarios carrying it, most-used first. Use to tag new scenarios consistently with what already exists.

The reusable step vocabulary: step definitions with their placeholders and (best-effort) allowed values pulled from the expression — cucumber {int}/{string}/{word}, regex alternations like (Auto|Allianz) as enum values, other groups as free parameters. Use to compose new scenarios from steps and values that already exist. Optional keyword/query filters.

The project dependency graph the suite implies: for each project, which projects it depends on and which depend on it, derived from cross-project binds_to/uses_type/inherits edges (edge counts as weight). Answers e.g. "what depends on the Party project?". Optional 'project' name filter.