## Description The `ai_context:get_relevant_ai_context_items` and `ai_context:list_ai_context_items` tools accept an optional `agent_id`. Nothing populates it server-side, so in practice the LLM has to supply a Drupal config machine name it has no way of knowing. When `agent_id` is absent, `AiContextRequestFactory::fromParameters()` skips the entire agent merge: scope subscriptions stay empty, `consumerId` stays null (logged as `consumer=none`), and every subscription-based scope becomes unreachable through the tool path. This was found during QA in #3586440+s. Selection logs showed `consumer=none` until an agent ID was hardcoded into the assistant's Pre Action Prompt, after which the same run logged `consumer=chatbot_assistant_v1`. That workaround depends on model compliance on every call, breaks silently when an agent is renamed or cloned, and has to be repeated for every agent-backed assistant. The push-injection path does not have this problem, because `AiContextSystemPromptSubscriber` receives the agent ID from `BuildSystemPromptEvent`. This issue is the pull/tool path. The function-call runtime exposes the running agent on `AgentToolPreExecuteEvent` (`getAgentId()`), not on the plugin itself. Keep the fix in `ai_context`; no `ai_agents` split is needed. Do not hardcode a single tool ID. Tools opt in with `AiContextInheritsAgentIdInterface` and an optional `agent_id` context definition. `GetRelevantAiContextItems` and `ListAiContextItems` implement it. `LoadAiContextItemById` does not (no `agent_id` parameter). Custom or third-party tools can opt in the same way. Declaring `agent_id` alone is not enough. `getResult()` and `getRenderedContext()` intentionally hardcode `agentId: NULL` for non-agent callers; that behavior should not change. ## Tasks - [x] Confirm the function-call runtime exposes the running agent ID (`AgentToolPreExecuteEvent`). Stay in `ai_context`. - [x] Add `AiContextInheritsAgentIdInterface` as the public opt-in. - [x] Implement it on `GetRelevantAiContextItems` and `ListAiContextItems`. - [x] When an opted-in tool executes inside an agent run and `agent_id` is omitted, default it from the running agent. - [x] Keep `agent_id` optional and explicitly overridable. - [x] Keep the existing "no context config found for agent" warning when an ID resolves but has no saved configuration. - [x] Kernel coverage: inherited ID, explicit override, no agent context, List applying inherited never-include, Load by ID not inheriting. - [x] Docs: function calls, events, API stability, agent configuration, context delivery. ## Acceptance criteria - An agent-backed assistant reaches its saved scope subscriptions through GetRelevant or List without any prompt instruction naming the agent. - Selection logs show the agent as the consumer rather than `none`. - An explicit `agent_id` argument still wins. - Non-agent callers behave exactly as before. - Tools that do not implement the interface are left untouched. ## Testing instructions Kernel tests from the project root: ``` ddev phpunit web/modules/contrib/ai_context/tests/src/Kernel/AiContextGetRelevantAgentIdInheritanceTest.php ``` Manual check (agent-backed assistant with GetRelevant and/or List enabled, plus at least one published item subscribed or always-included for that agent): 1. Confirm the Pre Action Prompt does **not** name the agent or tell the model to pass `agent_id`. 2. Enable CCC debug logging at `/admin/config/ai/context/settings/general`. 3. Ask the assistant something that should pull context (or force a tool call in the debugger). 4. In **Reports → Recent log messages** (type `ai_context`), the selection summary should show `consumer=<agent_id>`, not `consumer=none`. 5. Confirm GetRelevant uses the agent's saved subscriptions / Always include items, or that List honors the agent's Never include list. 6. Optional: pass an explicit `agent_id` for a different agent and confirm that config wins. 7. Optional: run an agent with no CCC settings and confirm the existing "No context config found for agent" warning still logs. No update hook. Rebuild caches after deploy. ## Related issues #3586440+s MR: !275 ## AI disclosure - [x] AI generated issue