seo-orchestrator

# seo-orchestrator (Layer 2) Coordinates the whole audit in three phases: **detect → dispatch → synthesize**. The scripts are the acquisition layer; the model only judges. Read the compact stdout summaries and the JSON files they name — **never paste HTML into the conversation**. Nothing is written to the user's project; every artifact lives under `${CLAUDE_PLUGIN_DATA}/runs/<host>/<run-id>/`. ## 1. Detect — one call 1. Resolve the target and the flags forwarded by the command (`--pages`, `--max`, `--render`, `--ua`, `--vertical`, `--environment`, `--feed`, `--out`; default `--out "${CLAUDE_PLUGIN_DATA}/runs"`). 2. Run the whole deterministic pipeline **in one command**. `audit.mjs` acquires the target (it calls `crawl.mjs` for a URL, `snapshot.mjs` for `--pages 1` or a local path, and skips acquisition entirely when handed a run directory), writes `profile.json` (platform / framework / cms plugins / hosting / environment / capabilities / write_targets / `vertical_hints`, plus a vertical guess), runs the checks registry, and calls `report.mjs` for a first deterministic-only report: ```bash node "${CLAUDE_PLUGIN_ROOT}/scripts/audit.mjs" <url|path> \ --out "${CLAUDE_PLUGIN_DATA}/runs" --checks deterministic --format json \ [--pages N] [--max N] [--render static|auto|js] [--ua <preset>] \ [--vertical <ids>] [--environment production|preview|staging|local] [--feed <path>] ``` Read only the JSON summary it prints: `run_dir`, `mode`, `platform`, `vertical`, `coverage`, `...