hoo-weeklylisted

# Weekly check Resolve the brain: use registry.get_active() when running interactively; scheduled runs receive the brain path from the routine configuration. 0. Run `core.contracts.check_schema(brain_path)` first. If not compatible, relay the action string and stop before any of the steps below. 1. Read profile. Launch analytics-reporting-chief and serp-ai-monitor agents (parallel) with the profile path. 2. Save their reports under runs/YYYYMMDD-weekly/ (01-analytics.md, 02-serp-ai.md, REPORT.md synthesis). 3. Append the week's headline observations as signals. Include the week-over-week `ai_referrals` trend read from the week's daily signal lines (the AI-surface list is maintained in hoo-daily's SKILL.md - quote it, never extend it here); days without an `ai_referrals` line are stated as gaps, never interpolated. A sustained rise on a single landing page (3 or more of the week's daily lines) feeds the citation tracker: name the page in REPORT.md so the next citation run checks whether a new AI citation explains the traffic. 3.5. Stage classification. Build rows from this run's GSC page/query pull (one dict per query: clicks, impressions, position, plus query and page where the pull has them) and call `core.stage.classify(rows)`: `PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c "..."` importing `core.stage`. The thresholds live in that module and are never restated here (see docs/INFORMATION-MAP.md in the repo). Record the re