## Problem `ai_empathy_ccc` integrates with AI Context (CCC) through the request factory, the scope plugin API and the scope-subscription form builder. Several of those surfaces were renamed or removed on `ai_context` 1.0.x, and more change in beta5 via [#3586346](https://git.drupalcode.org/project/ai_context/-/work_items/3586346) (MR !283). The submodule is currently fatal against `ai_context` 1.0.x HEAD. ## Already broken on ai_context 1.0.x 1. **Scope attribute property renamed** ([#3586438](https://git.drupalcode.org/project/ai_context/-/work_items/3586438)). `#[AiContextScope]` no longer accepts `weight`; it takes `display_weight` and an optional `scoring_weight`. `AiContextScopeRequestTag` passes `weight: 6`, which is an unknown named parameter and therefore a fatal error at plugin discovery. 2. **Selection API renamed** ([#3586453](https://git.drupalcode.org/project/ai_context/-/work_items/3586453)). `ai_context.request_factory` is now `ai_context.selection_factory`, and `AiContextRequestFactory` is now `AiContextSelectionFactory` with a new `AiContextSelectionFactoryInterface`. `ai_empathy_ccc.services.yml` and `CccIntegrationSubscriber` still use the old service ID and class. 3. **Scope plugin methods renamed** ([#3586449](https://git.drupalcode.org/project/ai_context/-/work_items/3586449)). `matchesCurrentContext()` is now `matchesRequestContext(AiContextItem $item)` and the abstract `doGetCurrentValue()` is now `doGetDetectedValue()`. `AiContextScopeRequestTag` implements only the old names, so it no longer satisfies the abstract base and its `parent::` call is undefined. ## Changing in beta5 (MR !283) 4. **Consumer IDs are canonical.** `consumerId` is promoted from a logging identifier to the configuration merge key and must be of the form `{type}:{instance}`; other strings are ignored. `CccIntegrationSubscriber` passes the bare string `ai_empathy`. `getRenderedContext()` and `getResult()` are explicitly retained as documented caller-opt-in helpers, so the integration approach is still supported — only the identifier needs a decision. Options: pass `NULL`, or register an `ai_empathy` consumer type plugin via the new `#[AiContextConsumerType]` attribute. 5. `AiContextScopeInterface::getConfigName()` is removed and becomes a protected `getSettingsConfigName()`. Verified: `ai_empathy_ccc` does not call it, so no change is required here. 6. `hook_ai_context_scope_values_alter()` now takes an optional third `?CacheableMetadata $cache` parameter. The current 2-parameter implementation keeps working but never registers cacheability for the `empathy_evaluation` use-case label. ## Proposed changes - `AiContextScopeRequestTag`: `weight: 6` → `display_weight: 6`, and set `scoring_weight` explicitly (it does not fall back to `display_weight`). - `AiContextScopeRequestTag`: rename `matchesCurrentContext()` → `matchesRequestContext(AiContextItem $item)` with the typed parameter, and `doGetCurrentValue()` → `doGetDetectedValue()`. - `ai_empathy_ccc.services.yml`: inject `@ai_context.selection_factory`. - `CccIntegrationSubscriber`: type against `AiContextSelectionFactoryInterface`, and stop passing a non-canonical `consumerId`. - `AiEmpathyCccHooks::aiContextScopeValuesAlter()`: accept the optional `CacheableMetadata` parameter and add the module's config cache tags. - `ai_empathy_ccc.info.yml`: constrain the dependency to `ai_context:ai_context (>=1.0.0-beta5)`, so a signature mismatch is blocked at install rather than fatalling at discovery. - `composer.json`: bump `drupal/ai_context` from `^1.0.0-beta3` to `^1.0.0-beta5`. - Update `RequestTagContextSelectionTest`, `AiContextScopeRequestTagTest` and `CccIntegrationSubscriberTest` for the renames. ## Open question Beta5 adds a generic `AiContextPreGenerateResponseSubscriber` plus consumer type plugins, with `AiContextProviderRequestContext` exposing the AI request tags natively. That overlaps with what the custom `request_tag` scope and its static `setCurrentTags()` hand-off were built to do. The beta5 plan states non-agent consumer types exist for AI core integrations and modules split out of AI core, and are removed in 2.x, which argues for keeping the current scope-based approach. Worth confirming with the ai_context maintainers before committing to either shape. ## Remaining tasks - [ ] Apply the API renames and fix the fatals - [ ] Decide the `consumerId` value (NULL vs. a consumer type plugin) - [ ] Add the dependency version constraints - [ ] Update the affected tests - [ ] Re-test against `ai_context` beta5 once MR !283 lands