release: 2.50.5 — 101 glossary: SDK accepts both ID forms (third stale instance)

Author: realfishsam

changelog.md

@@ -2,6 +2,12 @@
 
 All notable changes to this project will be documented in this file.
 
+## [2.50.5] - 2026-06-18
+
+### Docs
+
+- **`docs/concepts/prediction-markets-101.mdx`**: Fixed a third instance of the stale "hosted trading requires the catalog UUID" claim — the same lie that 2.50.3 fixed in `hosted-trading.mdx`. The 101 glossary still asserted catalog UUID was required for hosted trading and that venue-native IDs only came back from per-venue reads. The SDK has handled both forms since `_hosted_build_order_request` landed (`sdks/python/pmxt/client.py:764`): catalog UUIDs go on the wire as `outcome_id`, venue-native IDs go on as `(venue, venue_outcome_id)`. Reframed the paragraph to say the API accepts either and that the catalog UUID matters for cross-venue identity, not as a hosted-trading requirement. Missed by the strip pass because that pass operated by file ownership and the 101 page wasn't assigned to any of the three agents.
+
 ## [2.50.4] - 2026-06-18
 
 ### Docs

docs/concepts/prediction-markets-101.mdx

@@ -21,7 +21,7 @@ Outcome prices are in the closed interval [0, 1] and are read as the market's im
 
 ### Catalog UUID vs venue ID
 
-PMXT assigns its own stable UUID to every market and outcome. The underlying venue (Polymarket, Kalshi, etc.) also has its own native ID — a hex condition ID, a ticker, a hash. Hosted trading requires the catalog UUID. Per-venue read endpoints return venue-native IDs. See [Catalog UUID vs Venue ID](/concepts/catalog-uuid-vs-venue-id) for which surfaces use which.
+PMXT assigns its own stable UUID to every market and outcome. The underlying venue (Polymarket, Kalshi, etc.) also has its own native ID — a hex condition ID, a ticker, a hash. The hosted trading API accepts either — pass whatever your code already has; the SDK picks the right wire field. Cross-venue identity (Router results, portfolio analytics) is the place where the catalog UUID matters. See [Catalog UUID vs Venue ID](/concepts/catalog-uuid-vs-venue-id).
 
 ## Crypto / EVM terms (for the non-crypto reader)