Remove `scope` field from RecommendationsFilterRequest
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The scope property has been removed from the RecommendationsFilterRequest schema. Clients that currently pass scope (e.g. "experiment" or "*") in their recommendations filter request body will no longer have this field recognized by the API, which may silently change behavior or cause validation errors depending on server-side handling.