docs(ai-agent-sub-process): Update event handling

[afgambin]

Description

This PR addresses this issue.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support. (add bug or support label)
• This is already available but undocumented and should be released within a week. (add available & undocumented label)
• This is on a specific schedule and the assignee will coordinate a release with the Documentation team. (create draft PR and/or add hold label)
• This is part of a scheduled alpha or minor. (add alpha or minor label)
• There is no urgency with this change (add low prio label)

PR Checklist

• The commit history of this PR is cleaned up, using {type}(scope): {description} commit message(s)

• My changes are for an upcoming minor release and are in the /docs directory (version 8.9).
• My changes are for an already released minor and are in a /versioned_docs directory.

• I added a DRI, team, or delegate as a reviewer for technical accuracy and grammar/style:
  • Engineering team review
  • Technical writer review via @camunda/tech-writers unless working with an embedded writer.

[github-actions]

👋 🤖 🤔 Hello, @afgambin! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.8/.

• docs/components/connectors/out-of-the-box-connectors/agentic-ai/aiagent/configuration/_event-handling.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[maff]

What is the meaning of "each" here? That multiple event messages could be included?

Regarding the event payload, we briefly mention toolCallResult in the intro paragraph, but could we add a dedicated section describing what the event payload is?

With camunda/connectors#6105, the following will happen:

• If the event subprocess creates a non-empty toolCallResult, it's contents will be added as payload to the user message coming from the event.
• If no toolCallResult is created, a generic message will be added as user message, describing that an interrupting/not interrupting event was handled. See https://github.com/camunda/connectors/pull/6105/changes#diff-8c6ee6aec05c67d77e288c1949011fe8ada5aa7e3b58e3b0a6ee146dcd50e26fR52

[maff]

We probably should also document this on the generic AHSP and/or Event Subprocess pages as suggested by Philipp here.

While the AI Agent is our only solution building on the AHSP job worker, the general event subprocess logic triggering job workers is not specific to the AI Agent.

[github-actions]

The preview environment relating to the commit 2046268 has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-7788/