deep-reviewlisted

# Deep Review — 14-Lens Iterative Methodology Apply 14 sequential lenses to the target artifact. Each lens examines the work from a different angle. Continue until a full round produces ZERO new findings. ## Rules 1. State which lens you are applying at the start of each round 2. Run specific checks for that lens — use code tools (grep, find) if available, otherwise reason systematically through each item 3. Document every finding with specific references (file:line if code, section name if document) 4. Flag CRITICAL/ship-stopper issues immediately — do not wait until all lenses are done 5. Save findings after every round 6. Stop ONLY when a complete round finds zero new findings ## The 14 Lenses ### Lens 1: File / Section Completeness Does the artifact cover every relevant file, feature, section, or topic? Cross-reference against the actual codebase, spec, or requirements. Anything missing entirely? ### Lens 2: Function / Item-Level Audit For items that ARE covered — is each individual function, endpoint, component, or requirement actually addressed? Or just the file/section name listed without the details? ### Lens 3: Category Gaps Are entire CATEGORIES of concerns missing? For test plans: unit, integration, E2E, smoke, regression, performance, security, accessibility, cleanup, config. For architecture reviews: scalability, monitoring, disaster recovery. For code reviews: correctness, security, robustness, maintainability. ### Lens 4: Cleanup, Performance, and Resou