Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

refactor(matchers): centralize the matcher-type set

The wire-addressable matcher-type set was re-encoded in several sites
(matcherTypeFromParam, filterFromVars, isKnownMatchType), and the per-value
matcher validation pipeline in another. Add a single knownMatcherType predicate
and a validateProtocolMatcher helper in matchertype.go and route those sites
through them, so the set of protocol matcher types is defined once. The per-type
dispatch in validatePattern and matchMatcher stays as the one place that
branches on type (adding a type still edits those two, which is the real
per-type work). No behavior change.