## Summary Consumer configuration stores `always_include` and `never_include` values as local `ai_context_item` entity IDs. Those IDs are not portable across environments, so exported config can attach the wrong context item, or no context item, after config import on another site. This should store context item UUIDs in config, matching Drupal core entity reference default value config, where UUIDs are used so references survive config import/export between environments. It should also declare content dependencies for those referenced context items, using Drupal's standard content dependency format (`entity_type:bundle:uuid`), so config import can participate in the missing-content dependency workflow. ## Related issues - #3554221+s: Setting context pools acts differently between agent form and context pool form. Related because it discusses how context IDs are stored under include/always-include configuration. - #3574359+s: Refactor context selection logic. Related because it defines always-include and always-exclude overrides as explicit selection inputs independent of AI-based matching. - #3556875+s: Context summary on the AI Context settings page is not very helpful. Adjacent UI/DX context around surfacing which contexts are always included. ## Steps to reproduce 1. Enable `ai_context` on a Drupal site. 2. Create multiple AI context items. 3. Configure an AI Context consumer and set one non-global context item to `Always include`. 4. Export configuration and inspect `ai_context.consumers.yml`. 5. Import the same configuration into another environment where the same context item has a different numeric entity ID, or where a different `ai_context_item` has reused that numeric ID. ## Expected result `ai_context.consumers.yml` stores stable context item UUIDs for include/exclude overrides and declares matching content dependencies, for example: ```yaml dependencies: content: - 'ai_context_item:ai_context_item:92ae3b61-0ab0-47d0-ba1d-719b30c77a39' consumers: - consumer_id: 'agent:content_type_agent_triage' type: agent push_enabled: true always_include: - 92ae3b61-0ab0-47d0-ba1d-719b30c77a39 ``` On config import, the consumer resolves that UUID to the correct local `ai_context_item` entity ID. The content dependency lets the config import process participate in Drupal's missing-content dependency workflow. ## Actual result `ai_context.consumers.yml` stores local numeric entity IDs: ```yaml consumers: - consumer_id: 'agent:content_type_agent_triage' type: agent push_enabled: true always_include: - '3' ``` That value only means "entity ID 3 on this database". After import into another environment, entity ID `3` may point to a different context item, or may not exist. The consumer can silently include the wrong guidance. ## Environment - Drupal version: 11.4-dev - Module version: 1.0.x-dev - PHP version: 8.5.7 - Provider: Not provider-specific - Last known working version: Not applicable ## Proposed fix **Config stores UUIDs. Runtime selection works in local entity IDs.** - `ai_context.consumers` `always_include` / `never_include` store context item UUIDs. - Stored and resolved consumer config objects expose those values as-is (UUIDs, or leftover numeric IDs until conversion). - `AiContextSelectionFactory` resolves identifiers to local entity IDs when building an `AiContextSelection`. Direct `select()` still accepts UUIDs or leftover numeric IDs. - The consumer form still recognizes leftover numeric IDs when showing inclusion state, and rewrites them to UUIDs on save. - Form save writes `dependencies.content` and merges it into the existing `dependencies` map so other keys (`module`) survive. Empty content lists drop only `content`. - Post-update `0008` converts leftover numeric IDs to UUIDs where the item still exists, and backfills `dependencies.content`. Unknown leftover IDs stay in the list. - Leftover `ai_context.agents` is not converted and still holds IDs. Implementation outline: - Save UUIDs from `AiContextConsumerForm` instead of table-row entity IDs. - Keep recognizing leftover numeric IDs on the form and at runtime. - Resolve once in the selection factory (and budget calculator) so selector, subcontext, and `ListAiContextItems` all see local IDs. - Share resolution in `@internal` `AiContextItemIdentifierResolverTrait`. Preserve input order; first occurrence wins. - Add `dependencies` schema to `ai_context.consumers`. - Add post-update `0008` for existing sites. - Cover UUID selection, factory resolve, mixed numeric/UUID never-wins, form-save rewrite + dependency merge, and post-update conversion. > [!note] > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [x] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > > * [ ] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._