## Description Follow-up to: #3586207+s ### Summary When **Enable conditional subcontext AI decisions** (`conditional_subcontext_enabled`) is off, conditional subcontext children should not participate in normal context selection. This issue implements that behavior and adds admin UX so editors understand why conditional items are inactive, can reach the setting to re-enable the feature, and get clear warnings when editing affected items. ### Problem / motivation Previously, disabling conditional subcontext AI caused **all conditional children to be included without an AI call**. That was surprising: the toggle read like “skip AI,” but the runtime effect was closer to “include everything.” Admins also lacked clear signals in the UI: - Conditional children looked the same as active ones in the context item list - No warning appeared when editing a conditional subcontext with the feature disabled - Settings that control the behavior were hard to reach from list affordances A code review also identified accessibility, security, and rendering issues around list tooltips and toggle helpers. ### Proposed resolution #### Runtime behavior - When `conditional_subcontext_enabled` is **off**, **exclude conditional subcontext children** from normal context selection - **Required** subcontext children are still included - Conditional children may still appear when using **custom scope** or an agent’s **Always include** settings - When the toggle is **on**, existing AI-based conditional selection behavior is unchanged #### Admin UX **Context item list** - Ghost conditional child rows when the feature is disabled (visual de-emphasis scoped to the label cell) - Tooltip on the subcontext type indicator explaining the disabled state, with a link to context item settings - Accessible equivalents for keyboard/screen reader users: - visually hidden status text - keyboard-focusable settings link - focusable subcontext indicator with plain-text `aria-label` **Context item edit form** - Messenger warning when editing a **conditional** subcontext while the feature is disabled **Settings deep links** - Support `?fieldset=` on general and item settings forms to open the matching `details` fieldset - Scroll to the opened fieldset on load - Example: `/admin/config/ai/context/settings/items?fieldset=subcontext` #### Technical / maintainability - Refactor list label cells from `inline_template` to render arrays - Render subcontext type tooltips via trusted render arrays (`renderInIsolation()`), bubble cache metadata, and document the `data-ai-tooltip` / `innerHTML` contract - Escape parent labels in subcontext type tooltips via `inline_template` - Deduplicate subcontext toggle reads in `AiContextSubcontextToggleTrait` via shared `getAiContextBoolSetting()` - Update form descriptions and resolver docs to match the new disabled behavior ### User-facing behavior change Sites with `conditional_subcontext_enabled: false` will **stop including conditional subcontext children in normal selection**. This is intentional, but may affect existing sites that relied on the old “include all conditionals without AI” behavior. No config migration is required; default remains `true`. ### Testing - Kernel: subcontext resolver, conditional subcontext E2E, settings fieldset deep links, list builder tooltip rendering/escaping - Functional: item list ghosting/accessibility, item form warning visibility - Config validation: settings forms attach fieldset library and open matching fieldset from query param <!-- If this issue description was significantly AI-generated (entire sections, not autocomplete), please note it in a comment below. See https://www.drupal.org/docs/develop/issues/issue-procedures-and-etiquette/policy-on-the-use-of-ai-when-contributing-to-drupal --> > [!note] > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [ ] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > > * [x] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._