factcheck-docslisted

## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). It may specify which docs to check, specific areas of concern, or files to focus on. ## Purpose Deep factcheck of project documentation (README.md, CLAUDE.md, SVG diagrams, and skill/agent definitions) against the actual codebase. Finds inaccuracies, stale references, missing information, and bloat. Produces a report and then applies fixes. **Audience distinction:** - **README.md** is for humans setting up and using Rockport. It should explain what things do and how to use them. - **CLAUDE.md** is for Claude Code. It should document non-obvious gotchas, exact technical details, and things that would trip up an AI assistant working on the codebase. Don't duplicate what's readable from code. ## Phases ### Phase 1: Build ground truth from code Read ALL source-of-truth files listed in [sources.md](sources.md). Do not skip any. Use the Agent tool with subagent_type=Explore or parallel Read calls to maximise speed. ### Phase 2: Cross-reference and audit For each documentation file, check EVERY factual claim against the ground truth gathered in Phase 1. Be methodical — go line by line through each doc file. Use the checklists in [checklists.md](checklists.md). ### Phase 3: Report findings Present ALL findings in a table. Be exhaustive — every discrepancy matters. ``` | # | File | Location | Type | Description | Fix | |---|------|----------|------|-------------|---