docs(size-analysis): Clarify wildcard filter matching

Document that matches and notMatches values use Sentry wildcard pattern syntax while simple operators expose decoded literal values.

Refs EME-1061

Co-Authored-By: OpenAI Codex <noreply@openai.com>

Author: cameroncooke

docs/product/size-analysis/integrating-into-ci.mdx

@@ -237,9 +237,10 @@ Filter matching:
 - Objects in `filters` are combined with AND
 - Multiple `conditions` inside one filter are combined with OR
 - Each condition uses `values`; single-value operators still return a one-item array
-- Values in `filters` are decoded literal values, not query syntax. For example, `app_id:\*com` in `filterQuery` becomes `values: ["*com"]` with `operator: "equals"`
+- Values in `filters` are decoded literal values for exact/simple operators, not query syntax. For example, `app_id:\*com` in `filterQuery` becomes `values: ["*com"]` with `operator: "equals"`
 - The same key can appear in more than one filter object when positive and negative conditions both exist; those filter objects are still combined with AND
 - Supported filter operators are `equals`, `notEquals`, `in`, `notIn`, `contains`, `notContains`, `startsWith`, `notStartsWith`, `endsWith`, `notEndsWith`, `matches`, and `notMatches`
+- `matches` and `notMatches` values use Sentry wildcard pattern syntax. `*` matches zero or more characters, escaped `\*` matches a literal asterisk, and a pattern without `*` is an exact match. Simple wildcard patterns may be simplified to `startsWith`, `endsWith`, or `contains` instead.
 - `in` and `notIn` are evaluated as one condition against all values, matching Sentry's status check trigger behavior
 - A rule applies only when the build metadata matches all filters; if a referenced metadata key is missing, the filter does not match, even for negated operators