notfair-weekly-review

# NotFair Weekly Review 1. Read `{baseDir}/../../shared/adapter-rules.md`. 2. Read `{baseDir}/../../shared/artifact-contract.md`. 3. Read `{baseDir}/../../shared/policy.md`. 4. Read `{baseDir}/../../shared/recommendation-quality.md`. 5. Read `{baseDir}/../../../seo/shared/seo-best-practices.md` and use its MECE lanes to explain why the top action is the right kind of SEO work. 6. Resolve the target `site_id`; if no site was specified and multiple sites are active, run portfolio review first or ask the user which site to review. 7. Read and follow the canonical NotFair skill at `{baseDir}/../../../seo/seo-analysis/SKILL.md`. 8. Prefer the automated runner: - `python3 {baseDir}/../../bin/weekly_review.py <site_id-or-url>` - add `--gsc-property` if the site profile does not already contain one - add `--analysis-file` when testing against a saved GSC analysis JSON fixture 9. The runner will generate and persist the review artifacts automatically, including automatic deep-dive diagnostics for the top CTR/snippet/content opportunity when applicable. 10. Verify that the run wrote `audit.json`, `action-plan.json`, and `verification.json`, refreshed `latest-state.json`, and created queue items. The top proposal should include `best_practice_alignment` plus `deep_dive` with SERP, current snippet, above-the-fold, and zero-click checks before approval. 11. If runner stdout includes `user_message`, use it as the user-facing summary. If it includes `business_context_request`, exp...