check-requirements-against-codelisted

Comprehensively compare the requirements documents in `docs/` against the actual implementation. Also verify that the AI summary docs (`docs/ai/code-summary.md`, `docs/ai/requirements-summary.md`) and `CLAUDE.md` are in sync with both the requirements docs and the code. Generate a report with recommendations and questions about any discrepancies. ## Steps 1. **Read all requirements documents** in `docs/`. Note every stated requirement, behavior, and constraint. This includes the numbered docs (1, 2, 3, …) plus `plugin-development-guide.md`, `tauri-architecture.md`, `tauri-setup.md`, and `manual-test-plan.md`. 2. **For each requirement**, verify it against the implementation: - Search the codebase for the relevant code - Check if the behavior matches what's documented - Note any differences, missing features, or extra features not in the docs 3. **Check for undocumented features**: Scan the codebase for significant functionality that isn't covered by any requirements document. These are features that should either be documented or questioned. 4. **Check for stale documentation**: Requirements that describe behavior that no longer exists or has changed. 5. **Verify `CLAUDE.md` completeness**: Double-check that every requirements doc under `docs/` (numbered docs + `plugin-development-guide.md`, `tauri-architecture.md`, `tauri-setup.md`) appears in CLAUDE.md's "Reading order" list. Report any docs present on disk but missing from CLAUDE.md, or listed in CLAUDE.md b