chore: Dev v4 to main

[NirajC-Microsoft]

Purpose

This pull request includes several improvements and updates across documentation, backend configuration, logging, error handling, and testing. The most significant changes are the addition of new sample scenarios in documentation, enhanced logging for agent lifecycle events, updates to environment variables for model selection, improved error handling in the backend, and better feedback for document indexing and uploads.

Documentation Enhancements:

• Added detailed sample scenarios for "RFP Analysis" and "Contract Compliance Review" to docs/SampleQuestions.md, including step-by-step instructions and notes on agent usage and response times. Also clarified the availability of teams based on post-deployment selection. [1] [2]

Backend Logging and Error Handling:

• Improved logging in agent lifecycle management (lifecycle.py), replacing silent exception handling with warnings that provide context if agent registration, closing, or unregistration fails. [1] [2] [3]
• Enhanced error handling in the /input_task endpoint test to assert proper 400 responses and error messages for invalid JSON input.
• Improved WebSocket handling to avoid tight loops on timeouts and added debug logging for receive timeouts.

Configuration and Environment Updates:

• Updated .env.sample to use the latest Azure OpenAI model (gpt-4.1-mini) and deployment names, revised API versions, and adjusted reasoning model configuration. Also updated MCP server details and supported models.

Data Indexing and Upload Feedback:

• Enhanced feedback during Azure Search index creation and document upload in index_datasets.py by reporting the number of succeeded and failed uploads, and removing unused result assignments. [1] [2]

Code Maintenance and Cleanup:

• Removed commented-out or unused code from agent factory and models for clarity and maintainability. [1] [2] [3] [4]
• Minor adjustments to frontend dependencies and server imports for cleanliness. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]

These changes collectively improve user guidance, backend reliability, and system observability.

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 4.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀