Add Aspire MCP integration and improve developer CLI parallel execution

[tjementum]

Summary & Motivation

Enable Aspire MCP integration for Claude Code and enhance developer CLI tooling to improve development workflow efficiency.

• Add Aspire MCP server configuration to .mcp.json and enable the MCP endpoint in AppHost launch settings, allowing Claude Code to interact with Aspire directly
• Update AI agent instructions with comprehensive parallel execution guidance: build must run first, then slow operations (Aspire restart, backend format, backend inspect, end-to-end tests) must run in parallel Task agents, while fast operations (frontend format/inspect, backend test) can run sequentially
• Add waitForAspire parameter to the end-to-end MCP tool, which retries server availability checks up to 10 times (50 seconds total) when Aspire is starting. This eliminates the need for manual sleep delays when running end-to-end tests in parallel with Aspire restart
• Rename the MCP method from E2E to EndToEnd to produce a cleaner tool name (mcp__developer-cli__end_to_end over mcp__developer-cli__e2_e)
• Convert developer-cli/DeveloperCli.slnx.DotSettings to a symlink pointing to the main application/PlatformPlatform.slnx.DotSettings to avoid duplication and ensure consistent code style settings
• Remove redundant tool execution instructions from process workflow files, referencing the new global tool execution instructions instead

Checklist

• I have added tests, or done manual regression tests
• I have updated the documentation, if necessary

[linear]

PP-762 Add Aspire MCP to Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud