🧑‍💻 fix: Agents Config Defaults and Avatar Uploads Across File Strategies

[danny-avila]

Summary

I improved the Agents endpoint configuration handling by ensuring proper defaults are always applied and enhanced avatar file processing for unique storage and correctness across all supported storage backends.

• Refactored Agents endpoint configuration: moved agentsConfigSetup to a unified, TS-based implementation, and ensured that default values are reliably set via schema and passed down from the app configuration.
• Updated agentsEndpointSchema to provide defaults for disableBuilder and capabilities, ensuring robust fallback even if custom config is absent.
• Enhanced test coverage for Agents config setup to assert correct default and custom config behaviors in various scenarios.
• Fixed avatar file processing in all storage backends (Local, S3, Firebase, Azure): avatar files are now named uniquely per agent ID (for agents) or per timestamp (for users), preventing accidental overwrites.
• Prevented user avatar field from being overwritten when uploading agent avatars by passing through agent IDs and explicitly guarding update logic.
• Sanitized file paths in the Local file deletion handler to defend against invalid or potentially unsafe paths.

Change Type

• Bug fix (non-breaking change which fixes an issue)

Testing

I ran existing and new unit tests for AppService covering agents config defaults/custom cases. I manually uploaded avatars for both users and agents in all supported file strategies (Local, S3, Firebase, Azure) and confirmed that each file is uniquely stored and the correct records are updated in the database. For file deletion, I attempted to delete files with query params and invalid path scenarios to validate error handling.

Test Configuration:

• Local storage: uploading and deleting both user and agent avatars
• S3, Firebase, Azure: uploading agent avatars with/without agent IDs, user avatars, verifying DB update behavior
• Ran AppService.spec.js and new tests for agents endpoint coverage

Checklist

• My code adheres to this project's style guidelines
• I have performed a self-review of my own code
• I have commented in any complex areas of my code
• I have made pertinent documentation changes
• My changes do not introduce new warnings
• I have written tests demonstrating that my changes are effective or that my feature works
• Local unit tests pass with my changes