v0.10.0 — Edge-cached browse

Changed

• client:browse(...), client:sfxBrowse(...), and client:getSfxTaxonomy() now hit the API over GET instead of POST. Public method signatures, options, and return shapes are unchanged — but responses are now eligible for CloudFront edge caching, so identical calls served from a nearby edge return in ~30 ms anywhere globally instead of round-tripping to us-east-2 every time.
• Cache keys are scoped per-API-key, so customers stay isolated.
• TTL at the edge is 5 min default / 1 hour ceiling. Trending lists and canonical-genre drill-downs are invalidated automatically when the underlying refresh jobs run, so changes surface within seconds rather than waiting on TTL expiry.

Compatibility

• No code changes required. Bump your Wally pin to 0.10.0 and everything keeps working — same options, same return shapes.
• The API still accepts the equivalent POST for SDK <0.10.0 clients, so mixed-version game servers won't break during a gradual rollout.

Internal

• New requestGet() helper alongside request() (POST). Asymmetric naming is intentional and isolated; the two will fold into a single method-aware helper at v1.0.0.