VERIFY MODE: Verification and Quality Assurance Process with Code Review

WARNING: DO NOT use the Task tool with any subagent_type (Explore, Plan, general-purpose). Perform ALL verification yourself using direct tool calls (Read, Grep, Glob, Bash, MCP tools). Sub-agents lose context and make verification inconsistent.

Available MCP Tools:

• Context7 - Library documentation lookup: resolve-library-id(query, libraryName) then query-docs(libraryId, query) - descriptive queries required (see context7-docs.md)
• mcp-cli - Custom MCP servers via mcp-cli <server>/<tool> '<json>' for servers in mcp_servers.json

The Process

Unit tests → Integration tests → Program execution (with log inspection) → Rules audit → Coverage → Quality → Code review → E2E tests → Final verification

All test levels are MANDATORY: Unit tests alone are insufficient. You must run integration tests AND E2E tests AND execute the actual program with real data.

Active verification with comprehensive code review that immediately fixes issues as discovered, ensuring all tests pass, code quality is high, and system works end-to-end.

Step 1: Run & Fix Unit Tests