add CLAUDE.md and fix stale README install command

Documents the uv-based workflow, mkdocstrings dependency on the sibling
taskbadger-python checkout via TB_PYTHON_SRC, and the auto-deploy on push
to main. Also corrects README to use `uv sync` instead of the stale
`pip install requirements.txt`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: snopoke

CLAUDE.md

@@ -0,0 +1,36 @@
+# Task Badger Docs
+
+Mkdocs-material documentation site for Task Badger. Published to https://docs.taskbadger.net.
+
+## Commands
+
+```bash
+uv sync                                # Install deps (use uv, not pip — README is stale)
+inv serve                              # Dev server on http://localhost:8082
+uv run mkdocs serve -a localhost:8082  # Equivalent without invoke
+uv run mkdocs build                    # Build static site to ./site/
+```
+
+## Architecture
+
+- Content: Markdown files in `docs/`
+- Config: `mkdocs.yml` (theme, nav, plugins, markdown extensions)
+- Tasks: `tasks.py` (invoke tasks)
+
+## Sibling repo dependency
+
+The Python SDK reference pages use `mkdocstrings` to pull docstrings from a sibling
+checkout of `taskbadger-python`. Path is set via `TB_PYTHON_SRC` (defaults to
+`../taskbadger-python`). Without it sitting next to this repo, SDK pages won't render
+properly. mkdocs also `watch:`es that path during `mkdocs serve`.
+
+## Navigation
+
+The site nav is controlled by the `nav:` block in `mkdocs.yml`, **not** by the
+filesystem. Adding a new `.md` file under `docs/` doesn't make it appear in the
+sidebar — add it to `nav:` too.
+
+## Deployment
+
+Push to `main` triggers `.github/workflows/deploy.yml`, which runs
+`uv run mkdocs gh-deploy --force`. There is no staging — main goes live.

README.md

@@ -4,7 +4,7 @@ See https://docs.taskbadger.net
 
 ## Setup
 
-```python
-pip install requirements.txt
+```bash
+uv sync
 inv serve
 ```