Onboard once, then run on autopilot

Use on first use, "get started", "track my website/brand", or when adding a new project or site. Follow autopilot for when to ask and when to proceed, research-led intake, Apify access and projects and memory. The host LLM does the research, analysis and writing; the package supplies skills, not its own model, account or database.

1. Resume first. Read the project index. If this brand/site already has a project, do not onboard again: route to seo-growth-agent and continue from its memory. Ask "which project?" only when several saved projects plausibly match.
2. Ask once (turn 1). If Apify is not connected, start the browser sign-in yourself on the side (CLI apify login --method console, or the host's connector card) and mention it in one line. In the same short message ask only for brand, website and any keywords or questions that must be tracked — or "figure it out". Never ask for competitors, audience, market, device, panel size or report format; research and default them.
3. Research without asking. Inspect the site and market (intake): offering, audience, competitors, topics, 5–8 literal buyer questions, target pages and market/device defaults. Put the user's must-track keywords/questions first. Keep verified facts, inferences and user-supplied items labelled. Verify Apify access silently and read live Actor pricing plus credit status.
4. One plan card, one question (turn 2). Show the plan (brand/site, competitors, tracked questions × platforms, target pages, monthly growth scan, report location) with cost per run and per month for Weekly (recommended) / Daily / Hourly pulse / On demand, and ask "How often should I track this?". Flag any option that exceeds remaining credits. The answer is the standing approval for that plan and its caps; record it once against the plan revision.
5. Then do everything, no more questions. Run the baseline (ai-visibility-tracker), generate the dashboard with charts, produce the top recommendations with implementation steps (visibility-action-plan), configure and verify the schedule for the chosen frequency (scheduled-visibility-tracking), and save the project memory (portfolio.json, context.md, handoff.md, report).
6. Finish briefly: what was measured, the top 3 actions, next run with timezone, monthly cap, report location, and how to change frequency, pause, add a website or show the dashboard.

Validation stays on: give each project and site a stable safe ID; accept only public domains and same-domain HTTPS target URLs; exclude local/private addresses and credential-bearing URLs; budgets are finite nonnegative USD; a missing or zero cap permits no paid launch. If Apify is not connected yet, continue the research and show the plan with costs, and start the baseline as soon as access works — without re-asking the onboarding questions. If the host cannot schedule or store files, say so in one line and use on-demand tracking or a downloadable project export.