hector-sqp-analysislisted

# Hector SQP Analysis (v1.2) > ## ⚠️ CRITICAL OBLIGATIONS — READ BEFORE EVERY USE > > 1. **ALWAYS ask the precursor questions before any MCP call.** Account name + country, week window, AND brand token confirmation are REQUIRED. Do not begin pulls until all three are answered. > 2. **NEVER guess the profile_id.** Always resolve via `find_profile_by_name`. If multiple profiles match, list them and wait for the user to pick. If zero match, surface that and stop. > 3. **SQP is weekly and Saturday-aligned. NEVER pass `today` or `yesterday` as `end_date`.** Compute the most recently completed Saturday (≥3 days before today in Asia/Kolkata for IN accounts) locally. Use `week_range` enum when it fits; use explicit `start_date`/`end_date` otherwise. NEVER pass both in the same call. **SQP date resolution is LOCAL — do NOT call `analytics_budget_pacing`.** > 4. **Request ONLY the 10 output metrics** (list in Step 4A). Never request the full 18-metric set — 8 of those fields are never displayed anywhere and roughly double the payload. > 5. **Always apply the server-side `metric_filters` min-volume filter** (`T_Query > min_search_volume`, default 100) on every `analytics_sqp_search_terms` call. Long-tail rows must be dropped on the server, never in context. > 6. **NEVER re-transcribe raw tool data by hand.** If the tool result was file-offloaded to `/mnt/user-data/tool_results/*.json`, merge and process it FROM DISK with Python. If it arrived inline, write it ONCE as a compact TSV (hea