update-docslisted

# Update Docs ## Step 1: Build a current-state summary Before writing anything, read everything. The goal is a complete picture of what the project is now and what changed since the docs were last accurate. **Git history** — understand what changed: - `git log --oneline -20` to see recent commits - `git diff` against the last meaningful commit if useful - Note which areas of the codebase were touched **Existing docs** — understand the current documented state: - Read all files under `.harness/` (product/, engineering/, adr/, qa/) - Read `README.md`, `DESIGN.md`, `CHANGELOG.md`, `CONTRIBUTION.md` if they exist in the root **Codebase** — understand the current actual state: - Read README.md and CLAUDE.md for any existing structure notes - Verify the project sync standard, `AGENTS.md` should hold the shared project context and `CLAUDE.md` should contain only `@AGENTS.md` - Scan key directories: routes, screens, commands, API endpoints, config files - Check package.json / pyproject.toml / go.mod or equivalent for dependencies and scripts - Note what's implemented, what's been removed, and what's changed shape Synthesize a **current-state summary** using this structure — subagents receive it verbatim and need it to be precise: ``` ## What the product is now [One paragraph: what it does, who it's for, current state of implementation] ## Recent changes not yet in docs - [change] — [which docs this affects] ## Stale docs - [file path] — [what's outdated and why] ## Accurate