update-docslisted

<!-- requires: none --> <!-- chains: none --> <!-- generated from .ai/workflows/update-docs.md; do not edit directly --> > **Codex:** this skill is the `/update-docs` adapter. Use Codex role agents from `.codex/agents/` when the runtime exposes them; otherwise perform the work directly and keep the same structured output. Update documentation to reflect recent work. Steps: 1. **Review recent changes**: Run `git log --oneline -5` and `git diff HEAD~5..HEAD --name-only` to understand what was built. 2. **Update CLAUDE.md** (project root): - Add any new architecture decisions, patterns, or constraints discovered during the work - Remove patterns that are now obsolete - Keep CLAUDE.md under ~300 lines — trim verbose sections if needed 3. **Record changelog entries**: - If `changelog.d/` exists, write one fragment per change: `changelog.d/<issue-or-slug>.<added|changed|fixed|removed>.md`, containing the entry body without the leading `- `. Never edit CHANGELOG.md directly — it is assembled at release by `scripts/collect-changelog.sh <version>`. - Otherwise update **CHANGELOG.md** (create it with a `# Changelog` title and `## Unreleased` section if the project has none): ``` ## Unreleased ### Added / Changed / Fixed - <concise description of what shipped> ``` Use `###` for category headings — one per category, do not duplicate. - Reference issue/PR numbers where applicable 4. **Update README.md** only if a public-facing feature