aa6f7ec947
Implemented complete cross-switching system with database persistence and audit logging: **Tests:** - Contract tests for POST /api/v1/crossswitch (execute cross-switch) - Contract tests for POST /api/v1/crossswitch/clear (clear monitor) - Contract tests for GET /api/v1/crossswitch/routing (routing state) - Contract tests for GET /api/v1/crossswitch/history (routing history) - Integration tests for complete cross-switch workflow - RBAC tests (operator required for execution, viewer for reading) **Database:** - CrossSwitchRoute model with full routing history tracking - Fields: camera_id, monitor_id, mode, executed_at, executed_by, is_active - Cleared route tracking: cleared_at, cleared_by - SDK response tracking: sdk_success, sdk_error - JSONB details field for camera/monitor names - Comprehensive indexes for performance **Migration:** - 20251209_crossswitch_routes: Creates crossswitch_routes table - Foreign keys to users table for executed_by and cleared_by - Indexes: active routes, camera history, monitor history, user routes **Schemas:** - CrossSwitchRequest: camera_id, monitor_id, mode validation - ClearMonitorRequest: monitor_id validation - RouteInfo: Complete route information with user details - CrossSwitchResponse, ClearMonitorResponse, RoutingStateResponse - RouteHistoryResponse: Pagination support **Services:** - CrossSwitchService: Complete cross-switching logic - execute_crossswitch(): Route camera to monitor via SDK Bridge - clear_monitor(): Remove camera from monitor - get_routing_state(): Get active routes - get_routing_history(): Get historical routes with pagination - Automatic route clearing when new camera assigned to monitor - Cache invalidation after routing changes - Integrated audit logging for all operations **Router Endpoints:** - POST /api/v1/crossswitch - Execute cross-switch (Operator+) - POST /api/v1/crossswitch/clear - Clear monitor (Operator+) - GET /api/v1/crossswitch/routing - Get routing state (Viewer+) - GET /api/v1/crossswitch/history - Get routing history (Viewer+) **RBAC:** - Operator role or higher required for execution (crossswitch, clear) - Viewer role can read routing state and history - Administrator has all permissions **Audit Logging:** - All cross-switch operations logged to audit_logs table - Tracks: user, IP address, camera/monitor IDs, success/failure - SDK errors captured in both audit log and route record **Integration:** - Registered crossswitch router in main.py - SDK Bridge integration for hardware control - Redis cache invalidation on routing changes - Database persistence of all routing history 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>