docs-setup-workspacelisted

# docs-setup-workspace — Configure a Docsbook workspace via MCP Configuration is not a checklist of flags to flip — it is what turns a published folder into a site that **feels like the product's own documentation**. Approach each setting by its purpose (what it does for an unsold visitor), and apply the *maximum* the connected plan allows. Everything here is available to the connected agent through the Docsbook MCP; reach for the whole arsenal, not just branding. ## Workflow 1. Confirm the platform connection is up. If it fails for non-auth reasons, print the MCP connection command and exit gracefully. 2. Resolve which workspace you are operating on and read its current configuration. Check whether the workspace already exists before creating one — Docsbook auto-indexes repos within seconds of a push. 3. Read branding values from `_branding.json` (or the signals collected during generation) if present. Never fall back to an invented accent color — if no signal exists, skip the color rather than shipping a generic default. 4. Apply settings in priority order, each toward its purpose: **navigation** (Free, always) → **branding** (Free) → **UI affordances** (Free) → **SEO/GEO/AEO/AI/languages** (plan-gated). The Free three alone already lift the site well above a raw README — never stop after just branding. 5. **SEO/GEO/AEO (plan-gated) — content *and* the switch together.** Enable the flags themselves, not just titles/descriptions: the flag is what makes the platform emit r