Implemented database models and migration for tracking architecture violations in the admin dashboard. This is the foundation for the code quality UI. Database Models Added (app/models/architecture_scan.py): - ArchitectureScan: Tracks validator runs with statistics - ArchitectureViolation: Individual violations with status tracking - ArchitectureRule: Rule configuration with enable/disable support - ViolationAssignment: Assign violations to developers - ViolationComment: Collaboration on violations Schema Features: - Full violation history tracking - Status workflow (open → assigned → resolved/ignored/technical_debt) - Assignment and due date tracking - Comments for collaboration - Rule management (enable/disable, severity override) - Scan statistics (errors, warnings, duration) Migration: - Created 5 tables with proper indexes and foreign keys - SQLite-compatible datetime defaults - Supports relationships between scans, violations, users Next Steps (Remaining Phases): - Phase 2: Service layer (code_quality_service.py) - Phase 3: API endpoints (/admin/code-quality/*) - Phase 4: Frontend dashboard and UI Benefits: - Track technical debt over time - Assign violations to developers - Prioritize fixes by severity - Measure code quality improvements - Collaborative violation resolution 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Generic single-database configuration.