🔴 CRITICAL: Replace force unwraps in security-critical code

Problem

The codebase contains 11+ force unwraps and fatalError calls in security-critical paths that can cause production crashes.

Affected Files

Impact

• Severity: Critical
• Risk: App crashes in production when preconditions not met
• User Impact: Authentication failures, data loss

Solution

1. Replace fatalError with proper error handling (throw/Result)
2. Replace ! force unwraps with guard let + error handling
3. Add graceful degradation for missing services
4. Log errors instead of crashing

Acceptance Criteria

• Zero force unwraps in AuthenticationManager.swift
• Zero force unwraps in ArkavoWebSocket.swift
• ServiceLocator returns nil or throws instead of fatalError
• All security paths have proper error recovery

Start by auditing the listed Swift files: ArkavoApp.swift, AuthenticationManager.swift, ArkavoWebSocket.swift, and IDCardScannerViewController.swift, focusing on the reported force unwraps and fatalError calls. Trace how each security-critical path handles missing values or services. Done means the stated force unwraps are removed, ServiceLocator no longer crashes on missing services, and all security paths have error recovery.