chore: merge dev into main

[Harmanpreet-Microsoft]

Purpose

This pull request introduces robust error handling and user feedback improvements across both backend and frontend for plan orchestration and approval flows. The changes ensure that errors are consistently communicated to users via WebSocket messages, with clear formatting and improved logging for debugging. Additionally, the .flake8 config and documentation are updated for clarity and maintainability.

Backend Improvements:

Error Handling and User Feedback:

• Introduced a new ERROR_MESSAGE type to WebsocketMessageType in both backend (messages.py) and frontend (enums.tsx) to standardize error communication. [1] [2]
• Enhanced the plan_approval endpoint and orchestration manager to catch and log errors, sending user-friendly error messages via WebSocket on various failure scenarios (e.g., invalid input, agent not found, unexpected errors, runtime errors). [1] [2] [3]
• Added try/except blocks to agent response callbacks to log errors without breaking orchestration flow.

Code Quality and Maintenance:

• Improved import organization and removed commented-out code for cleaner, more maintainable files. [1] [2] [3]

Frontend Improvements:

Error Display and User Experience:

• Added a handler for ERROR_MESSAGE WebSocket events in PlanPage.tsx, extracting and formatting error content for display as a system agent message, and ensuring UI state resets appropriately on errors.
• Implemented formatErrorMessage to display error messages with clear visual cues and indentation.
• Updated plan approval UI state management to reflect processing and error states, improving user feedback during approval actions. [1] [2] [3]

Configuration and Documentation:

Project Maintenance:

• Updated .flake8 to exclude additional frontend and test files, improving linting accuracy for the backend codebase.
• Enhanced documentation in ACRBuildAndPushGuide.md with clearer instructions and new sections for MCP server image management.

These changes collectively make the system more resilient to errors, improve the developer experience with better logging, and provide users with clearer, actionable feedback when issues occur.

• ...

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