Create recipe feedback and initialization, recipe ui and state refactor

[zanesq]

Summary

Follow up for the larger refactor efforts mentioned in feedback on #4693

I had goose analyze my changes to help with my PR description:

Major Architectural Improvements

1. Hook Separation and Specialization

• Split useAgent.ts: Extracted agent initialization logic into a dedicated useAgentInitialization.ts hook
• Decomposed useRecipeManager.ts: Broke down the monolithic recipe manager into three specialized hooks:
  • useRecipeState.ts - Core recipe state management and validation
  • useRecipeUI.ts - UI-specific interactions and modal handling
  • useRecipeCreationModal.ts - Recipe creation modal logic
• Reduced complexity: The main useAgent.ts went from 257 lines to just 61 lines

2. Improved State Management

• Cleaner reset logic: Replaced forceReset and generic resetChat with targeted reset options:
  • resetSession - Creates new session ID
  • clearMessages - Clears chat messages
  • clearRecipe - Removes recipe configuration
  • clearRecipeParameters - Clears recipe parameters
• Better initialization context: More explicit control over what gets reset during initialization

3. Enhanced Error Handling

• Custom error types: Added specific error classes:
  • NoProviderOrModelError
  • AgentInitializationError
  • ConfigurationError
• Better error boundaries: More granular error handling during agent initialization

4. Recipe Management Improvements

• Unified save location: Both create and edit recipe modals now use the same save logic
• Recipe launching while saving: Added ability to launch a recipe immediately after saving it
• Consistent naming: Replaced recipeConfig with recipe throughout the codebase for consistency
• Better parameter validation: Improved filtering of recipe parameters to only show those actually used

5. UI/UX Enhancements

• Streamlined modals: Better modal state management and user flow
• Improved recipe form: Enhanced recipe creation/editing with better validation
• Auto-execution support: Better handling of scheduled recipe execution
• Cleaner component structure: Reduced coupling between UI components and business logic

6. Code Quality Improvements

• Better separation of concerns: UI logic separated from business logic
• More testable code: Smaller, focused hooks are easier to test
• Reduced duplication: Consolidated common recipe operations
• Type safety: Added comprehensive TypeScript types for agent states and contexts

Key Benefits

1. Maintainability: Code is now more modular and easier to understand
2. Testability: Smaller, focused hooks with clear responsibilities
3. Reliability: Better error handling and state management
4. User Experience: More responsive UI with better modal handling
5. Developer Experience: Cleaner APIs and more predictable behavior

[zanesq]

Closing this so we can get a plan together first will bring over the ui changes to the original PR