relewise-analyticslisted

# Relewise Analytics When `../../scripts/relewise-agent` exists relative to this file, resolve it to an absolute path and use that executable. Otherwise, use `relewise-agent` from `PATH`. Use `relewise-agent` for execution. Do not construct Agent Gateway URLs, send HTTP directly, or ask for a PAT in chat. Discover and validate each requested Dataset before analysis; never invent a Dataset ID or silently substitute another Dataset. ## Plan the analysis Clarify or choose a defensible inclusive date range and state it in the answer. Preserve the same period, currency, and filters when comparing Datasets unless the user asks otherwise. Select the narrowest operation that answers the question. Read [references/operation-selection.md](references/operation-selection.md) when choosing among search-analytics operations. Before a call: 1. Inspect the exact operation with `relewise-agent schema <operation-id>`. 2. Use `CoreGetDatasetMetadata` when language, currency, Data Keys, or Classification Values are unknown. 3. For Search Analytics, use `AnalyticsGetSearchFilterOptions` to discover conditional filter values rather than guessing them. 4. Put validated parameters and body values in the documented input envelope, then call the operation for each Dataset. Execute with `relewise-agent call <operation-id> --dataset <dataset-id> [--input <path>]`. All analytics operations are read-only. Avoid identical retries after `validation_error` or `api_error`; correct the request from th