AmbiguousStepDefinitionsException and Regex Overlap Limits

Cucumber-JVM maps Gherkin steps to Java methods using Cucumber Expressions or regular expressions. When a single step matches multiple definitions, the framework triggers an AmbiguousStepDefinitionsException to prevent non-deterministic execution.

Currently, the framework lacks a native priority or weighting mechanism to designate a primary match when overlapping patterns are intentional or necessary for generic step handling. This requires all step definitions to be mutually exclusive, which can become complex in large-scale test suites with highly generic patterns.

What are the recommended strategies for managing overlapping regular expressions without creating excessive redundancy in the step definition layer? Is there a documented way to implement a priority system for step resolution?