Inconsistent Matching Behavior Between `(feature/**|feature*)` and `(feature*|feature/**)` for `feature/test/test`

Issue Description:

The regular expressions (feature/**|feature*) and (feature*|feature/**) yield inconsistent results when matching the string feature/test/test. Specifically:

1. (feature/**|feature*) does not match feature/test/test.
2. (feature*|feature/**) does match feature/test/test.

This behavior seems unexpected, as both expressions appear to be logically similar. Could you please clarify why this inconsistency occurs and provide guidance on the correct usage of these patterns?

Steps to Reproduce:

1. Use the regular expression (feature/**|feature*) to match the string feature/test/test.
2. Use the regular expression (feature*|feature/**) to match the same string.

Expected Result:
Both expressions should either match or not match the string consistently.

Actual Result:
The first expression does not match, while the second one does.

Additional Context:
This issue might be related to the order of patterns in the alternation (|) or the interpretation of the * and /** operators. Any insights or documentation on this behavior would be greatly appreciated.

Thank you!

The issue names no files, tests, or entry points. Start by reproducing both patterns against feature/test/test using the project's public matching interface, then identify where pattern-order and glob-operator behavior is documented. Done means explaining the differing results and documenting the correct usage or expected semantics.