chore(submodules): bump for EVO-2139 (Custom MCP test connection fix)

[marcelogorutuba]

Summary

• Bumps 3 submodules to bring in the fix for the Custom MCP "Test connection" button (was 404 for every compliant server because Go was doing GET /health, a route MCP doesn't define).

Submodule bumps

Submodule	From	To	PR
evo-ai-processor-community	9bb90d0	5282804	#36
evo-ai-core-service-community	bdec249	f621fea	#19
evo-ai-frontend-community	15582db	0cc1727	#260

Test plan

• E2E local via docker compose build evo-processor evo-core && docker compose up -d + reload frontend dev server → botão Test com https://mcp.deepwiki.com/mcp retorna toast verde "3 ferramentas descobertas".
• Contrato preservado — frontend usa test_result.success, test_result.error, test_result.tools_count (optional, novo).
• Tenant header propagation em paridade com discoverTools (EVO-1623): X-Evo-Tenant-Id set quando runtime context tem tenant, omitido caso contrário.
• Reviewer: subir stack completo e validar botão Test na UI.

Nota sobre re-bump

Os 3 pointers apontam para tips de branches feature (não develop). Se os PRs filhos forem merged como squash, os SHAs mudam e este PR precisa re-bump antes do merge — ou merge dos filhos primeiro e este PR bumpa pra develop tips depois.

Linear: https://linear.app/evoai/issue/EVO-2139

🤖 Generated with Claude Code

Summary by Sourcery

Chores:

• Update community submodule SHAs to latest feature branch tips for evo-ai-processor, evo-ai-core-service, and evo-ai-frontend.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates three git submodule pointers (core service, frontend, and processor) to newer commits that contain the Custom MCP "Test connection" fix and related contract/tenant-header behavior, without making any direct code changes in this repository.

File-Level Changes

Change	Details	Files
Update git submodules to newer commits that include the Custom MCP "Test connection" behavior fix and related API/contract adjustments.	Advance evo-ai-processor-community submodule pointer to commit 5282804 to pick up Custom MCP test-connection handling changes. Advance evo-ai-core-service-community submodule pointer to commit f621fea to align core service behavior and headers with the new MCP test-connection flow. Advance evo-ai-frontend-community submodule pointer to commit 0cc1727 to consume the updated MCP test-connection API contract (success/error/tools_count) and UI behavior.	evo-ai-processor-community .gitmodules evo-ai-core-service-community evo-ai-frontend-community

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Before merging, consider rebasing this PR to point the submodules at the final merge commits on the main/develop branches rather than feature branch tips to avoid future SHA drift and confusion.
• Once the child PRs are merged, double-check that the submodule SHAs here include only the intended MCP fix and not additional in-progress feature work from those branches.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Before merging, consider rebasing this PR to point the submodules at the final merge commits on the main/develop branches rather than feature branch tips to avoid future SHA drift and confusion.
- Once the child PRs are merged, double-check that the submodule SHAs here include only the intended MCP fix and not additional in-progress feature work from those branches.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[marcelogorutuba]

Fechando — fluxo do time é PR direto submódulo → develop, sem umbrella bump. Os 3 PRs filhos (#36 processor, #19 core, #260 frontend) seguem para review.