TypeScript `Router.fetchEventMatches` missing `query` and `category` params present in Python

[realfishsam]

Drift

Python Router.fetch_event_matches accepts query and category parameters. The TypeScript Router.fetchEventMatches overload signatures do not include these parameters.

TypeScript SDK

sdks/typescript/pmxt/router.ts, lines 217–225:

async fetchEventMatches(params?: {
    event?: UnifiedEvent;
    eventId?: string;
    slug?: string;
    relation?: MatchRelation;
    minConfidence?: number;
    limit?: number;
    includePrices?: boolean;
    // query    — missing
    // category — missing
}): Promise<EventMatchResult[]>

Python SDK

sdks/python/pmxt/router.py, lines 189–199:

def fetch_event_matches(
    self,
    event: Optional[UnifiedEvent] = None,
    *,
    event_id: Optional[str] = None,
    slug: Optional[str] = None,
    query: Optional[str] = None,      # ← only in Python
    category: Optional[str] = None,   # ← only in Python
    relation: Optional[MatchRelation] = None,
    min_confidence: Optional[float] = None,
    limit: Optional[int] = None,
    include_prices: bool = False,
) -> List[EventMatchResult]:

Expected

TypeScript Router.fetchEventMatches should add query?: string and category?: string to its params object.

Impact

Python users can browse cross-venue event matches by free-text or category. TypeScript users cannot pass these parameters through the typed interface, meaning they silently fail to filter results that Python users can filter.

---

Found by automated SDK cross-language drift audit