website-project-init

# Website Project Init The first command for every new client website. Sets up credentials, scans the site, and produces a complete `projects/{slug}/` archive that all subsequent `/article` / `/audit` / `/refresh` commands inherit from. ## Mandatory ordering **STEP 0 (CRITICAL) — Setup Wizard FIRST** Before ANY web crawling or analysis happens, run the setup wizard to ensure we have all credentials and brand context. The wizard is non-negotiable because: - /init Stage 1 needs Tavily key - /init Stage 7 (GEO baseline) needs Anthropic for AI probe - Image gen later needs OpenAI key - Publish later needs WordPress App Password - Image Art Direction needs brand colors Running scan first and discovering credentials missing later wastes the crawl + frustrates the user. So: ```python from scripts._core.setup_wizard import SetupWizard wiz = SetupWizard(site_slug, site_url) status = wiz.detect_existing() ``` Then for each `provider.found == False` and `provider.tier in (REQUIRED, RECOMMENDED, PUBLISH)`, ask the user via natural conversation: - Tier 1 (Anthropic, contact_email): HARD REQUIRED — halt /init if user refuses - Tier 2 (Tavily, OpenAI, Gemini): STRONGLY RECOMMENDED — warn but allow skip; explain what features unlock - Tier 3 (WordPress): REQUIRED ONLY IF user plans to publish via /publish; ask upfront so they don't get stuck later - Tier 4 (Brand config): RECOMMENDED — can be filled later via /context edit but image-gen + voice need this - Tier 5 ...