NATS '>' wildcard case sensitivity across '/'-delimited subjects

NATS subject-based routing uses '*' and ' wildcards to filter messages across /-delimited subject trees. The '>' wildcard matches any number of tokens after its position, and the specification states that matching is case‑sensitive (e.g., com.> does not match COM.>).

In bridged or multi‑tenant deployments, operators sometimes report that '>' subscriptions deliver messages whose subject tokens differ in case, suggesting a possible deviation from the documented behavior. This uncertainty affects access‑control policies, subject quotas, and bridge subject mapping designs.

The goal is to pinpoint the exact matching boundary for '>' wildcards when subject tokens vary in case and to determine whether server version, JetStream configuration, or bridge hops influence the outcome.

Does '>' matching enforce case sensitivity uniformly across NATS server versions and bridge hops? Is there a server‑level configuration to normalize subject case for wildcard evaluation? How do JetStream streams interact with case‑variant wildcard subscriptions?