Phase 9: Fix argument type errors (TS2345) - TypeScript error reduction

[zanesq]

Phase 9: Fix Argument Type Errors (TS2345)

Summary

Systematic fix of argument type errors throughout the TypeScript codebase, targeting TS2345 "Argument of type X is not assignable to parameter of type Y" errors.

Changes Made

• App.tsx Electron Event Handlers: Updated function signatures to match Electron's expected (...args: unknown[]) pattern
• App.tsx Function Compatibility: Added wrapper functions to resolve setView parameter type mismatches
• sessionLinks Integration: Exported SessionLinksViewOptions type and added proper type conversions
• ChatInput.tsx CustomEvent: Added proper type assertion for FormEvent compatibility
• ChatView.tsx Recipe Conversion: Added proper RecipeConfig object creation from Recipe data
• ChatView.tsx Token Handling: Added null coalescing operator for total_tokens safety
• ConfigContext.tsx Provider Data: Added null coalescing for response.data handling
• SearchBar.tsx State Management: Changed null assignments to undefined for proper typing
• Linting Compliance: Fixed unused parameter warnings with underscore prefix

Technical Approach

• ✅ Electron Compatibility: Updated event handler signatures to match Electron's typing expectations
• ✅ Type Conversion: Added safe type conversions and wrapper functions for compatibility
• ✅ Null Safety: Replaced null with undefined and added null coalescing operators
• ✅ Interface Mapping: Created proper object transformations between different type interfaces
• ✅ Type Assertions: Used safe type assertions where runtime types are guaranteed
• ✅ Linting Standards: Ensured all changes pass lint checks with zero warnings

Results

• Before: 228 TypeScript errors (52 TS2345 errors)
• After: 214 TypeScript errors (35 TS2345 errors)
• Eliminated: 14 total errors, 17 argument type errors ✅
• Files Modified: 6 files
• Linting: ✅ All checks pass with zero warnings

Quality Assurance

• All changes maintain runtime functionality while improving type safety
• Proper error handling and null safety implemented
• No unsafe type assertions or any types introduced
• Full compliance with ESLint standards (zero warnings)
• Systematic approach ensures maintainable and scalable solutions

Overall Progress

• Total Progress: 186+ errors eliminated across all phases
• Phases Completed: 9 out of estimated 13 phases
• Consistent Success: Each phase continues systematic error reduction

Part of the ongoing systematic TypeScript error reduction effort with full linting compliance.