docslisted

You are running `/docs` in the **current working directory's repo**. Goal: author the three top-of-repo documentation files — `README.md`, `CLAUDE.md`, `mkdocs.yml` — or, where they exist, refresh them in place. Argument (optional): `$ARGUMENTS` — `readme`, `claude`, or `mkdocs` for just that file; `all` (or empty) for all three. **Refresh, don't clobber.** Existing prose, tables, and section order are authoritative. You may only: *replace* the generated badge block, *add* missing standard sections, and *correct* stale facts (wrong owner/repo, dead workflow name, changed template version). Never delete a hand-written section to standardise it — report it instead. Prefer `Edit` over `Write` on an existing file so the diff stays reviewable; `Write` is for scaffolding a file that isn't there. **Detect, never hardcode.** Every fact comes from this repo at runtime. Nothing about `jebel-quant/rhiza` is assumed. ## 1. Detect the repo's facts - **Root + cleanliness** — `git rev-parse --show-toplevel`, and note `git status --porcelain`. A dirty tree is fine (you're editing docs) but say what the user is mixing your changes with. - **Platform + `OWNER`/`REPO`** from `git remote get-url origin`: `github.com` → GitHub; a GitLab host → GitLab. No remote ⇒ ask, or scaffold with `OWNER`/`REPO` placeholders and flag them. - **Default branch + visibility** — one call, both platforms: ```bash uv run --python 3.12 --no-project python \ "${CLAUDE_PLUGIN_ROOT}/scripts/platfor