Always provide comprehensive context for code reviews and testing

The user consistently provides extensive context when requesting code reviews or discussing testing. This includes: detailed file contents, specific line numbers, test results, implementation logic, design intent, and areas requiring special scrutiny. The user expects reviewers to have all necessary information to understand changes, identify edge cases, and verify correctness without needing to ask follow-up questions about context.