chore: sync fork with upstream microsoft/main

[cxzyr9hm2t-del]

Purpose

• Brings this fork up to date with microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator@main.
• The fork's main was pinned at 452419c (merge of psl-mainChanges, 2026-07-07) and had drifted 1359 commits behind upstream, with 0 commits ahead — so this is a clean fast-forward, not a merge.
• Branch claude/full-sync-status-mv873v now points at upstream 9937162 (merge of PR feat: Modularity Enhancement and New use case for Content Generation microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator#1068 microsoft/dev, 2026-07-23) and is byte-identical to it.
• Net effect: 399 files changed, ~191,955 insertions, ~82,597 deletions. No commits were authored here — every commit in this PR originates upstream.

Notable content carried in by the sync:

• Backend test suite reorganized out of src/tests/backend/v4/... into src/tests/backend/{services,tools}/..., with new test_mcp_service.py, test_plan_service.py, test_team_service.py, and test_clarification_tool.py.
• New src/tests/mcp_server/test_image_service.py and tests/e2e-test/pyproject.toml.
• Assorted infra, orchestration, and MCP tooling updates from the upstream dev merge.

Does this introduce a breaking change?

• Yes
• No

Not a breaking change to any code written in this fork, but it is a large upstream jump: test paths moved, backend service modules were restructured, and infra/Bicep templates changed. Anything pinned to the old src/tests/backend/v4/ layout will need updating.

How to Test

• Get the code

git clone https://github.com/cxzyr9hm2t-del/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator.git
cd Multi-Agent-Custom-Automation-Engine-Solution-Accelerator
git checkout claude/full-sync-status-mv873v

• Test the code

# Confirm the branch is an exact fast-forward of upstream main
git fetch https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator.git main
git rev-list --left-right --count FETCH_HEAD...HEAD   # expect: 0  0

# Run the suites
python -m pytest src/tests/backend
python -m pytest src/tests/mcp_server
flake8 --config=.flake8 src/backend

What to Check

Verify that the following are valid

• git rev-list --left-right --count <upstream/main>...HEAD reports 0 0 — the branch matches upstream exactly with no fork-local drift.
• The relocated backend tests are collected and pass under their new src/tests/backend/services/ and src/tests/backend/tools/ paths, and no stale v4/ test paths remain referenced by CI.
• CI workflows under .github/workflows/ still resolve to existing paths after the test-tree move.
• No fork-specific customization was silently dropped — the fast-forward is only safe because the fork had zero unique commits, which is worth confirming before merge.

Other Information

• Fast-forward only; no merge commit and no conflict resolution was required.
• PR fix: correct CLAUDE.md against the current tree and repair three dead test-config defects #1 (claude/claude-md-docs-fbnno8, adds CLAUDE.md) branches from the old 452419c base and is unaffected by this PR, but will need a rebase onto the synced main before it merges cleanly.
• GitHub reports 130 open Dependabot vulnerability alerts on the default branch (1 critical, 47 high, 40 moderate, 42 low). Out of scope for this sync, but flagging it.

---

Generated by Claude Code