chore(submodule): bump evo-ai-processor-community for EVO-1626 stack

[marcelogorutuba]

Summary

Bumps evo-ai-processor-community submodule pointer to carry the EVO-1626 stack:

• runtime_context EP version bump 1.0.0 → 1.1.0 (new optional bind_context sibling)
• StandardRunner.run_agent wires async with runtime_context.bind_context(context_id) to keep operational context bound across awaits
• Request threaded from chat/a2a routes into the EP call site
• Mirror tests for the wrap shape (community vocab — no tenant/enterprise leakage)

Depends on

• feat(runtime_context): pass Request to extension point (EVO-1626 followup) evo-ai-processor-community#13 — must merge first

Companion (overlay, external repo)

• evolution-foundation/evo-enterprise-licensing-python#1 — consumer impl (gem, not in this umbrella)

Test plan

• Wait for evo-ai-processor-community#13 to merge into its base
• Re-point this branch's submodule to that merged SHA
• Confirm community processor tests still pass on the bumped pointer
• Merge

Linked Issue

• EVO-1626

🤖 Generated with Claude Code

Summary by Sourcery

Chores:

• Bump evo-ai-processor-community submodule pointer to the latest required revision.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the evo-ai-processor-community git submodule pointer to a newer commit that carries the EVO-1626 stack changes, without modifying any in-repo source files.

File-Level Changes

Change	Details	Files
Bump evo-ai-processor-community submodule to a newer commit containing EVO-1626 runtime_context and StandardRunner updates.	Update the git submodule reference for evo-ai-processor-community to a new SHA that includes runtime_context EP version 1.1.0 with the new bind_context sibling. Rely on upstream changes where StandardRunner.run_agent binds operational context across awaits via runtime_context.bind_context. Pick up upstream changes that thread Request objects from chat/a2a routes into the EP call site and add mirrored community tests for the wrapping shape.	evo-ai-processor-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.