check-requirements-against-code

Check the requirements documents against the actual implementation, verify the AI-oriented summaries still match reality, and confirm the CLAUDE.md index is complete. Generate a report with recommendations and questions about any discrepancies. ## Process 1. **Read all requirements documents** in `docs/` (numbered files like `1-review-workflow.md` through `17-claude-channel.md`). Each contains functional (FR-) and non-functional (NFR-) requirements. 2. **For each requirement**, verify the implementation exists: - Search the codebase (`src/`) for the relevant code - Check that the behavior described in the requirement is actually implemented - Note any partial implementations or deviations from the spec 3. **Check for undocumented features**: Look for significant functionality in the code that isn't covered by any requirement. These may be intentional additions that need documentation, or accidental scope creep. 4. **Synchronize the AI summaries** (`docs/ai/code-summary.md` and `docs/ai/requirements-summary.md`): - Open both files and verify they reflect the current state of the tree. - For `code-summary.md`: walk through each section and confirm it matches what's actually in `src/`, `src-tauri/`, `scripts/`, and the database schema. Look specifically for: - Files/folders listed that no longer exist - Files/folders in the tree that aren't mentioned - Routes in the catalog that no longer exist (or new ones missing) - Database tables/colum...