Module bind 

Step binding (TECH-SPEC §4.3): match each authored step against the loaded macros’ match: patterns.

Exactly one pattern must match: zero is an unbound step (with a closest-pattern suggestion), two or more is ambiguity (listing candidates). Captured {name} values, | key | value | data-table rows, and macro defaults fill the macro’s params; conflicts and missing required params are bind-time errors anchored to the step’s line.

Structs

BoundScenario

One scenario with every step bound.

BoundStep

One step bound to a macro with fully-assembled args.

Functions

bind

Bind every scenario of a feature. Diagnostics accumulate across steps and scenarios so authors see all problems in one run.

bind_collect

Bind every scenario, always returning both the bound scenarios (bound steps only) and every diagnostic. This is the collect-all substrate the LSP reads; bind is its fail-fast wrapper. One binder, two error policies.