What is the user interaction of your feature
When a new user registers for ApeRAG, they should be able to immediately start chatting without any additional setup steps. The user story is:

1. User completes registration
2. User is automatically redirected to chat interface
3. User can immediately start asking questions and receive responses
4. No manual bot creation or API key setup required

Is your feature request related to a problem? Please describe.
Currently, new users face friction during onboarding because they must manually create a bot before they can start using ApeRAG's chat functionality. This creates a poor first-time user experience where users have to:

• Navigate to bot creation interface
• Configure bot settings
• Set up API keys for MCP integration
• Only then can they start chatting

This multi-step process may discourage new users from fully exploring ApeRAG's capabilities.

If this is a new feature, please describe the motivation and goals.
The motivation is to eliminate onboarding friction and improve user adoption rates. Goals include:

• Reduce time-to-first-value for new users
• Simplify the registration-to-chat flow
• Increase user engagement and retention
• Provide seamless MCP integration out-of-the-box
• Create a more intuitive user experience similar to other chat platforms

Describe the solution you'd like
Automatically create the following resources when a new user registers:

1. Agent-type bot: Pre-configured and ready for immediate use
2. API key: Generated for MCP HTTP interface authentication
3. Hidden management: Both resources should be invisible to users and non-deletable
4. Seamless integration: The auto-created bot should work immediately with existing MCP endpoints

The system should handle this creation transparently during the registration process, with proper error handling and rollback mechanisms.

Describe alternatives you've considered

1. Guided onboarding wizard: Walk users through bot creation step-by-step

   • Pros: Educational for users
   • Cons: Still adds friction and complexity

2. Default bot templates: Provide pre-made bot templates for quick setup

   • Pros: Faster than manual creation
   • Cons: Still requires user action and decision-making

3. Optional auto-creation: Ask users during registration if they want auto-creation

   • Pros: Gives users choice
   • Cons: Adds decision fatigue and complexity

Additional context
This feature aligns with modern SaaS onboarding best practices where users can immediately experience core functionality. Similar to how ChatGPT, Claude, or other AI chat platforms work - users can start chatting immediately after account creation.

Technical considerations:

• Ensure auto-created resources don't count against user quotas
• Implement proper cleanup for abandoned accounts
• Consider rate limiting for auto-created bots
• Maintain backward compatibility with existing user flows