tags. After the project summary prose, add a single subsection titled "

How can I help on this project?

" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now (e.g. reviewing a specific MR, picking up an unassigned issue, writing a test, or investigating a blocker). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add event hook to ai_ckeditor to allow context injection](https://git.drupalcode.org/project/ai/-/work_items/3581952) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Jesse Hofmann-Smith (jessehs) | Labels: AI Initiative Sprint, AI Product Development, aiCkeditor, category::feature Description: >>> [!note] Migrated issue Reported by: [jessehs](https://www.drupal.org/user/620440) Related to !1469 !1425 >>> Problem/Motivation The ai_ckeditor module provides AI-powered CKEditor 5 actions (Tone, Translate, Summarize, etc.) but has zero entity awareness — it doesn't know what content type, bundle, or entity ID the editor is attached to. The ai_context module provides a sophisticated scope-based context selection system that can inject bundle-specific writing guidelines into AI prompts. These two modules cannot communicate because: ai_ckeditor does not pass entity information (… ### [Generalize behaviour of FWA with Automators](https://git.drupalcode.org/project/ai/-/work_items/3577050) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Ahmad Khader (Ahmad-Khader) | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::task Description: >>> [!note] Migrated issue Reported by: [a.dmitriiev](https://www.drupal.org/user/3235287) Related to !1283 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation At the moment each field widget action in ai_automators module (that use automators) is using its own custom code to manipulate the form element data. This leads to a lot of different approaches and doesn't always allow using mul… ### [Move Automators to Structured Output](https://git.drupalcode.org/project/ai/-/work_items/3577170) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1291 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Currently Automators is using pseudo json to create the output that is required when calling AI. This has historical reasons that are all explained here: #3565806: [Discuss] Move Automators to Structured Output. The main reas… ### [Document how update hooks should be named](https://git.drupalcode.org/project/ai/-/work_items/3578472) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, category::task, documentation Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1318 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have a little bit weird way of doing update hooks right now. We should use version name major/minor and three numbers. So the first on 1.1.x would be 11001, the second one is 11002 and so on. Then on 1.2.x it would be 1200… ### [Create JS form editor for the default information tools](https://git.drupalcode.org/project/ai/-/work_items/3577937) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, Needs UX review, aiAgent Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1490 !253 >>> Problem/Motivation Default Information Tools, are tools that loads context into the agent, before it did need to take a decision. For instance the Field Agent, needs to know what entites and bundles exists that are fieldable for almost any query. So, instead of having an expensive loop this loads this into the system prompt using a tool/function call. The problem we are having is that setting these up is quite complex, see the documentation here: https://project.pages.d… ### [Use the provider configuration element for Automators](https://git.drupalcode.org/project/ai/-/work_items/3577173) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1449 !1320 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: Use the AI provider configuration form element instead of AiProviderFormHelper in AI Automators and migrate stored configuration Check-in Date: MM/DD/YYYY [/Tracker] Problem/Motivation In AI 2.0 a standardized provider selection and configuration form element was introduced for configuring AI providers. This element is documented here: AI Provider Configuration Element. The AI Automa… ### [TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields](https://git.drupalcode.org/project/ai/-/work_items/3586430) State: opened | Updated: 2026-05-10 | Author: Pieter Frenssen (pfrenssen) | Assigned: unassigned | Labels: Description: ## Summary Currently `AutomatorBaseAction::getAutomatorsOptions()` requires a `$bundle` to be passed in to retrieve the options for a field. The bundle is available for regular fields added through the field API, but base fields are not associated with a bundle (since base fields apply to all bundles). This can cause a fatal `TypeError` to be thrown when calling code cannot supply a bundle. For example when `AutomatorBaseAction::isAvailable()` is called for an automator associated with a base field. ## Steps to reproduce 1. Create an "Article" node type. 2. Enable the [Base Field Override… --- MERGE REQUESTS (24h) --- ### [feat: #3577170 Move Automators to Structured Output](https://git.drupalcode.org/project/ai/-/merge_requests/1291) State: opened | Author: Ann Mary Sruthy (annmarysruthy) | Branch: 3577170-move-automators-to | 1819 diff lines Description: Closes #3577170 ### [#3577937: add default tools editor](https://git.drupalcode.org/project/ai/-/merge_requests/1490) State: opened | Author: Bruno Bruno (bbruno) | Branch: 3577937-default-tools-editor | 6722 diff lines Description: Adds a new React app `default-tools-editor` which provides an 'Interactive' way to manipulate the `Default Information Tools` field for Agents which only takes YAML. Allowing for easier Add/Removal/Edit of different tools. Some of the features of the react app: - Ability to change tabs between YAML and the Interactive mode. So manual adjustments are still possible - Autocomplete on tool selection field, listing all available tools on the website. - Lists all available tool parameters based on the chosen tool, along with the described Help Text (description) for the expected values for that … ### [TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields](https://git.drupalcode.org/project/ai/-/merge_requests/1568) State: opened | Author: Pieter Frenssen (pfrenssen) | Branch: 3586430-automatorbaseaction | 257 diff lines Description: ## Description Fixes #3586430 ## Testing instructions Run `\Drupal\Tests\ai_automators\Kernel\AiAutomatorsBaseFieldTest`. Manual test instructions are in #3586430 ## Checklist - [x] I have linked the related issue in the MR title or description - [x] I have performed a self-review of my own code - [x] I have added or updated tests, or explained in the description why this change is not covered by tests - [ ] I have updated documentation for any new or changed functionality - [x] I have written testing instructions and verified them locally - [ ] I have noted any required post-merge steps… ### [Resolve #3577173 "Wrong rebase"](https://git.drupalcode.org/project/ai/-/merge_requests/1449) State: opened | Author: Marcus Johansson (Marcus_Johansson) | Branch: 3577173-wrong-rebase | 1500 diff lines Description: Closes #3577173 ### [#3577173: Use the provider configuration element for Automators](https://git.drupalcode.org/project/ai/-/merge_requests/1320) State: opened | Author: Anjali Prasannan (AnjaliPrasannan) | Branch: 3577173-use-the-provider | 1015 diff lines Description: Closes #3577173 ### [ai-3578472:3578472-document-how-update](https://git.drupalcode.org/project/ai/-/merge_requests/1318) State: opened | Author: Avinash jha (avinash.jha) | Branch: 3578472-document-how-update | 24 diff lines Description: Adds documentation explaining the update hook naming convention. Update hooks follow the pattern: ai_update_MAJORMINORNNN() Examples: ai_update_11001() ai_update_11002() ai_update_12001() Closes #3578472 --- COMMITS (24h) --- (none) ======================================================================== ## [2] summariseModule:ai_initiative:developer ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal AI Initiative (machine name: ai_initiative) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, contributors, and what is blocking progress. Be specific — mention function names, module names, and MR references where relevant. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Drupal AI Initiative
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now (e.g. reviewing a specific MR, picking up an unassigned issue, writing a test, or investigating a blocker). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Update Chicago Driesnote repo to include demo prompts](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586511) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Demo, AI Initiative Sprint, category::task, demos Description: ## Problem/motivation We have the repo for the Chicago Driesnote: https://github.com/fosterinteractive/c2026/ but the demo prompts aren't included. ## Solution Pull out the minimum prompt info from the "Chicago DriesNote Brainstorm / AI CMS Comparison" Google doc and add to a file in the repo. ## Tasks - Review Google doc and extract best prompt info - Add prompts to an md file in the repo ### [Fix RAG search on Chicago Driesnote repo install](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586512) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Demo, AI Initiative Sprint, category::bug, demos Description: ## Problem/motivation We have the repo for the Chicago Driesnote: https://github.com/fosterinteractive/c2026/ but RAG search wasn't working for me ## Solution Fix it in the repo or provide instructions in the readme on how to set it up. ## Tasks - Figure out fix - Update config and/or readme as needed --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [3] summariseModule:unstructured:developer ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Unstructured (machine name: unstructured) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, contributors, and what is blocking progress. Be specific — mention function names, module names, and MR references where relevant. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Unstructured
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now (e.g. reviewing a specific MR, picking up an unassigned issue, writing a test, or investigating a blocker). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Resolve #3582438 "Create document loader"](https://git.drupalcode.org/project/unstructured/-/merge_requests/17) State: opened | Author: Ahmad Khader (Ahmad-Khader) | Branch: 3582438-create-document-loader | 1989 diff lines Description: Closes #3582438 --- COMMITS (24h) --- (none) ======================================================================== ## [4] summariseModule:canvas:developer ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal Canvas (machine name: canvas) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, contributors, and what is blocking progress. Be specific — mention function names, module names, and MR references where relevant. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Drupal Canvas
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now (e.g. reviewing a specific MR, picking up an unassigned issue, writing a test, or investigating a blocker). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Draft: Resolve #3583684 "Symmetric content inputs"](https://git.drupalcode.org/project/canvas/-/merge_requests/882) State: opened | Author: Ted Bowman (tedbow) | Branch: 3583684-symmetric-content-inputs | 1071 diff lines Description: Closes #3583684 The aim here is to achieve the equivalent functionality for component trees stored in content entities as !898 does for component trees stored in config entities. It integrates with tmgmt_content Screenshots of translation form: ![tmgmt_content_multi_text](/uploads/b2883defec61bad563bb03ab9c32093c/tmgmt_content_multi_text.png){width=900 height=325} ![tmgmt_content_cta](/uploads/864471c5836067c0258b6e4f9d5ae1c1/tmgmt_content_cta.png){width=900 height=340} Relative link: This looks wrong "internal:/about" Does our widget hide. internal:/ ![tmgmt_content_multi_relative_link](… ### [Issue #3588450](https://git.drupalcode.org/project/canvas/-/merge_requests/1072) State: closed | Author: Shubham Prakash (shubham.prakash) | Branch: 3588450-formattedtext-component-renders | 47 diff lines Description: Closes #3588450 ### [Issue #3587472](https://git.drupalcode.org/project/canvas/-/merge_requests/1017) State: closed | Author: Shubham Prakash (shubham.prakash) | Branch: 3587472-re-adding-a-multivalue | 65 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 AI Assisted code ### [The original fix MR added to #3587865 - but with test added](https://git.drupalcode.org/project/canvas/-/merge_requests/1088) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-re-adding-a-multivalue-where-i-can-run-it | 24 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [Resolve #3587472 "Backend Widget solution"](https://git.drupalcode.org/project/canvas/-/merge_requests/1089) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-solution | 44 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [3587865 test only](https://git.drupalcode.org/project/canvas/-/merge_requests/1087) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-test | 24 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [Draft: Post multivalue reroll](https://git.drupalcode.org/project/canvas/-/merge_requests/1033) State: opened | Author: Ben Mullins (bnjmnm) | Branch: post-multivalue-reroll | 8546 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR --- COMMITS (24h) --- (none) ======================================================================== ## [5] summariseModule:ai_context:developer ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Context Control Center (CCC) (machine name: ai_context) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, contributors, and what is blocking progress. Be specific — mention function names, module names, and MR references where relevant. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Context Control Center (CCC)
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now (e.g. reviewing a specific MR, picking up an unassigned issue, writing a test, or investigating a blocker). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [[META] CCC MVP 1.0 roadmap](https://git.drupalcode.org/project/ai_context/-/work_items/3567798) State: opened | Updated: 2026-05-11 | Author: drupalbot | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, category::plan, mvp Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> --- ## Problem/Motivation We need a stable release of CCC to support Drupal CMS that includes a lot of the ideas and features we've been discussing, including the 1-year plan capabilities. --- ## Proposed resolution Update issue list and work through them --- ## Target date or deadline - March 23rd: Beta1 release - March 23rd to 27th: DrupalCon Chicago - May 10: Beta2 release - May TBD: Beta3 release - June TBD: RC1 release - June TBD: RC2 release - June TBD: 1.0 release --- ## Remaining task… ### [Create CCC beta2 release](https://git.drupalcode.org/project/ai_context/-/work_items/3585920) State: closed | Updated: 2026-05-11 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Create CCC beta2 release Tag: 1.0.0-beta2 Proposed resolution Create the release once at least the must-haves are done here: #3585902: CCC beta2 release planning Target date or deadline 4 May 2026 Remaining tasks … ### [Create CCC video showing how to configure it](https://git.drupalcode.org/project/ai_context/-/work_items/3586153) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: People have been having some trouble understanding how to set up CCC. Create a simple video for setting it up. ### [CCC navigation icon missing due to menu changes](https://git.drupalcode.org/project/ai_context/-/work_items/3586227) State: closed | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation The menu changed in: #3586147 which broke the css for the icon ## Solution Update css to handle change. ## Tasks - Update code - Review and test ## AI disclosures - [ ] AI assisted issue - [x] AI generated code ### [CCC beta blog post](https://git.drupalcode.org/project/ai_context/-/work_items/3577657) State: opened | Updated: 2026-05-11 | Author: drupalbot | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need a blog post to announce CCC beta Proposed resolution Write it and run it by the marketing team Target date or deadline 1 May 2026 Remaining tasks Write blog post Review and tweak Ping marketing team for s… ### [CCC beta2 QA](https://git.drupalcode.org/project/ai_context/-/work_items/3586156) State: closed | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: > [!note] > Migrated issue > Migrated from issue #3577669 > Reported by: [kristen pol](https://www.drupal.org/user/8389) --- ## Tracker **Update Summary:** [One-line status update for stakeholders] **Check-in Date:** MM/DD/YYYY **Blocked by:** - [#XXXXXX](https://www.drupal.org/project/ai_context/issues/XXXXXX) **Additional Collaborators:** @username1, @username2 _Metadata is used by the [AI Tracker](https://www.drupalstarforge.ai/). Docs and additional fields [here](https://www.drupalstarforge.ai/ai-dashboard/docs)._ --- ## Problem/Motivation Need a QA script for beta… ### [Integrate CCC with Document Loader for MDXEditor integration](https://git.drupalcode.org/project/ai_context/-/work_items/3586228) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 10, category::feature, priority::major, sprint candidate Description: ## Problem/motivation Follow-up or perhaps a replacement to: #3569310 We want to allow users to use a source for their markdown (e.g. MD, PDF, text file, URL). Document Loader has integrated with MDXEditor to make this easy: [#3580850](https://www.drupal.org/project/document_loader/issues/3580850) This has been fixed and there's a new release (2.0.1) that includes it. Hooks were also added: [#3585786](https://www.drupal.org/project/document_loader/issues/3585786) so we can save the source. ## Solution **IMPORTANT: The integration should be done using progressive enhancement. We shoul… ### [Add webpage (URL) context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574414) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, needs prioritization, needs ux review, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3547034: [Spike] Research URL support for CCC This requires a UX discussion before we work on it. Proposed resolution Review #3547034: [Spike] Research URL support for CCC, discuss UX options, pick … ### [Add MD context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574928) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, needs prioritization, priority::normal, state::postponed Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We want to upload MD files as context. Proposed resolution Discuss, scope, and implement Target date or deadline Post-Chicago Remaining tasks Discuss and align Scope feature Update code Review and test AI usage … ### [Add PDF context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574413) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, priority::normal, state::postponed, what::code Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3547035: [Spike] Research PDF upload support for CCC Ability to use PDF to source context. This requires a UX discussion before we work on it. Please take a look at comment #34 of that issue. Propos… ### [[META] Context source plugin feature (context from PDF/MD/Word/URL/etc)](https://git.drupalcode.org/project/ai_context/-/work_items/3569310) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, category::feature, needs prioritization Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !103 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We want a generic mechanism for adding context source plugins, such as loading context from a: PDF MD file Word doc Google doc Single webpage (URL) And converting the info to markdown, and inser… ### [Add Site Architecture context source for Drupal site behavior contracts](https://git.drupalcode.org/project/ai_context/-/work_items/3586150) State: opened | Updated: 2026-05-10 | Author: scott falconer (scottfalconer) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem / Motivation Outside-in agents need to understand how a Drupal site actually produces public and operational outcomes before they act. Today, that site-specific truth often lives across routes, aliases, entity routes, bundles, fields, workflows, Views, Pathauto, Canvas pages, menus, custom routes, code signals, and runtime validation. Without that context, agents can make plausible but wrong decisions, such as: - creating a static page where an existing route, alias, View, Canvas page, or entity route already owns the surface; - creating the wrong bundle for a listing or detail r… ### [Default some context scope plugins to disabled if module dependencies aren't installed](https://git.drupalcode.org/project/ai_context/-/work_items/3579235) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: blocked, category::task, needs prioritization, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation There are context scope plugins that are dependent on other modules: languages => language module tags => taxonomy module and there may be custom/contrib plugins added later that may be as well Proposed reso… ### [(Discuss) Associating adhoc vocabularies (freetagging) with context items](https://git.drupalcode.org/project/ai_context/-/work_items/3586198) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 10, category::plan, needs ux review, priority::normal Description: ## Problem/motivation ### Current taxonomy-related features Right now taxonomy-related functionality is available for context items in the following ways: 1. **Tags Scope Plugin:** The AI Context Tags is a vocabulary provided if you want to categorize your context in special ways. Agents can subscribe to these tags if they way. Example: Add a "webform" tag in the vocabulary and then if you have a webform agent, you could use that tag for scope subscriptions and you can tag any context items that are suited for webforms with the tag. This would a way to join the webform agent to one or more… ### [CCC slides and presentation for NYC Drupal AI Summit 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3586201) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Sprint 9, NYC2026, category::task, priority::normal Description: ## What CCC presentation by Kristen Pol for NYC Drupal AI Summit 2026 ## Tasks - Update slides - Practice - Present! ### [CCC slides and presentation for DrupalSouth Wellington 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3586200) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 9, DrupalSouth2026, category::task, priority::normal Description: ## What CCC presentation by Suchi Garg for DrupalSouth Wellington 2026 ## Tasks - Meet with Kristen to go over materials - Suchi research and testing - Suchi prep slides and create videos - Kristen review slides and videos - Suchi present! ### [Clarify scope items are additive in docs and UI](https://git.drupalcode.org/project/ai_context/-/work_items/3586196) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Sprint 10, category::task, priority::normal Description: ## Problem/motivation Follow-up to: #3586195 Scope subscriptions are additive. If you subscribe to use case = "writing words" and tag = "campaign", you will get context items that are scoped to either of these. Meaning, the context item doesn't need *both* of them to be relevant. ## Solution - Review existing docs and update as needed - Review UI text and consider clarifying this to the user ### [Create GitLab issue templates for ai_context project](https://git.drupalcode.org/project/ai_context/-/work_items/3586155) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: Need to have our issue templates again! Look at the new ai_initiative ones for inspiration ### [Sprint 10 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3586225) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and estimates on release timing. --- ## Proposed resolution - Go through all issues and prioritize - Identify what goes into the next sprint - Identify candidates for future sprints - Add new issues as needed - Update roadmap meta with latest info --- ## Target date or deadline 10 May to 29 May 2026 --- ## Remaining tasks - Go through all issues and prioritize - Figure out what's in the next sprint - Figure out candidates for future sprints - Add new issues as needed… ### [Test Chicago Driesnote repo with cheaper models](https://git.drupalcode.org/project/ai_context/-/work_items/3586221) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem/motivation The Chicago Driesnote demo videos were recorded with Open AI for Vector DB and Opus 4.6 for everything else. Opus 4.6 is expensive. It can cost $1 to $2 USD to create a page. We want to see if cheaper models can produce okay results. ## Solution Test with smaller/cheaper models and post results. ## Tasks - [ ] Set up demo environment - [ ] Test with 2 or 3 cheaper/smaller models - [ ] Post results ### [Gather CCC contribution stats for code and non-code contributions for release notes](https://git.drupalcode.org/project/ai_context/-/work_items/3586222) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Sprint 10, category::task, priority::normal, sprint candidate Description: ## Problem/motivation The current tools for generating release notes are inadequate as they only focus on code commits. They also require the issue number to be in the commit message. I want to gather the stats for all contributors for a release including non-code contributions which there are many. ## Solution The result for release notes should be something like: ``` New Features * one * two Bug Fixes * one * two Tasks * one * two Non-Code Contributions * number of issues? Contributors: kristen pol (35), afoster (8), emma horrell (6), scott falconer (6), mglaman (3)... salsa (35),… ### [(Discuss) Add boundaries / exclusions to scope plugins](https://git.drupalcode.org/project/ai_context/-/work_items/3586197) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Sprint 10, category::task, priority::normal Description: ## Problem/motivation Follow-up to: #3586195 Boundaries / exclusions were discussed quite a bit in the past, but hasn't been implemented yet. Example context item: - Tone and voice - Scope - Use case = Writing Words - Entity bundle = exclude for Support Notes (content type) Translation: The context will be applicable to any agent subscription with use case = writing words unless it's a node that's a Support Notes content type ## Solution Add an exclusion option for each scope item and bake that into the logic Could be a dropdown per scope item: - None (neutral/default) - Include… ### [Create CCC status update video](https://git.drupalcode.org/project/ai_context/-/work_items/3586154) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Create a video on the current status of CCC and what's coming up. ### [Address todos in CCC subscription update logic and scope visibility in tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586111) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Subscription update logic and scope visibility (2 tests) The first test verifies that editing one agent's subscriptions doesn't clobber anoth… ### [Address todos in CCC empty scope / subscription handling tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586110) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Empty scope / subscription handling (2 tests) Empty or cleared scope selections are a normal user action. If this isn't handled gracefully it… ### [Stabilize global context item ordering before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586189) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3582504 **Description:** Global context items are capped in first-seen/ascending-ID order. When `max_global_items` is reached, older or earlier-loaded items win arbitrarily, which makes the selected global context depend on creation/load order rather than an intentional ranking. Before RC1, global item selection should be deterministic and documented. Global items should be sorted by an intended ordering before applying `max_global_items`, preferably most recently changed first with an ID tie-breaker. **Scope:** - Sort global context items deterministically before applyin… ### [Clean up CCC inconsistences and DX issues before rc1 (part 1)](https://git.drupalcode.org/project/ai_context/-/work_items/3586147) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Back and forth with opus 4.6 to review inconsistencies and DX issues: See MD file: [ai-context-naming-dx-review.md](https://git.drupalcode.org/-/project/191993/uploads/bdc9625673e049cdd31d2f0653de3ccd/ai-context-naming-dx-review.md) ## Handled in this issue (part 1) The ones that are addressed in this MR are: Addressed from `reviews/ai-context-naming-dx-review.md`: - **1c: Orphaned form**: deleted `AiContextScopeSiteSectionForm` - **2d: Missing `declare(strict_types=1)`**: added to `DiffHooks.php` and `AiContextUninstallValidator.php`; `DynamicEntityReferenceHooks.php` already had it - *… ### [Fix custom path matching for site section scope](https://git.drupalcode.org/project/ai_context/-/work_items/3586158) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, AI Sprint 9, category::bug Description: Follow up to: #3582504 **Description:** The site-section scope supports custom path values such as `custom:/products/*`, but the selection pipeline currently relies on the base scope matching logic, which only compares the detected section ID to stored scope values. As a result, custom path patterns may never match during context selection. **Scope:** - Override `matchesCurrentContext()` in the site-section scope plugin. - Match both configured section IDs and `custom:` path patterns against the current path. - Preserve existing behavior for items with no site-section values. - Add tests fo… ### [Configure GitLab metadata for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586142) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Go through and review the metadata available and remove anything that's not needed and decide if anything should be added. ### [Address todos in CCC taxonomy entity type dependency in kernel tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586109) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Taxonomy entity type dependency in kernel tests (2 tests) `getAllScopeValues()` is a core API method used by the scope system. The fix is lik… ### [Design for the Context Item single entity view (manual/markdown/text/static)](https://git.drupalcode.org/project/ai_context/-/work_items/3586141) State: closed | Updated: 2026-05-10 | Author: Aidan Foster (aidanfoster) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Step 1: Mockups x 2 (Update the Context Item entity view (/admin/ai/context/items/{id}) to match modern admin patterns and improve editing continuity. Wrap the entire entity view in a white card frame to match the markdown editor treatment. The current state has the form on a tinted background and the editor on white, which creates two competing visual zones. Add a right sidebar with navigation to the parent Context Item and sibling Context Items. For example, from "Content Structure: Product Pages," the sidebar should link to "Articles & Blogs," "PPC Landing Page," and "Press Releases." O… ### [Design for the Context Item single entity view (connected/remote/dynamic)](https://git.drupalcode.org/project/ai_context/-/work_items/3586224) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: This was split off from: #3586141 to focus on Connected Context. ## Step 1: Mockup From original issue: For Connected Context items, add sync metadata to the sidebar: last synced (relative time), next sync, sync status, sync schedule with edit link, a manual "Sync now" button, and source freshness from the external system when available. ## Step 2: Review, discuss and iterate. ## Step 3: Create follow-up issue to implement. ### [Design Improved Context Items List View](https://git.drupalcode.org/project/ai_context/-/work_items/3586140) State: closed | Updated: 2026-05-10 | Author: Aidan Foster (aidanfoster) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ### Step 1: Update Context Items List view to see impact of proposed changes. 1. Resolve "Add AI Context Item" button label inconsistency with "Context Items" page title (recommend dropping "AI" from the button) 2. Update tooltips or text labels to Type column icons. 3. Add source badge next to each item (manual / file / connector) 4. Add column sorts 5. Figure out how to show token usage ### Step 2: Discuss / Review Done ### Step 3: Create Follow-up Issues Done ### [Fatal errors when uninstalling CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586223) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Fatal errors when uninstalling CCC (1.0.x). ### First error 1. Install on CMS 2.1 2. Don't add anything 3. Uninstall 4. Error ``` In ExceptionHandler.php line 96: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'db.ai_context_usage' doesn't exist: SELECT "base_table"."id" AS "id", "base_table"."id" AS "base_table_id " … ### [Address todos in scope form rendering and persistence tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586108) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) ### Scope form field rendering and persistence (7 tests) This test cluster is broader than language scoping. It verifies that scope fields render and persist correctly across both context item forms and agent configuration forms, including language, use case, site section, and tag scopes. The original failure looked language-related because language fields only render as checkboxes on multilingual sites. On single-language sites, production code intentionally shows an informational message instead. The… ### [Normalize token/item limit naming — eliminate `tokenBudget` and align on `maxTokens`/`maxItems`](https://git.drupalcode.org/project/ai_context/-/work_items/3586146) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow-up to: #3584838 Went back and forth with opus 4.6 on this: --- **Problem:** The concept "maximum tokens for rendered context" uses three different names as it flows through the codebase: - Public API: `tokenLimit` (`retrieve(tokenLimit: 2000)`) - Request DTO: `maxTokens` (`$request->getMaxTokens()`) - Result VO: `tokenBudget` (`$result->getTokenBudget()`) Similarly for items: - Public API: no public param yet - Request DTO: `maxItems` (`$request->getMaxItems()`) - Config: `max_items` The `tokenBudget` naming is the main inconsistency — it implies allocation planning rather than… ### [Allow AI Context provider/model setting to be explicitly unset](https://git.drupalcode.org/project/ai_context/-/work_items/3586190) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::feature, priority::normal, what::code, why::wontFix Description: Handling this in: #3586159 **Description:** The AI Context general settings page currently uses the AI provider configuration element for `AI Provider/Model`. When no module-specific provider/model is saved, the element visually falls back to the AI module’s core default provider. This makes it look like AI Context has a provider configured and does not give administrators an obvious way to explicitly unset provider/model for AI Context. AI Context should support an explicit “No provider” state so conditional subcontext can be disabled intentionally unless a provider/model is configured f… ### [Document subcontext entity validation rules for RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586185) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** AI Context now enforces subcontext integrity at the entity validation layer through `AiContextItemIntegrity` / `AiContextItemValidator`. This is the desired behavior for RC1, but the docs should explicitly describe the persistence contract. Document that: - A context item cannot be its own parent. - Subcontext hierarchies are limited to one level. - An item with children cannot become a subcontext itself. - `subcontext_type` is required when a parent is selected. - Parent deletion clears child `parent` and `subcontext_type` references. - These rule… ### [Test CCC using DrupalForge DrupalCon Chicago Driesnote template](https://git.drupalcode.org/project/ai_context/-/work_items/3586152) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: We have this now: https://www.drupalforge.org/template/driesnote-chicago Test this out to make sure it works as expected. ### [Create CCC example module that adds scope plugin and extends existing plugins](https://git.drupalcode.org/project/ai_context/-/work_items/3571354) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation In order to see how scope plugins work, it would be helpful to have a code example. Proposed resolution Create example module that adds scope plugin and extends existing plugins It should create a scope plugin as … ### [Test CCC on Drupal CMS 2.1](https://git.drupalcode.org/project/ai_context/-/work_items/3586193) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Test CCC on latest version of Drupal CMS 2.1 ### [Long context items are skipped instead of truncated when max token limit is reached](https://git.drupalcode.org/project/ai_context/-/work_items/3586191) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Found this while testing: #3586160 **Description:** When a selected AI Context item is longer than the configured max token budget, the renderer may exclude the item entirely instead of truncating its guidance content to fit. This happens because token limiting is applied before the item metadata wrapper is added, and the full rendered block can still exceed the budget after wrapping. Expected behavior: oversized context item content should be truncated when possible so the item can still be injected within the token limit. The item should only be skipped if its required metadata wrapper… ### [Add `AiContextSelectorInterface` before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586184) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** `AiContextSelector::select()` is the primary programmatic API for selecting and rendering AI Context items. Before RC1, this should be exposed through an interface so contrib modules and custom integrations can depend on a stable contract instead of the concrete service class. Proposed scope: - Add `Drupal\ai_context\Service\AiContextSelectorInterface`. - Define `select(AiContextRequest $request): AiContextResult`. - Have `AiContextSelector` implement the interface. - Add a service alias for the interface in `ai_context.services.yml`. - Update inter… ### [ai_context overview CSS references missing external.svg asset via bad relative path](https://git.drupalcode.org/project/ai_context/-/work_items/3586143) State: closed | Updated: 2026-05-10 | Author: scott falconer (scottfalconer) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: - Problem: Loading /admin/ai/context/overview records a missing asset request. - Evidence: request goes to /modules/contrib/contrib/ai/assets/ icons/external.svg - Likely source: web/modules/contrib/ai_context/css/ ai_context_overview.css - Current CSS path: ../../contrib/ai/assets/icons/external.svg - Actual asset exists at: web/modules/contrib/ai/assets/icons/ external.svg - Expected: overview loads without 404/watchdog noise. - Actual: browser/watchdog records missing asset. - Suggested fix area: correct the relative CSS URL or avoid reaching through anothe… ### [Set default usage record retention to 90 days](https://git.drupalcode.org/project/ai_context/-/work_items/3586186) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** Usage records are useful for auditability and debugging, but they may expose prompt/task behavior and can grow over time. Before RC1, the module should ship with conservative default retention settings. Recommended defaults: - Keep usage tracking enabled by default. - Set `usage_max_age` to `7776000` seconds, 90 days. - Keep `usage_max_records` at `10000` as a safety cap. - Keep cron pruning batched. - Update the usage settings form fallback to match install config. - Ensure config schema and tests continue to cover these settings. This makes the … ### [(Discuss) Logic for multiple context scope items being handled separately](https://git.drupalcode.org/project/ai_context/-/work_items/3586195) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation I was testing in prep for beta1 and noticed this behavior which I think is okay, but I want to talk with the UX team about it. 1. Context item is scoped to use case (writing words) and entity bundle (article) 2. Agent scope subscriptions are use case (writing words), tag (foobar), site section (foobar), and entity bundle (blog) In this case, the context item is injected into the agent's prompt. This is because they both have use case = writing words. Let's discuss if scope should be handled like this. I think it makes sense. ## Next steps - Discuss - If necessary, m… ### [[Discuss] Conditional subcontext logic](https://git.drupalcode.org/project/ai_context/-/work_items/3586194) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3586149 ## Problem The conditional subcontext work was merged a day before beta1 was tagged as part of a huge rewrite of the selection logic. It wasn't thoroughly tested, so we need to do that. Aidan did do some testing as part of the Driesnote test cases but that was before this was merged. ## Use cases 1. Create parent + child but author didn't include any information about the child in the parent and see if it picks up the child without the extra guidance 2. Create parent + child but author did add information in the parent about the child and see if it picks up the chi… ### [CCC beta2 codebase review](https://git.drupalcode.org/project/ai_context/-/work_items/3586202) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Beta2 will be released shortly. We continually need to check the codebase as it changes for potential security issues, performance issues, and any pre-rc1 features/apis that need to be addressed. ## Solution Run AI checks against the codebase to identify for pre-rc1 and post-1.0: - Important performance issues - Important feature/API gaps - Security issues (these will not be reported here) ## Next steps - Run security review - Run performance review - Run api/feature review - Attach findings for here (not security) - Create follow-up issues as needed ### [Sprint 9 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3586183) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and estimates on release timing. --- ## Proposed resolution - Go through all issues and prioritize - Identify what goes into the next sprint - Identify candidates for future sprints - Add new issues as needed - Update roadmap meta with latest info --- ## Target date or deadline 2 May to 16 May 2026 --- ## Remaining tasks - Go through all issues and prioritize - Figure out what's in the next sprint - Figure out candidates for future sprints - Add new issues as needed … ### [Require provider for conditional subcontext before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586159) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3582504 **Description:** Conditional subcontext currently includes all conditional children when no AI provider/model is configured. This can unexpectedly expand token usage and makes conditional behavior observable even though the provider-dependent selection mechanism is unavailable. Before RC1, conditional subcontext should require an explicitly configured AI Context provider/model. Users should not be able to newly select conditional subcontext without a provider/model, and the UI should clearly explain why the option is unavailable with a link to the global AI Context … ### [Sprint 6 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3582536) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and a estimates on release timing. Proposed resolution Go through all issues and prioritize, figure out what's in the next sprint an… ### [Fix local ./lint.sh stylelint script errors for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3576094) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !118 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have a ./lint.sh script in the module that people can run to check for issues before committing. Right now, the pipeline is clean with no stylelint errors, but when I run ./lint.sh locally, I g… ### [Review CCC todo comments for action items](https://git.drupalcode.org/project/ai_context/-/work_items/3586091) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Here are the todo comments in the code which need to be reviewed to see if any should happen before rc1: ./tests/src/Functional/AiContextScopeContextItemFormTest.php: * @todo Fix language scope form fi… ### [Drupal Developer Days CCC contribution planning](https://git.drupalcode.org/project/ai_context/-/work_items/3583319) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Drupal Developer Days is April 22-25, 2026, and they would have people who could help with CCC during the event. This issue is for planning issues that could be tackled there, ideally focused on reviews, testing, … ### [Add regular CCC contributors as GitLab reporter members](https://git.drupalcode.org/project/ai_context/-/work_items/3586139) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::bug Description: With the cutover to GitLab, people can't edit metadata or issue summaries unless they are a "member" in GitLab for the project. The simplest role is "reporter". Go through and add regular contributors as "reporter" members so they can continue to collaborate. FEEL FREE TO COMMENT ON THIS ISSUE IF YOU NEED ACCESS ASAP. IT WILL TAKE SOME TIME TO GATHER EVERYONE AND GET PEOPLE ADDED. I'm creating a list here: https://docs.google.com/spreadsheets/d/1fqnpQYl9SsxkIe2iTFKExYY-ojAyxXAwuLdWdACHQ-g/edit?usp=sharing ### [CCC beta testing at Drupal Dev Days (DDD) 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3585917) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation This issue is for testing CCC at Drupal Dev Days. Multiple people can do this at the same time, so you don't have to assign this issue to yourself. Or, if it is assigned to someone else, you can still also test it… ### [Still getting GitLab CI timeouts for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586138) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !123 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Getting timeouts like this: https://git.drupalcode.org/project/ai_context/-/jobs/9459792 The script exceeded the maximum execution time set for the job Proposed resolution Figure out how to fix Ta… ### [Remove Scheduler content moderation integration CCC patch once a new release is available](https://git.drupalcode.org/project/ai_context/-/work_items/3586090) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !121 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have this patch: "extra": { "patches": { "drupal/scheduler_content_moderation_integration": { "I… ### [Sprint 8 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3585850) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and a estimates on release timing. Proposed resolution Go through all issues and prioritize, figure out what's in the next sprint an… ### [CCC Chicago planning](https://git.drupalcode.org/project/ai_context/-/work_items/3577670) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, Chicago2026 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Planning issue for DrupalCon Chicago Proposed resolution Before Chicago #3567570: [META] Context Control Center MVP demo #3577087: CCC MVP Demo: Finalize FinDrop context #3577661: CCC Chicago session slides #35776… ### [Increase gitlab ci timeout for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3582562) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, category::task, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !112 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Getting timeouts like this: https://git.drupalcode.org/project/ai_context/-/jobs/9180630 The script exceeded the maximum execution time set for the job Proposed resolution Increase the timeout Ta… ### [Fix PHPStan errors in CCC after 2.1.45 release](https://git.drupalcode.org/project/ai_context/-/work_items/3582544) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !111 >>> Overview Fix PHPStan errors in HEAD after 2.1.45 release in CI Proposed resolution Ignore or fix items User interface changes > Related issue: [Issue #3582335](https://www.drupal.org/node/3582335) ### [Update context listing to not use target column](https://git.drupalcode.org/project/ai_context/-/work_items/3586116) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation This issue makes target entities scope optional: #3577428: Update context item target entities for progressive enhancement And the context list isn't consistent with the agent context settings page (see screenshot… ### [Update context list to show workflow state](https://git.drupalcode.org/project/ai_context/-/work_items/3586127) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::feature Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3577425: [Discuss] Possible styling updates for context listing We lost the publishing status when the context list page was redone. We need to know the moderation state. Proposed resolution Update … ### [CCC QA scripts for 1.0 testing](https://git.drupalcode.org/project/ai_context/-/work_items/3586226) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: blocker::stable, category::task, mvp, needs prioritization Description: ## Problem/motivation Need to make sure we're ready for the QA team to do pre-1.0 testing. ## Solution From Bruna Emerich (Zoocha): Documentation covering the functionality, along with a test script (such as the example in this ticket, where an .md file is included), is sufficient for us to carry out testing. If any questions come up, we’ll raise them directly in the channel and tag you. Regarding lead time, it depends on the size of the functionality, but generally one week’s notice is sufficient. If there’s a fixed release date, allowing around 14 days is preferable, as it gives enough … ### [Full QA of CCC in prep for 1.0](https://git.drupalcode.org/project/ai_context/-/work_items/3573716) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: blocker::stable, category::task, mvp, needs prioritization Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We are getting close to creating an alpha or beta version and want to take a step back and do a full QA review before doing so. Proposed resolution Testing various features and finding bugs that would be good to f… ### [Create CCC rc1 release](https://git.drupalcode.org/project/ai_context/-/work_items/3586151) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Innovation, category::task, mvp Description: Problem/Motivation Create CCC rc1 release Tag: 1.0.0-rc1 Proposed resolution Create the release once at least the must-haves are done here: #3585902: CCC beta2 release planning Target date or deadline June 2026 Remaining tasks Wait on must-haves Tag code Create the release in UI Celebrate! AI usage (if applicable) [ ] AI Assisted Issue This issue was generated with AI assistance, but was reviewed and refined by the creator. [ ] AI Assisted Code This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision. [ ] AI Generated Code This… ### [Move scheduler feature to submodule or progressive enhancement](https://git.drupalcode.org/project/ai_context/-/work_items/3577429) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Matt Glaman (mglaman) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !92 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3569967: [Discuss] Figure out which CCC features can be optional for MVP We are trying to reduce the number of dependencies for ai_context. The scheduler is one dependency that not e… ### [Remove AiContextItemType](https://git.drupalcode.org/project/ai_context/-/work_items/3584775) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, blocked Description: >>> [!note] Migrated issue Reported by: [mglaman](https://www.drupal.org/user/2416470) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation I don't get why context items have a bundle. I think the only reason is for Scheduler support. That entire concept is also being discussed in #3577429: Move scheduler feature to submodule or progressive enhancement… ### [Fix eslint errors in GitLab UI even when pipeline is green](https://git.drupalcode.org/project/ai_context/-/work_items/3576093) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, blocked Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !99 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Although the pipeline passes with no eslint issues, there are still failures shown on the test summary, e.g. https://git.drupalcode.org/project/ai_context/-/merge_requests/71 Test summary: 3 failed… ### [Update context listing page per new design](https://git.drupalcode.org/project/ai_context/-/work_items/3586219) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Aidan Foster (aidanfoster), Eric Homanchuk (erichomanchuk) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Follow-up to: #3586140 There is a new design for the context listing page based on UX review and feedback. ## Solution 1. Type: Manual => Text 2. Subcontext type icon needs to pass contrast checker 3. Tokens in own column is good 4. No icon for yellow (medium) and grey (low) token numbers 5. Warning icon for red (high) token numbers 6. No info icon after context items 7. Scope column is good 8. Keep use cases column separated 9. Target => scope (but minimize what's shown) 10. Updated => Status (draft/published/unpublished) 11. Target dropdown => Scope dropd… ### [Inject context into ai_ckeditor requests](https://git.drupalcode.org/project/ai_context/-/work_items/3581955) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: >>> [!note] Migrated issue Reported by: [jessehs](https://www.drupal.org/user/620440) Related to !116 >>> Problem/Motivation The ai_context module cannot inject scope-matched context items into ai_ckeditor AI requests because ai_ckeditor bypasses the ai_agents pipeline (and its BuildSystemPromptEvent) entirely — it calls the AI provider directly in its own streaming controller. There is no event or hook point for ai_context to intercept. This issue is the ai_context companion to the ai_ckeditor entity context and event extensibility work tracked in the drupal/ai module issue queue. … ### [Clean up follow-ups from target entity decoupling review](https://git.drupalcode.org/project/ai_context/-/work_items/3586082) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> **Problem/Motivation** There was out-of-scope feedback on: #3577428 Feedback (PDF) Feedback (MD) **Description:** Follow up on the non-blocking items identified during the target entity / DER decoupling review. The MR made `dynamic_entity_reference` optional successfully, but a few cleanup tasks remain to reduce optional dependency coupling, improve documentation, and tighten safer render/input patterns. **Tasks:** - Remove the `DynamicEntityReferenceItem` import/reference from `AiContextItem:… ### [Improve config validation and use #config_target for settings form](https://git.drupalcode.org/project/ai_context/-/work_items/3580910) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [svendecabooter](https://www.drupal.org/user/35369) Related to !107 >>> [Tracker] Update Summary: `ai_context.settings` config validation Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation AiContextSettingsForm uses #default_value with manual $config->get() calls and a manual submitForm() that sets each config value individually. Validation for numeric fields (max_global_items,… ### [Can't Apply Scheduler Patch](https://git.drupalcode.org/project/ai_context/-/work_items/3579841) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, blocker::beta Description: >>> [!note] Migrated issue Reported by: [robloach](https://www.drupal.org/user/61114) Related to !102 >>> [Tracker] Update Summary: Created the issue Check-in Date: 03/17/2026 Blocked by: Additional Collaborators: @robloach Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation When installing Context Control Center on a fresh site, you run into a composer error when it tries to apply the patch. Gathering patches for dependencies. This might take a minute. - Installing drupal/scheduler_content_moderation_integration (3.0.4): Extracting a… ### [Update context view page per new design](https://git.drupalcode.org/project/ai_context/-/work_items/3586220) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Eric Homanchuk (erichomanchuk) | Labels: AI Sprint 10, category::task, priority::major, sprint candidate Description: ## Problem/motivation Follow-up to: #3586141 There is a new design for the context view page based on UX review and feedback. ## Solution ### Walkthough ## Tasks - [X] Add new design comp above - [ ] Double check design issue for anything missing - [ ] Update code - [ ] Review code - [ ] Manually test ### [(Discuss) Context Connector feature](https://git.drupalcode.org/project/ai_context/-/work_items/3586216) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI UX, category::plan, post 1.0, priority::major Description: Follow up to: #3573715 ## Problem/motivation Pasted from review issue: **Connected Context** (replaces "Remote Context" / "External Context") — Defining characteristic is a synced connection to an external system, not just remote location. Industry alignment is strong: Glean, ChatGPT, Claude, Salesforce, HubSpot, Notion, and Airtable all use Connector / Connected language for this pattern. A **Context Connector** is the platform-specific integration plugin that enables Connected Context as a source type. I need to install the "Google Analytics Context Connector" Detailed feedback on Cont… --- MERGE REQUESTS (24h) --- ### [Issue #3586227: CCC navigation icon missing due to menu changes.](https://git.drupalcode.org/project/ai_context/-/merge_requests/149) State: merged 2026-05-11 | Author: Kristen Pol (kepol) | Branch: 3586227-d11-icon | 52 diff lines Description: Closes #3586227 ### [Issue #3586227: Fix navigation icon.](https://git.drupalcode.org/project/ai_context/-/merge_requests/148) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586227-ccc-navigation-icon | 41 diff lines Description: Closes #3586227 ### [Issue #3586108: Add language tests.](https://git.drupalcode.org/project/ai_context/-/merge_requests/137) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586108-langage-todos | 466 diff lines Description: Closes #3586108 ### [Issue #3586223: Fatal errors when uninstalling CCC.](https://git.drupalcode.org/project/ai_context/-/merge_requests/147) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586223-fatal-uninstall-erro | 743 diff lines Description: Closes #3586223 ### [Issue #3586150: Add ai_context_site_architecture submodule with MCP resource provider.](https://git.drupalcode.org/project/ai_context/-/merge_requests/146) State: opened | Author: George Kastanis (zorz) | Branch: 3586150-site-architecture | 6499 diff lines Description: Resolves #3586150. ## Summary Adds **`ai_context_site_architecture`** — a submodule that auto-harvests "site behavior contracts" describing what owns each surface on a Drupal site (entity routes, Views, path aliases, pathauto patterns, ECA rules, field definitions, content moderation workflows, module state) and writes them into CCC as drafts for human review before they reach AI agents. Plus an optional **`ai_context_site_architecture_mcp`** sub-submodule that exposes the same contracts as MCP resources at `drupal://site/contracts/{contract_id}`, so MCP-aware agents (Claude Code, Cursor, e… ### [Issue #3586157: Improve selection performance.](https://git.drupalcode.org/project/ai_context/-/merge_requests/141) State: opened | Author: Kristen Pol (kepol) | Branch: 3586157-select-performance | 688 diff lines Description: Closes #3586157 ### [Issue #3586160: Add agent schema fields.](https://git.drupalcode.org/project/ai_context/-/merge_requests/134) State: opened | Author: Kristen Pol (kepol) | Branch: 3586160-per-agent-selection | 1331 diff lines Description: Closes #3586160 ### [Issue #3586161: Add entity schema fields.](https://git.drupalcode.org/project/ai_context/-/merge_requests/133) State: opened | Author: Kristen Pol (kepol) | Branch: 3586161-entity-schema | 371 diff lines Description: Closes #3586161 ### [Issue #3586162: Add post_select and post_render selection events.](https://git.drupalcode.org/project/ai_context/-/merge_requests/131) State: opened | Author: Kristen Pol (kepol) | Branch: 3586162-add-selection-events | 816 diff lines Description: Closes #3586162 ### [Issue #3586150: Add site architecture context source.](https://git.drupalcode.org/project/ai_context/-/merge_requests/126) State: opened | Author: scott falconer (scottfalconer) | Branch: 3586150-add-site-ar | 13094 diff lines Description: Work item: https://git.drupalcode.org/project/ai_context/-/work_items/3586150 Adds the ai_context_site_architecture submodule as a CCC-governed Drupal site behavior contract generator. Summary: - Compiles Drupal surfaces into structured site behavior contracts. - Keeps MCP optional while producing MCP-ready resource payloads. - Adds CCC draft writing, Drush export, schema docs, resource template support, and tests. - Refactors generation behind collector and post-processor services. Validation run locally: - PHP 8.3 syntax lint across modules/ai_context_site_architecture/src and tests/src: … ### [Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools.](https://git.drupalcode.org/project/ai_context/-/merge_requests/116) State: opened | Author: Jesse Hofmann-Smith (jessehs) | Branch: 3581955-inject-context-into | 339 diff lines Description: Closes #3581955 ### [Issue #3580910: Use proper config validation and #config_target for ai_context.settings.](https://git.drupalcode.org/project/ai_context/-/merge_requests/107) State: opened | Author: Sven Decabooter (svendecabooter) | Branch: 3580910-improve-config-validation | 252 diff lines Description: Closes #3580910 ### [Issue #3577429: Move scheduler feature.](https://git.drupalcode.org/project/ai_context/-/merge_requests/92) State: opened | Author: axioteo | Branch: 3577429-move-scheduler-feature | 1045 diff lines Description: Moves scheduler functionality into a submodule, and if enabled, sets by default the scheduling options to false. Closes #3577429 ### [Issue #3574937: Review and update CCC permissions.](https://git.drupalcode.org/project/ai_context/-/merge_requests/78) State: opened | Author: Ann Mary Sruthy (annmarysruthy) | Branch: 3574937-review-and-update | 271 diff lines Description: Closes #3574937 ### [Issue #3586145: Handle removed scope values.](https://git.drupalcode.org/project/ai_context/-/merge_requests/132) State: opened | Author: Kristen Pol (kepol) | Branch: 3586145-stale-scope-values | 867 diff lines Description: Closes #3586145 ### [Issue #3586082: Clean up after der decoupling.](https://git.drupalcode.org/project/ai_context/-/merge_requests/145) State: opened | Author: Kristen Pol (kepol) | Branch: 3586082-clean-up-follow-ups | 223 diff lines Description: Closes #3586082 --- COMMITS (24h) --- - [a13c90c7](https://git.drupalcode.org/project/ai_context/-/commit/a13c90c74b2d8f358a602d6251286d83322c9dbd) Issue #3586227: CCC navigation icon missing due to menu changes. — Kristen Pol (2026-05-11T00:36:04.000+00:00) - [3a7ce43d](https://git.drupalcode.org/project/ai_context/-/commit/3a7ce43d9c6c7a14c0aa355845986e93913d5744) Issue #3586227: Fix navigation icon. — Kristen Pol (2026-05-10T20:19:53.000+00:00) - [0c5920b6](https://git.drupalcode.org/project/ai_context/-/commit/0c5920b600f9624d44cb82a3b6afb3f4fd048d5d) Issue #3586108: Add language tests. — Kristen Pol (2026-05-10T16:21:59.000+00:00) - [9cd9f210](https://git.drupalcode.org/project/ai_context/-/commit/9cd9f210b2846da9cc5f59d52eee4e027b0aabda) Issue #3586223: Fatal errors when uninstalling CCC. — Kristen Pol (2026-05-10T16:21:02.000+00:00) ======================================================================== ## [6] generateTldr:developer ======================================================================== You are an editor distilling a Drupal AI project newsletter into its most important highlights. You are writing for a technical developer audience. Be specific — name modules, merged features, and critical bugs. Read all the module summaries below. Separate the highlights into two categories: - SHIPPED: things that were merged, fixed, released, or completed during this period. - ONGOING: things that are actively in progress, under review, or blocked. Be specific — name the module, what happened, and why it matters. Do not use emoticons or mdashes. Do not include any text outside the two sections. Do not mention issue numbers (e.g. #12345) or MR IDs (e.g. !42) — they are not linked and are meaningless to readers out of context. Instead, describe what was done in plain language. Format as two HTML sections. Use exactly this structure (all
elements must be inside the
, never outside it):
Shipped

Title here — One sentence explanation.

Another title — One sentence explanation.

Ongoing

Title here — One sentence explanation.

Up to 5 items per section. Do not output any text, tags, or characters outside these two sections. Output only the HTML fragment, no surrounding tags. --- MODULE SUMMARIES ---
AI (Artificial Intelligence)

Bug Fixes and New Issues

Pieter Frenssen (pfrenssen) filed and submitted a fix for a newly reported crash: TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields. The root cause is that getAutomatorsOptions() requires a $bundle argument, which is not available for base fields since they apply to all bundles, causing a fatal TypeError when isAvailable() is called. The accompanying fix MR includes a new kernel test, AiAutomatorsBaseFieldTest, and is awaiting review.

In-Progress Sprint Work

Several AI Initiative Sprint items saw activity. The Move Automators to Structured Output MR from Ann Mary Sruthy (annmarysruthy) remains open at 1,819 diff lines, replacing pseudo-JSON output in ai_automators with a structured output approach. Two parallel MRs -- from Anjali Prasannan (AnjaliPrasannan) and a rebase variant from Marcus Johansson (Marcus_Johansson) -- address Use the provider configuration element for Automators, migrating away from AiProviderFormHelper. Bruno Bruno (bbruno) posted a large MR (6,722 diff lines) adding a React-based default tools editor for agents, with YAML/interactive tab switching and tool autocomplete. The update hook naming convention documentation MR from Avinash jha (avinash.jha) is a small 24-line change awaiting merge. No commits landed in the reporting period.

How can I help on this project?

Review the base field TypeError fix MR -- it has tests and manual instructions ready, and just needs a code review to merge.

The Move Automators to Structured Output issue is unassigned; review the open MR or help reconcile the two competing provider configuration element MRs.

Pick up the unassigned update hook naming documentation review -- it is a trivial merge candidate.

---
Drupal AI Initiative

Activity in the last 24 hours was light, with no merged MRs or commits landing during the reporting period. Two new issues were filed by Kristen Pol (kepol) around the Chicago Driesnote demonstration repository at https://github.com/fosterinteractive/c2026/, which is used for live AI CMS comparison demos.

Chicago Driesnote Demo Work

The Update Chicago Driesnote repo to include demo prompts issue is open and unassigned, requesting that prompt content be extracted from an internal Google doc and committed to the repo as a Markdown file. Separately, Fix RAG search on Chicago Driesnote repo install is assigned to Kristen Pol (kepol) and tracks a broken RAG search experience on fresh installs -- the fix may land as either a config change or updated README instructions. Neither issue has a corresponding MR yet, and no root cause for the RAG failure has been identified publicly.

How can I help on this project?

A developer could make an immediate contribution in one of these ways:

Clone the fosterinteractive/c2026 repo, attempt a fresh install, and diagnose the RAG search failure described in Fix RAG search on Chicago Driesnote repo install.

Pick up the unassigned Update Chicago Driesnote repo to include demo prompts task and open an MR adding a PROMPTS.md file.

---
Unstructured

Activity on the Unstructured module over the last 24 hours was limited to a single open merge request. Ahmad Khader (Ahmad-Khader) opened Resolve #3582438 "Create document loader", a substantial contribution spanning 1,989 diff lines aimed at introducing a document loader component to the module. The MR remains open and unmerged, with no associated commits landing in the reporting period and no issue comments recorded.

No bugs were fixed, no APIs were merged, and no blockers were explicitly documented during this window. The size of the MR suggests it likely introduces significant new functionality, and it will need thorough review before it can land.

How can I help on this project?

Review Resolve #3582438 "Create document loader" -- at nearly 2,000 diff lines it needs eyes on architecture, API design, and coding standards compliance.

Write or suggest tests to cover the new document loader logic introduced in that MR.

---
Drupal Canvas

Active Development

No commits landed in the reporting period, but significant MR activity is underway around two related problem areas: multi-value field handling and symmetric content inputs for translation.

Two MRs from Shubham Prakash (shubham.prakash) were closed: one targeting a FormattedText component rendering issue (Issue #3588450) and one addressing re-adding a multi-value field (Issue #3587472). The latter was flagged as AI-assisted and appears to have been superseded by work from Ben Mullins (bnjmnm), who has opened three separate MRs against the same issue: a test-plus-original-fix variant, a backend widget solution, and a test-only MR. This split suggests active investigation into the right fix strategy for the multi-value re-add regression. A large post-multivalue reroll draft (8,546 diff lines) from bnjmnm also remains open.

Separately, Ted Bowman (tedbow) has a draft open for symmetric content inputs, bringing translation parity between content and config entity component trees via tmgmt_content integration. A known issue with relative internal links (internal:/about) is noted in the description.

How can I help on this project?

Review the three competing MRs for Resolve #3587472 "Backend Widget solution" and provide feedback on which approach is preferable. You could also run the test suite against the test-plus-fix MR, or investigate the relative internal link rendering bug noted in the symmetric content inputs draft.
---
Context Control Center (CCC)

Sprint 9 wrapped up with a flurry of merges during the reporting period as the project transitions into Sprint 10 with RC1 targeting June 2026. Kristen Pol (kepol) landed four commits to the 1.x branch.

Merged and Shipped

Two back-to-back fixes addressed CCC navigation icon missing due to menu changes, caused by CSS path breakage introduced in the DX cleanup pass; both MR 149 and the earlier MR 148 were merged. Fatal uninstall errors on a clean Drupal CMS 2.1 instance -- a missing ai_context_usage table causing SQL crashes in AiContextUninstallValidator -- were resolved via MR 147, closing Fatal errors when uninstalling CCC. Language scope form tests were also added in MR 137, closing out Address todos in scope form rendering and persistence tests.

Open MRs Awaiting Review

Several substantial MRs are queued. Two competing approaches to Add Site Architecture context source for Drupal site behavior contracts are open simultaneously: MR 146 from George Kastanis (zorz) adds an ai_context_site_architecture submodule with an optional ai_context_site_architecture_mcp layer (6,499 diff lines), while MR 126 from scott falconer (scottfalconer) takes a collector/post-processor service approach (13,094 diff lines). These need reconciliation before either can merge. Other open MRs cover selection performance improvements, per-agent and entity schema fields, post_select and post_render events, CKEditor context injection from Jesse Hofmann-Smith (jessehs), config validation using #config_target from Sven Decabooter (svendecabooter), scheduler submodule extraction assigned to Matt Glaman (mglaman), and permissions review from Ann Mary Sruthy (annmarysruthy).

Blockers

Remove AiContextItemType and Fix eslint errors in GitLab UI even when pipeline is green remain labeled blocked. The AiContextItemType removal is explicitly gated on the scheduler submodule work in MR 92. QA scripts for pre-1.0 testing (CCC QA scripts for 1.0 testing) are also unassigned and flagged as a stable blocker.

How can I help on this project?

Review the two competing site architecture submodule MRs (MR 146 and MR 126) and comment on which approach better fits the plugin architecture.

Pick up the unassigned CCC QA scripts for 1.0 testing issue to unblock the QA team.

Review MR 107 replacing manual config gets with #config_target in AiContextSettingsForm.

======================================================================== ## [7] summariseModule:ai:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI (Artificial Intelligence) (machine name: ai) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
AI (Artificial Intelligence)
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add event hook to ai_ckeditor to allow context injection](https://git.drupalcode.org/project/ai/-/work_items/3581952) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Jesse Hofmann-Smith (jessehs) | Labels: AI Initiative Sprint, AI Product Development, aiCkeditor, category::feature Description: >>> [!note] Migrated issue Reported by: [jessehs](https://www.drupal.org/user/620440) Related to !1469 !1425 >>> Problem/Motivation The ai_ckeditor module provides AI-powered CKEditor 5 actions (Tone, Translate, Summarize, etc.) but has zero entity awareness — it doesn't know what content type, bundle, or entity ID the editor is attached to. The ai_context module provides a sophisticated scope-based context selection system that can inject bundle-specific writing guidelines into AI prompts. These two modules cannot communicate because: ai_ckeditor does not pass entity information (… ### [Generalize behaviour of FWA with Automators](https://git.drupalcode.org/project/ai/-/work_items/3577050) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Ahmad Khader (Ahmad-Khader) | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::task Description: >>> [!note] Migrated issue Reported by: [a.dmitriiev](https://www.drupal.org/user/3235287) Related to !1283 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation At the moment each field widget action in ai_automators module (that use automators) is using its own custom code to manipulate the form element data. This leads to a lot of different approaches and doesn't always allow using mul… ### [Move Automators to Structured Output](https://git.drupalcode.org/project/ai/-/work_items/3577170) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1291 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Currently Automators is using pseudo json to create the output that is required when calling AI. This has historical reasons that are all explained here: #3565806: [Discuss] Move Automators to Structured Output. The main reas… ### [Document how update hooks should be named](https://git.drupalcode.org/project/ai/-/work_items/3578472) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, category::task, documentation Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1318 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have a little bit weird way of doing update hooks right now. We should use version name major/minor and three numbers. So the first on 1.1.x would be 11001, the second one is 11002 and so on. Then on 1.2.x it would be 1200… ### [Create JS form editor for the default information tools](https://git.drupalcode.org/project/ai/-/work_items/3577937) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, Needs UX review, aiAgent Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1490 !253 >>> Problem/Motivation Default Information Tools, are tools that loads context into the agent, before it did need to take a decision. For instance the Field Agent, needs to know what entites and bundles exists that are fieldable for almost any query. So, instead of having an expensive loop this loads this into the system prompt using a tool/function call. The problem we are having is that setting these up is quite complex, see the documentation here: https://project.pages.d… ### [Use the provider configuration element for Automators](https://git.drupalcode.org/project/ai/-/work_items/3577173) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiAutomators, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1449 !1320 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: Use the AI provider configuration form element instead of AiProviderFormHelper in AI Automators and migrate stored configuration Check-in Date: MM/DD/YYYY [/Tracker] Problem/Motivation In AI 2.0 a standardized provider selection and configuration form element was introduced for configuring AI providers. This element is documented here: AI Provider Configuration Element. The AI Automa… ### [TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields](https://git.drupalcode.org/project/ai/-/work_items/3586430) State: opened | Updated: 2026-05-10 | Author: Pieter Frenssen (pfrenssen) | Assigned: unassigned | Labels: Description: ## Summary Currently `AutomatorBaseAction::getAutomatorsOptions()` requires a `$bundle` to be passed in to retrieve the options for a field. The bundle is available for regular fields added through the field API, but base fields are not associated with a bundle (since base fields apply to all bundles). This can cause a fatal `TypeError` to be thrown when calling code cannot supply a bundle. For example when `AutomatorBaseAction::isAvailable()` is called for an automator associated with a base field. ## Steps to reproduce 1. Create an "Article" node type. 2. Enable the [Base Field Override… --- MERGE REQUESTS (24h) --- ### [feat: #3577170 Move Automators to Structured Output](https://git.drupalcode.org/project/ai/-/merge_requests/1291) State: opened | Author: Ann Mary Sruthy (annmarysruthy) | Branch: 3577170-move-automators-to | 1819 diff lines Description: Closes #3577170 ### [#3577937: add default tools editor](https://git.drupalcode.org/project/ai/-/merge_requests/1490) State: opened | Author: Bruno Bruno (bbruno) | Branch: 3577937-default-tools-editor | 6722 diff lines Description: Adds a new React app `default-tools-editor` which provides an 'Interactive' way to manipulate the `Default Information Tools` field for Agents which only takes YAML. Allowing for easier Add/Removal/Edit of different tools. Some of the features of the react app: - Ability to change tabs between YAML and the Interactive mode. So manual adjustments are still possible - Autocomplete on tool selection field, listing all available tools on the website. - Lists all available tool parameters based on the chosen tool, along with the described Help Text (description) for the expected values for that … ### [TypeError in AutomatorBaseAction::getAutomatorsOptions() when automating base fields](https://git.drupalcode.org/project/ai/-/merge_requests/1568) State: opened | Author: Pieter Frenssen (pfrenssen) | Branch: 3586430-automatorbaseaction | 257 diff lines Description: ## Description Fixes #3586430 ## Testing instructions Run `\Drupal\Tests\ai_automators\Kernel\AiAutomatorsBaseFieldTest`. Manual test instructions are in #3586430 ## Checklist - [x] I have linked the related issue in the MR title or description - [x] I have performed a self-review of my own code - [x] I have added or updated tests, or explained in the description why this change is not covered by tests - [ ] I have updated documentation for any new or changed functionality - [x] I have written testing instructions and verified them locally - [ ] I have noted any required post-merge steps… ### [Resolve #3577173 "Wrong rebase"](https://git.drupalcode.org/project/ai/-/merge_requests/1449) State: opened | Author: Marcus Johansson (Marcus_Johansson) | Branch: 3577173-wrong-rebase | 1500 diff lines Description: Closes #3577173 ### [#3577173: Use the provider configuration element for Automators](https://git.drupalcode.org/project/ai/-/merge_requests/1320) State: opened | Author: Anjali Prasannan (AnjaliPrasannan) | Branch: 3577173-use-the-provider | 1015 diff lines Description: Closes #3577173 ### [ai-3578472:3578472-document-how-update](https://git.drupalcode.org/project/ai/-/merge_requests/1318) State: opened | Author: Avinash jha (avinash.jha) | Branch: 3578472-document-how-update | 24 diff lines Description: Adds documentation explaining the update hook naming convention. Update hooks follow the pattern: ai_update_MAJORMINORNNN() Examples: ai_update_11001() ai_update_11002() ai_update_12001() Closes #3578472 --- COMMITS (24h) --- (none) ======================================================================== ## [8] summariseModule:ai_initiative:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal AI Initiative (machine name: ai_initiative) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Drupal AI Initiative
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Update Chicago Driesnote repo to include demo prompts](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586511) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Demo, AI Initiative Sprint, category::task, demos Description: ## Problem/motivation We have the repo for the Chicago Driesnote: https://github.com/fosterinteractive/c2026/ but the demo prompts aren't included. ## Solution Pull out the minimum prompt info from the "Chicago DriesNote Brainstorm / AI CMS Comparison" Google doc and add to a file in the repo. ## Tasks - Review Google doc and extract best prompt info - Add prompts to an md file in the repo ### [Fix RAG search on Chicago Driesnote repo install](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586512) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Demo, AI Initiative Sprint, category::bug, demos Description: ## Problem/motivation We have the repo for the Chicago Driesnote: https://github.com/fosterinteractive/c2026/ but RAG search wasn't working for me ## Solution Fix it in the repo or provide instructions in the readme on how to set it up. ## Tasks - Figure out fix - Update config and/or readme as needed --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [9] summariseModule:unstructured:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Unstructured (machine name: unstructured) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Unstructured
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Resolve #3582438 "Create document loader"](https://git.drupalcode.org/project/unstructured/-/merge_requests/17) State: opened | Author: Ahmad Khader (Ahmad-Khader) | Branch: 3582438-create-document-loader | 1989 diff lines Description: Closes #3582438 --- COMMITS (24h) --- (none) ======================================================================== ## [10] summariseModule:canvas:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal Canvas (machine name: canvas) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Drupal Canvas
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Draft: Resolve #3583684 "Symmetric content inputs"](https://git.drupalcode.org/project/canvas/-/merge_requests/882) State: opened | Author: Ted Bowman (tedbow) | Branch: 3583684-symmetric-content-inputs | 1071 diff lines Description: Closes #3583684 The aim here is to achieve the equivalent functionality for component trees stored in content entities as !898 does for component trees stored in config entities. It integrates with tmgmt_content Screenshots of translation form: ![tmgmt_content_multi_text](/uploads/b2883defec61bad563bb03ab9c32093c/tmgmt_content_multi_text.png){width=900 height=325} ![tmgmt_content_cta](/uploads/864471c5836067c0258b6e4f9d5ae1c1/tmgmt_content_cta.png){width=900 height=340} Relative link: This looks wrong "internal:/about" Does our widget hide. internal:/ ![tmgmt_content_multi_relative_link](… ### [Issue #3588450](https://git.drupalcode.org/project/canvas/-/merge_requests/1072) State: closed | Author: Shubham Prakash (shubham.prakash) | Branch: 3588450-formattedtext-component-renders | 47 diff lines Description: Closes #3588450 ### [Issue #3587472](https://git.drupalcode.org/project/canvas/-/merge_requests/1017) State: closed | Author: Shubham Prakash (shubham.prakash) | Branch: 3587472-re-adding-a-multivalue | 65 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 AI Assisted code ### [The original fix MR added to #3587865 - but with test added](https://git.drupalcode.org/project/canvas/-/merge_requests/1088) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-re-adding-a-multivalue-where-i-can-run-it | 24 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [Resolve #3587472 "Backend Widget solution"](https://git.drupalcode.org/project/canvas/-/merge_requests/1089) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-solution | 44 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [3587865 test only](https://git.drupalcode.org/project/canvas/-/merge_requests/1087) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3587472-test | 24 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3587472 ### [Draft: Post multivalue reroll](https://git.drupalcode.org/project/canvas/-/merge_requests/1033) State: opened | Author: Ben Mullins (bnjmnm) | Branch: post-multivalue-reroll | 8546 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR --- COMMITS (24h) --- (none) ======================================================================== ## [11] summariseModule:ai_context:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Context Control Center (CCC) (machine name: ai_context) Reporting period: last 24h (2026-05-10T05:00:02+00:00 to 2026-05-11T05:00:02+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. When mentioning contributors, use the format "Real Name (username)" when a real name is available in the data, otherwise use just the username. Format your response as an HTML fragment. Start with
Context Control Center (CCC)
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [[META] CCC MVP 1.0 roadmap](https://git.drupalcode.org/project/ai_context/-/work_items/3567798) State: opened | Updated: 2026-05-11 | Author: drupalbot | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, category::plan, mvp Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> --- ## Problem/Motivation We need a stable release of CCC to support Drupal CMS that includes a lot of the ideas and features we've been discussing, including the 1-year plan capabilities. --- ## Proposed resolution Update issue list and work through them --- ## Target date or deadline - March 23rd: Beta1 release - March 23rd to 27th: DrupalCon Chicago - May 10: Beta2 release - May TBD: Beta3 release - June TBD: RC1 release - June TBD: RC2 release - June TBD: 1.0 release --- ## Remaining task… ### [Create CCC beta2 release](https://git.drupalcode.org/project/ai_context/-/work_items/3585920) State: closed | Updated: 2026-05-11 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Create CCC beta2 release Tag: 1.0.0-beta2 Proposed resolution Create the release once at least the must-haves are done here: #3585902: CCC beta2 release planning Target date or deadline 4 May 2026 Remaining tasks … ### [Create CCC video showing how to configure it](https://git.drupalcode.org/project/ai_context/-/work_items/3586153) State: opened | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: People have been having some trouble understanding how to set up CCC. Create a simple video for setting it up. ### [CCC navigation icon missing due to menu changes](https://git.drupalcode.org/project/ai_context/-/work_items/3586227) State: closed | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation The menu changed in: #3586147 which broke the css for the icon ## Solution Update css to handle change. ## Tasks - Update code - Review and test ## AI disclosures - [ ] AI assisted issue - [x] AI generated code ### [CCC beta blog post](https://git.drupalcode.org/project/ai_context/-/work_items/3577657) State: opened | Updated: 2026-05-11 | Author: drupalbot | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need a blog post to announce CCC beta Proposed resolution Write it and run it by the marketing team Target date or deadline 1 May 2026 Remaining tasks Write blog post Review and tweak Ping marketing team for s… ### [CCC beta2 QA](https://git.drupalcode.org/project/ai_context/-/work_items/3586156) State: closed | Updated: 2026-05-11 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: > [!note] > Migrated issue > Migrated from issue #3577669 > Reported by: [kristen pol](https://www.drupal.org/user/8389) --- ## Tracker **Update Summary:** [One-line status update for stakeholders] **Check-in Date:** MM/DD/YYYY **Blocked by:** - [#XXXXXX](https://www.drupal.org/project/ai_context/issues/XXXXXX) **Additional Collaborators:** @username1, @username2 _Metadata is used by the [AI Tracker](https://www.drupalstarforge.ai/). Docs and additional fields [here](https://www.drupalstarforge.ai/ai-dashboard/docs)._ --- ## Problem/Motivation Need a QA script for beta… ### [Integrate CCC with Document Loader for MDXEditor integration](https://git.drupalcode.org/project/ai_context/-/work_items/3586228) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 10, category::feature, priority::major, sprint candidate Description: ## Problem/motivation Follow-up or perhaps a replacement to: #3569310 We want to allow users to use a source for their markdown (e.g. MD, PDF, text file, URL). Document Loader has integrated with MDXEditor to make this easy: [#3580850](https://www.drupal.org/project/document_loader/issues/3580850) This has been fixed and there's a new release (2.0.1) that includes it. Hooks were also added: [#3585786](https://www.drupal.org/project/document_loader/issues/3585786) so we can save the source. ## Solution **IMPORTANT: The integration should be done using progressive enhancement. We shoul… ### [Add webpage (URL) context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574414) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, needs prioritization, needs ux review, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3547034: [Spike] Research URL support for CCC This requires a UX discussion before we work on it. Proposed resolution Review #3547034: [Spike] Research URL support for CCC, discuss UX options, pick … ### [Add MD context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574928) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, needs prioritization, priority::normal, state::postponed Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We want to upload MD files as context. Proposed resolution Discuss, scope, and implement Target date or deadline Post-Chicago Remaining tasks Discuss and align Scope feature Update code Review and test AI usage … ### [Add PDF context source plugin to CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3574413) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, priority::normal, state::postponed, what::code Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3547035: [Spike] Research PDF upload support for CCC Ability to use PDF to source context. This requires a UX discussion before we work on it. Please take a look at comment #34 of that issue. Propos… ### [[META] Context source plugin feature (context from PDF/MD/Word/URL/etc)](https://git.drupalcode.org/project/ai_context/-/work_items/3569310) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, category::feature, needs prioritization Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !103 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We want a generic mechanism for adding context source plugins, such as loading context from a: PDF MD file Word doc Google doc Single webpage (URL) And converting the info to markdown, and inser… ### [Add Site Architecture context source for Drupal site behavior contracts](https://git.drupalcode.org/project/ai_context/-/work_items/3586150) State: opened | Updated: 2026-05-10 | Author: scott falconer (scottfalconer) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem / Motivation Outside-in agents need to understand how a Drupal site actually produces public and operational outcomes before they act. Today, that site-specific truth often lives across routes, aliases, entity routes, bundles, fields, workflows, Views, Pathauto, Canvas pages, menus, custom routes, code signals, and runtime validation. Without that context, agents can make plausible but wrong decisions, such as: - creating a static page where an existing route, alias, View, Canvas page, or entity route already owns the surface; - creating the wrong bundle for a listing or detail r… ### [Default some context scope plugins to disabled if module dependencies aren't installed](https://git.drupalcode.org/project/ai_context/-/work_items/3579235) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: blocked, category::task, needs prioritization, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation There are context scope plugins that are dependent on other modules: languages => language module tags => taxonomy module and there may be custom/contrib plugins added later that may be as well Proposed reso… ### [(Discuss) Associating adhoc vocabularies (freetagging) with context items](https://git.drupalcode.org/project/ai_context/-/work_items/3586198) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 10, category::plan, needs ux review, priority::normal Description: ## Problem/motivation ### Current taxonomy-related features Right now taxonomy-related functionality is available for context items in the following ways: 1. **Tags Scope Plugin:** The AI Context Tags is a vocabulary provided if you want to categorize your context in special ways. Agents can subscribe to these tags if they way. Example: Add a "webform" tag in the vocabulary and then if you have a webform agent, you could use that tag for scope subscriptions and you can tag any context items that are suited for webforms with the tag. This would a way to join the webform agent to one or more… ### [CCC slides and presentation for NYC Drupal AI Summit 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3586201) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Sprint 9, NYC2026, category::task, priority::normal Description: ## What CCC presentation by Kristen Pol for NYC Drupal AI Summit 2026 ## Tasks - Update slides - Practice - Present! ### [CCC slides and presentation for DrupalSouth Wellington 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3586200) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Sprint 9, DrupalSouth2026, category::task, priority::normal Description: ## What CCC presentation by Suchi Garg for DrupalSouth Wellington 2026 ## Tasks - Meet with Kristen to go over materials - Suchi research and testing - Suchi prep slides and create videos - Kristen review slides and videos - Suchi present! ### [Clarify scope items are additive in docs and UI](https://git.drupalcode.org/project/ai_context/-/work_items/3586196) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Sprint 10, category::task, priority::normal Description: ## Problem/motivation Follow-up to: #3586195 Scope subscriptions are additive. If you subscribe to use case = "writing words" and tag = "campaign", you will get context items that are scoped to either of these. Meaning, the context item doesn't need *both* of them to be relevant. ## Solution - Review existing docs and update as needed - Review UI text and consider clarifying this to the user ### [Create GitLab issue templates for ai_context project](https://git.drupalcode.org/project/ai_context/-/work_items/3586155) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: Need to have our issue templates again! Look at the new ai_initiative ones for inspiration ### [Sprint 10 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3586225) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and estimates on release timing. --- ## Proposed resolution - Go through all issues and prioritize - Identify what goes into the next sprint - Identify candidates for future sprints - Add new issues as needed - Update roadmap meta with latest info --- ## Target date or deadline 10 May to 29 May 2026 --- ## Remaining tasks - Go through all issues and prioritize - Figure out what's in the next sprint - Figure out candidates for future sprints - Add new issues as needed… ### [Test Chicago Driesnote repo with cheaper models](https://git.drupalcode.org/project/ai_context/-/work_items/3586221) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: ## Problem/motivation The Chicago Driesnote demo videos were recorded with Open AI for Vector DB and Opus 4.6 for everything else. Opus 4.6 is expensive. It can cost $1 to $2 USD to create a page. We want to see if cheaper models can produce okay results. ## Solution Test with smaller/cheaper models and post results. ## Tasks - [ ] Set up demo environment - [ ] Test with 2 or 3 cheaper/smaller models - [ ] Post results ### [Gather CCC contribution stats for code and non-code contributions for release notes](https://git.drupalcode.org/project/ai_context/-/work_items/3586222) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Sprint 10, category::task, priority::normal, sprint candidate Description: ## Problem/motivation The current tools for generating release notes are inadequate as they only focus on code commits. They also require the issue number to be in the commit message. I want to gather the stats for all contributors for a release including non-code contributions which there are many. ## Solution The result for release notes should be something like: ``` New Features * one * two Bug Fixes * one * two Tasks * one * two Non-Code Contributions * number of issues? Contributors: kristen pol (35), afoster (8), emma horrell (6), scott falconer (6), mglaman (3)... salsa (35),… ### [(Discuss) Add boundaries / exclusions to scope plugins](https://git.drupalcode.org/project/ai_context/-/work_items/3586197) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Sprint 10, category::task, priority::normal Description: ## Problem/motivation Follow-up to: #3586195 Boundaries / exclusions were discussed quite a bit in the past, but hasn't been implemented yet. Example context item: - Tone and voice - Scope - Use case = Writing Words - Entity bundle = exclude for Support Notes (content type) Translation: The context will be applicable to any agent subscription with use case = writing words unless it's a node that's a Support Notes content type ## Solution Add an exclusion option for each scope item and bake that into the logic Could be a dropdown per scope item: - None (neutral/default) - Include… ### [Create CCC status update video](https://git.drupalcode.org/project/ai_context/-/work_items/3586154) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Create a video on the current status of CCC and what's coming up. ### [Address todos in CCC subscription update logic and scope visibility in tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586111) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Subscription update logic and scope visibility (2 tests) The first test verifies that editing one agent's subscriptions doesn't clobber anoth… ### [Address todos in CCC empty scope / subscription handling tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586110) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Empty scope / subscription handling (2 tests) Empty or cleared scope selections are a normal user action. If this isn't handled gracefully it… ### [Stabilize global context item ordering before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586189) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3582504 **Description:** Global context items are capped in first-seen/ascending-ID order. When `max_global_items` is reached, older or earlier-loaded items win arbitrarily, which makes the selected global context depend on creation/load order rather than an intentional ranking. Before RC1, global item selection should be deterministic and documented. Global items should be sorted by an intended ordering before applying `max_global_items`, preferably most recently changed first with an ID tie-breaker. **Scope:** - Sort global context items deterministically before applyin… ### [Clean up CCC inconsistences and DX issues before rc1 (part 1)](https://git.drupalcode.org/project/ai_context/-/work_items/3586147) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Back and forth with opus 4.6 to review inconsistencies and DX issues: See MD file: [ai-context-naming-dx-review.md](https://git.drupalcode.org/-/project/191993/uploads/bdc9625673e049cdd31d2f0653de3ccd/ai-context-naming-dx-review.md) ## Handled in this issue (part 1) The ones that are addressed in this MR are: Addressed from `reviews/ai-context-naming-dx-review.md`: - **1c: Orphaned form**: deleted `AiContextScopeSiteSectionForm` - **2d: Missing `declare(strict_types=1)`**: added to `DiffHooks.php` and `AiContextUninstallValidator.php`; `DynamicEntityReferenceHooks.php` already had it - *… ### [Fix custom path matching for site section scope](https://git.drupalcode.org/project/ai_context/-/work_items/3586158) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, AI Sprint 9, category::bug Description: Follow up to: #3582504 **Description:** The site-section scope supports custom path values such as `custom:/products/*`, but the selection pipeline currently relies on the base scope matching logic, which only compares the detected section ID to stored scope values. As a result, custom path patterns may never match during context selection. **Scope:** - Override `matchesCurrentContext()` in the site-section scope plugin. - Match both configured section IDs and `custom:` path patterns against the current path. - Preserve existing behavior for items with no site-section values. - Add tests fo… ### [Configure GitLab metadata for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586142) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Go through and review the metadata available and remove anything that's not needed and decide if anything should be added. ### [Address todos in CCC taxonomy entity type dependency in kernel tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586109) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up from: #3586091: Review CCC todo comments for action items ### Taxonomy entity type dependency in kernel tests (2 tests) `getAllScopeValues()` is a core API method used by the scope system. The fix is lik… ### [Design for the Context Item single entity view (manual/markdown/text/static)](https://git.drupalcode.org/project/ai_context/-/work_items/3586141) State: closed | Updated: 2026-05-10 | Author: Aidan Foster (aidanfoster) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Step 1: Mockups x 2 (Update the Context Item entity view (/admin/ai/context/items/{id}) to match modern admin patterns and improve editing continuity. Wrap the entire entity view in a white card frame to match the markdown editor treatment. The current state has the form on a tinted background and the editor on white, which creates two competing visual zones. Add a right sidebar with navigation to the parent Context Item and sibling Context Items. For example, from "Content Structure: Product Pages," the sidebar should link to "Articles & Blogs," "PPC Landing Page," and "Press Releases." O… ### [Design for the Context Item single entity view (connected/remote/dynamic)](https://git.drupalcode.org/project/ai_context/-/work_items/3586224) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: This was split off from: #3586141 to focus on Connected Context. ## Step 1: Mockup From original issue: For Connected Context items, add sync metadata to the sidebar: last synced (relative time), next sync, sync status, sync schedule with edit link, a manual "Sync now" button, and source freshness from the external system when available. ## Step 2: Review, discuss and iterate. ## Step 3: Create follow-up issue to implement. ### [Design Improved Context Items List View](https://git.drupalcode.org/project/ai_context/-/work_items/3586140) State: closed | Updated: 2026-05-10 | Author: Aidan Foster (aidanfoster) | Assigned: Aidan Foster (aidanfoster) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ### Step 1: Update Context Items List view to see impact of proposed changes. 1. Resolve "Add AI Context Item" button label inconsistency with "Context Items" page title (recommend dropping "AI" from the button) 2. Update tooltips or text labels to Type column icons. 3. Add source badge next to each item (manual / file / connector) 4. Add column sorts 5. Figure out how to show token usage ### Step 2: Discuss / Review Done ### Step 3: Create Follow-up Issues Done ### [Fatal errors when uninstalling CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586223) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Fatal errors when uninstalling CCC (1.0.x). ### First error 1. Install on CMS 2.1 2. Don't add anything 3. Uninstall 4. Error ``` In ExceptionHandler.php line 96: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'db.ai_context_usage' doesn't exist: SELECT "base_table"."id" AS "id", "base_table"."id" AS "base_table_id " … ### [Address todos in scope form rendering and persistence tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586108) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) ### Scope form field rendering and persistence (7 tests) This test cluster is broader than language scoping. It verifies that scope fields render and persist correctly across both context item forms and agent configuration forms, including language, use case, site section, and tag scopes. The original failure looked language-related because language fields only render as checkboxes on multilingual sites. On single-language sites, production code intentionally shows an informational message instead. The… ### [Normalize token/item limit naming — eliminate `tokenBudget` and align on `maxTokens`/`maxItems`](https://git.drupalcode.org/project/ai_context/-/work_items/3586146) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow-up to: #3584838 Went back and forth with opus 4.6 on this: --- **Problem:** The concept "maximum tokens for rendered context" uses three different names as it flows through the codebase: - Public API: `tokenLimit` (`retrieve(tokenLimit: 2000)`) - Request DTO: `maxTokens` (`$request->getMaxTokens()`) - Result VO: `tokenBudget` (`$result->getTokenBudget()`) Similarly for items: - Public API: no public param yet - Request DTO: `maxItems` (`$request->getMaxItems()`) - Config: `max_items` The `tokenBudget` naming is the main inconsistency — it implies allocation planning rather than… ### [Allow AI Context provider/model setting to be explicitly unset](https://git.drupalcode.org/project/ai_context/-/work_items/3586190) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::feature, priority::normal, what::code, why::wontFix Description: Handling this in: #3586159 **Description:** The AI Context general settings page currently uses the AI provider configuration element for `AI Provider/Model`. When no module-specific provider/model is saved, the element visually falls back to the AI module’s core default provider. This makes it look like AI Context has a provider configured and does not give administrators an obvious way to explicitly unset provider/model for AI Context. AI Context should support an explicit “No provider” state so conditional subcontext can be disabled intentionally unless a provider/model is configured f… ### [Document subcontext entity validation rules for RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586185) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** AI Context now enforces subcontext integrity at the entity validation layer through `AiContextItemIntegrity` / `AiContextItemValidator`. This is the desired behavior for RC1, but the docs should explicitly describe the persistence contract. Document that: - A context item cannot be its own parent. - Subcontext hierarchies are limited to one level. - An item with children cannot become a subcontext itself. - `subcontext_type` is required when a parent is selected. - Parent deletion clears child `parent` and `subcontext_type` references. - These rule… ### [Test CCC using DrupalForge DrupalCon Chicago Driesnote template](https://git.drupalcode.org/project/ai_context/-/work_items/3586152) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: We have this now: https://www.drupalforge.org/template/driesnote-chicago Test this out to make sure it works as expected. ### [Create CCC example module that adds scope plugin and extends existing plugins](https://git.drupalcode.org/project/ai_context/-/work_items/3571354) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation In order to see how scope plugins work, it would be helpful to have a code example. Proposed resolution Create example module that adds scope plugin and extends existing plugins It should create a scope plugin as … ### [Test CCC on Drupal CMS 2.1](https://git.drupalcode.org/project/ai_context/-/work_items/3586193) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Test CCC on latest version of Drupal CMS 2.1 ### [Long context items are skipped instead of truncated when max token limit is reached](https://git.drupalcode.org/project/ai_context/-/work_items/3586191) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Found this while testing: #3586160 **Description:** When a selected AI Context item is longer than the configured max token budget, the renderer may exclude the item entirely instead of truncating its guidance content to fit. This happens because token limiting is applied before the item metadata wrapper is added, and the full rendered block can still exceed the budget after wrapping. Expected behavior: oversized context item content should be truncated when possible so the item can still be injected within the token limit. The item should only be skipped if its required metadata wrapper… ### [Add `AiContextSelectorInterface` before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586184) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** `AiContextSelector::select()` is the primary programmatic API for selecting and rendering AI Context items. Before RC1, this should be exposed through an interface so contrib modules and custom integrations can depend on a stable contract instead of the concrete service class. Proposed scope: - Add `Drupal\ai_context\Service\AiContextSelectorInterface`. - Define `select(AiContextRequest $request): AiContextResult`. - Have `AiContextSelector` implement the interface. - Add a service alias for the interface in `ai_context.services.yml`. - Update inter… ### [ai_context overview CSS references missing external.svg asset via bad relative path](https://git.drupalcode.org/project/ai_context/-/work_items/3586143) State: closed | Updated: 2026-05-10 | Author: scott falconer (scottfalconer) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: - Problem: Loading /admin/ai/context/overview records a missing asset request. - Evidence: request goes to /modules/contrib/contrib/ai/assets/ icons/external.svg - Likely source: web/modules/contrib/ai_context/css/ ai_context_overview.css - Current CSS path: ../../contrib/ai/assets/icons/external.svg - Actual asset exists at: web/modules/contrib/ai/assets/icons/ external.svg - Expected: overview loads without 404/watchdog noise. - Actual: browser/watchdog records missing asset. - Suggested fix area: correct the relative CSS URL or avoid reaching through anothe… ### [Set default usage record retention to 90 days](https://git.drupalcode.org/project/ai_context/-/work_items/3586186) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3576100 **Description:** Usage records are useful for auditability and debugging, but they may expose prompt/task behavior and can grow over time. Before RC1, the module should ship with conservative default retention settings. Recommended defaults: - Keep usage tracking enabled by default. - Set `usage_max_age` to `7776000` seconds, 90 days. - Keep `usage_max_records` at `10000` as a safety cap. - Keep cron pruning batched. - Update the usage settings form fallback to match install config. - Ensure config schema and tests continue to cover these settings. This makes the … ### [(Discuss) Logic for multiple context scope items being handled separately](https://git.drupalcode.org/project/ai_context/-/work_items/3586195) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation I was testing in prep for beta1 and noticed this behavior which I think is okay, but I want to talk with the UX team about it. 1. Context item is scoped to use case (writing words) and entity bundle (article) 2. Agent scope subscriptions are use case (writing words), tag (foobar), site section (foobar), and entity bundle (blog) In this case, the context item is injected into the agent's prompt. This is because they both have use case = writing words. Let's discuss if scope should be handled like this. I think it makes sense. ## Next steps - Discuss - If necessary, m… ### [[Discuss] Conditional subcontext logic](https://git.drupalcode.org/project/ai_context/-/work_items/3586194) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3586149 ## Problem The conditional subcontext work was merged a day before beta1 was tagged as part of a huge rewrite of the selection logic. It wasn't thoroughly tested, so we need to do that. Aidan did do some testing as part of the Driesnote test cases but that was before this was merged. ## Use cases 1. Create parent + child but author didn't include any information about the child in the parent and see if it picks up the child without the extra guidance 2. Create parent + child but author did add information in the parent about the child and see if it picks up the chi… ### [CCC beta2 codebase review](https://git.drupalcode.org/project/ai_context/-/work_items/3586202) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Beta2 will be released shortly. We continually need to check the codebase as it changes for potential security issues, performance issues, and any pre-rc1 features/apis that need to be addressed. ## Solution Run AI checks against the codebase to identify for pre-rc1 and post-1.0: - Important performance issues - Important feature/API gaps - Security issues (these will not be reported here) ## Next steps - Run security review - Run performance review - Run api/feature review - Attach findings for here (not security) - Create follow-up issues as needed ### [Sprint 9 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3586183) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and estimates on release timing. --- ## Proposed resolution - Go through all issues and prioritize - Identify what goes into the next sprint - Identify candidates for future sprints - Add new issues as needed - Update roadmap meta with latest info --- ## Target date or deadline 2 May to 16 May 2026 --- ## Remaining tasks - Go through all issues and prioritize - Figure out what's in the next sprint - Figure out candidates for future sprints - Add new issues as needed … ### [Require provider for conditional subcontext before RC1](https://git.drupalcode.org/project/ai_context/-/work_items/3586159) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: Follow up to: #3582504 **Description:** Conditional subcontext currently includes all conditional children when no AI provider/model is configured. This can unexpectedly expand token usage and makes conditional behavior observable even though the provider-dependent selection mechanism is unavailable. Before RC1, conditional subcontext should require an explicitly configured AI Context provider/model. Users should not be able to newly select conditional subcontext without a provider/model, and the UI should clearly explain why the option is unavailable with a link to the global AI Context … ### [Sprint 6 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3582536) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and a estimates on release timing. Proposed resolution Go through all issues and prioritize, figure out what's in the next sprint an… ### [Fix local ./lint.sh stylelint script errors for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3576094) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !118 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have a ./lint.sh script in the module that people can run to check for issues before committing. Right now, the pipeline is clean with no stylelint errors, but when I run ./lint.sh locally, I g… ### [Review CCC todo comments for action items](https://git.drupalcode.org/project/ai_context/-/work_items/3586091) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Here are the todo comments in the code which need to be reviewed to see if any should happen before rc1: ./tests/src/Functional/AiContextScopeContextItemFormTest.php: * @todo Fix language scope form fi… ### [Drupal Developer Days CCC contribution planning](https://git.drupalcode.org/project/ai_context/-/work_items/3583319) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Drupal Developer Days is April 22-25, 2026, and they would have people who could help with CCC during the event. This issue is for planning issues that could be tackled there, ideally focused on reviews, testing, … ### [Add regular CCC contributors as GitLab reporter members](https://git.drupalcode.org/project/ai_context/-/work_items/3586139) State: closed | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::bug Description: With the cutover to GitLab, people can't edit metadata or issue summaries unless they are a "member" in GitLab for the project. The simplest role is "reporter". Go through and add regular contributors as "reporter" members so they can continue to collaborate. FEEL FREE TO COMMENT ON THIS ISSUE IF YOU NEED ACCESS ASAP. IT WILL TAKE SOME TIME TO GATHER EVERYONE AND GET PEOPLE ADDED. I'm creating a list here: https://docs.google.com/spreadsheets/d/1fqnpQYl9SsxkIe2iTFKExYY-ojAyxXAwuLdWdACHQ-g/edit?usp=sharing ### [CCC beta testing at Drupal Dev Days (DDD) 2026](https://git.drupalcode.org/project/ai_context/-/work_items/3585917) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation This issue is for testing CCC at Drupal Dev Days. Multiple people can do this at the same time, so you don't have to assign this issue to yourself. Or, if it is assigned to someone else, you can still also test it… ### [Still getting GitLab CI timeouts for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586138) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !123 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Getting timeouts like this: https://git.drupalcode.org/project/ai_context/-/jobs/9459792 The script exceeded the maximum execution time set for the job Proposed resolution Figure out how to fix Ta… ### [Remove Scheduler content moderation integration CCC patch once a new release is available](https://git.drupalcode.org/project/ai_context/-/work_items/3586090) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !121 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We have this patch: "extra": { "patches": { "drupal/scheduler_content_moderation_integration": { "I… ### [Sprint 8 CCC roadmap updates, sprint planning, and issue triage](https://git.drupalcode.org/project/ai_context/-/work_items/3585850) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::plan Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need to know where things are at and what can get done before the 1.0 release and a estimates on release timing. Proposed resolution Go through all issues and prioritize, figure out what's in the next sprint an… ### [CCC Chicago planning](https://git.drupalcode.org/project/ai_context/-/work_items/3577670) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, Chicago2026 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Planning issue for DrupalCon Chicago Proposed resolution Before Chicago #3567570: [META] Context Control Center MVP demo #3577087: CCC MVP Demo: Finalize FinDrop context #3577661: CCC Chicago session slides #35776… ### [Increase gitlab ci timeout for CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3582562) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, category::task, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !112 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Getting timeouts like this: https://git.drupalcode.org/project/ai_context/-/jobs/9180630 The script exceeded the maximum execution time set for the job Proposed resolution Increase the timeout Ta… ### [Fix PHPStan errors in CCC after 2.1.45 release](https://git.drupalcode.org/project/ai_context/-/work_items/3582544) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !111 >>> Overview Fix PHPStan errors in HEAD after 2.1.45 release in CI Proposed resolution Ignore or fix items User interface changes > Related issue: [Issue #3582335](https://www.drupal.org/node/3582335) ### [Update context listing to not use target column](https://git.drupalcode.org/project/ai_context/-/work_items/3586116) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation This issue makes target entities scope optional: #3577428: Update context item target entities for progressive enhancement And the context list isn't consistent with the agent context settings page (see screenshot… ### [Update context list to show workflow state](https://git.drupalcode.org/project/ai_context/-/work_items/3586127) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, category::feature Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3577425: [Discuss] Possible styling updates for context listing We lost the publishing status when the context list page was redone. We need to know the moderation state. Proposed resolution Update … ### [CCC QA scripts for 1.0 testing](https://git.drupalcode.org/project/ai_context/-/work_items/3586226) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: blocker::stable, category::task, mvp, needs prioritization Description: ## Problem/motivation Need to make sure we're ready for the QA team to do pre-1.0 testing. ## Solution From Bruna Emerich (Zoocha): Documentation covering the functionality, along with a test script (such as the example in this ticket, where an .md file is included), is sufficient for us to carry out testing. If any questions come up, we’ll raise them directly in the channel and tag you. Regarding lead time, it depends on the size of the functionality, but generally one week’s notice is sufficient. If there’s a fixed release date, allowing around 14 days is preferable, as it gives enough … ### [Full QA of CCC in prep for 1.0](https://git.drupalcode.org/project/ai_context/-/work_items/3573716) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: blocker::stable, category::task, mvp, needs prioritization Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We are getting close to creating an alpha or beta version and want to take a step back and do a full QA review before doing so. Proposed resolution Testing various features and finding bugs that would be good to f… ### [Create CCC rc1 release](https://git.drupalcode.org/project/ai_context/-/work_items/3586151) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Innovation, category::task, mvp Description: Problem/Motivation Create CCC rc1 release Tag: 1.0.0-rc1 Proposed resolution Create the release once at least the must-haves are done here: #3585902: CCC beta2 release planning Target date or deadline June 2026 Remaining tasks Wait on must-haves Tag code Create the release in UI Celebrate! AI usage (if applicable) [ ] AI Assisted Issue This issue was generated with AI assistance, but was reviewed and refined by the creator. [ ] AI Assisted Code This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision. [ ] AI Generated Code This… ### [Move scheduler feature to submodule or progressive enhancement](https://git.drupalcode.org/project/ai_context/-/work_items/3577429) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: Matt Glaman (mglaman) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !92 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Follow-up to: #3569967: [Discuss] Figure out which CCC features can be optional for MVP We are trying to reduce the number of dependencies for ai_context. The scheduler is one dependency that not e… ### [Remove AiContextItemType](https://git.drupalcode.org/project/ai_context/-/work_items/3584775) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, blocked Description: >>> [!note] Migrated issue Reported by: [mglaman](https://www.drupal.org/user/2416470) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation I don't get why context items have a bundle. I think the only reason is for Scheduler support. That entire concept is also being discussed in #3577429: Move scheduler feature to submodule or progressive enhancement… ### [Fix eslint errors in GitLab UI even when pipeline is green](https://git.drupalcode.org/project/ai_context/-/work_items/3576093) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Innovation, AI Sprint 10, blocked Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) Related to !99 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Although the pipeline passes with no eslint issues, there are still failures shown on the test summary, e.g. https://git.drupalcode.org/project/ai_context/-/merge_requests/71 Test summary: 3 failed… ### [Update context listing page per new design](https://git.drupalcode.org/project/ai_context/-/work_items/3586219) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Aidan Foster (aidanfoster), Eric Homanchuk (erichomanchuk) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: ## Problem/motivation Follow-up to: #3586140 There is a new design for the context listing page based on UX review and feedback. ## Solution 1. Type: Manual => Text 2. Subcontext type icon needs to pass contrast checker 3. Tokens in own column is good 4. No icon for yellow (medium) and grey (low) token numbers 5. Warning icon for red (high) token numbers 6. No info icon after context items 7. Scope column is good 8. Keep use cases column separated 9. Target => scope (but minimize what's shown) 10. Updated => Status (draft/published/unpublished) 11. Target dropdown => Scope dropd… ### [Inject context into ai_ckeditor requests](https://git.drupalcode.org/project/ai_context/-/work_items/3581955) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 10 Description: >>> [!note] Migrated issue Reported by: [jessehs](https://www.drupal.org/user/620440) Related to !116 >>> Problem/Motivation The ai_context module cannot inject scope-matched context items into ai_ckeditor AI requests because ai_ckeditor bypasses the ai_agents pipeline (and its BuildSystemPromptEvent) entirely — it calls the AI provider directly in its own streaming controller. There is no event or hook point for ai_context to intercept. This issue is the ai_context companion to the ai_ckeditor entity context and event extensibility work tracked in the drupal/ai module issue queue. … ### [Clean up follow-ups from target entity decoupling review](https://git.drupalcode.org/project/ai_context/-/work_items/3586082) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> **Problem/Motivation** There was out-of-scope feedback on: #3577428 Feedback (PDF) Feedback (MD) **Description:** Follow up on the non-blocking items identified during the target entity / DER decoupling review. The MR made `dynamic_entity_reference` optional successfully, but a few cleanup tasks remain to reduce optional dependency coupling, improve documentation, and tighten safer render/input patterns. **Tasks:** - Remove the `DynamicEntityReferenceItem` import/reference from `AiContextItem:… ### [Improve config validation and use #config_target for settings form](https://git.drupalcode.org/project/ai_context/-/work_items/3580910) State: opened | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 9 Description: >>> [!note] Migrated issue Reported by: [svendecabooter](https://www.drupal.org/user/35369) Related to !107 >>> [Tracker] Update Summary: `ai_context.settings` config validation Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation AiContextSettingsForm uses #default_value with manual $config->get() calls and a manual submitForm() that sets each config value individually. Validation for numeric fields (max_global_items,… ### [Can't Apply Scheduler Patch](https://git.drupalcode.org/project/ai_context/-/work_items/3579841) State: closed | Updated: 2026-05-10 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, blocker::beta Description: >>> [!note] Migrated issue Reported by: [robloach](https://www.drupal.org/user/61114) Related to !102 >>> [Tracker] Update Summary: Created the issue Check-in Date: 03/17/2026 Blocked by: Additional Collaborators: @robloach Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation When installing Context Control Center on a fresh site, you run into a composer error when it tries to apply the patch. Gathering patches for dependencies. This might take a minute. - Installing drupal/scheduler_content_moderation_integration (3.0.4): Extracting a… ### [Update context view page per new design](https://git.drupalcode.org/project/ai_context/-/work_items/3586220) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: Eric Homanchuk (erichomanchuk) | Labels: AI Sprint 10, category::task, priority::major, sprint candidate Description: ## Problem/motivation Follow-up to: #3586141 There is a new design for the context view page based on UX review and feedback. ## Solution ### Walkthough ## Tasks - [X] Add new design comp above - [ ] Double check design issue for anything missing - [ ] Update code - [ ] Review code - [ ] Manually test ### [(Discuss) Context Connector feature](https://git.drupalcode.org/project/ai_context/-/work_items/3586216) State: opened | Updated: 2026-05-10 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI UX, category::plan, post 1.0, priority::major Description: Follow up to: #3573715 ## Problem/motivation Pasted from review issue: **Connected Context** (replaces "Remote Context" / "External Context") — Defining characteristic is a synced connection to an external system, not just remote location. Industry alignment is strong: Glean, ChatGPT, Claude, Salesforce, HubSpot, Notion, and Airtable all use Connector / Connected language for this pattern. A **Context Connector** is the platform-specific integration plugin that enables Connected Context as a source type. I need to install the "Google Analytics Context Connector" Detailed feedback on Cont… --- MERGE REQUESTS (24h) --- ### [Issue #3586227: CCC navigation icon missing due to menu changes.](https://git.drupalcode.org/project/ai_context/-/merge_requests/149) State: merged 2026-05-11 | Author: Kristen Pol (kepol) | Branch: 3586227-d11-icon | 52 diff lines Description: Closes #3586227 ### [Issue #3586227: Fix navigation icon.](https://git.drupalcode.org/project/ai_context/-/merge_requests/148) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586227-ccc-navigation-icon | 41 diff lines Description: Closes #3586227 ### [Issue #3586108: Add language tests.](https://git.drupalcode.org/project/ai_context/-/merge_requests/137) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586108-langage-todos | 466 diff lines Description: Closes #3586108 ### [Issue #3586223: Fatal errors when uninstalling CCC.](https://git.drupalcode.org/project/ai_context/-/merge_requests/147) State: merged 2026-05-10 | Author: Kristen Pol (kepol) | Branch: 3586223-fatal-uninstall-erro | 743 diff lines Description: Closes #3586223 ### [Issue #3586150: Add ai_context_site_architecture submodule with MCP resource provider.](https://git.drupalcode.org/project/ai_context/-/merge_requests/146) State: opened | Author: George Kastanis (zorz) | Branch: 3586150-site-architecture | 6499 diff lines Description: Resolves #3586150. ## Summary Adds **`ai_context_site_architecture`** — a submodule that auto-harvests "site behavior contracts" describing what owns each surface on a Drupal site (entity routes, Views, path aliases, pathauto patterns, ECA rules, field definitions, content moderation workflows, module state) and writes them into CCC as drafts for human review before they reach AI agents. Plus an optional **`ai_context_site_architecture_mcp`** sub-submodule that exposes the same contracts as MCP resources at `drupal://site/contracts/{contract_id}`, so MCP-aware agents (Claude Code, Cursor, e… ### [Issue #3586157: Improve selection performance.](https://git.drupalcode.org/project/ai_context/-/merge_requests/141) State: opened | Author: Kristen Pol (kepol) | Branch: 3586157-select-performance | 688 diff lines Description: Closes #3586157 ### [Issue #3586160: Add agent schema fields.](https://git.drupalcode.org/project/ai_context/-/merge_requests/134) State: opened | Author: Kristen Pol (kepol) | Branch: 3586160-per-agent-selection | 1331 diff lines Description: Closes #3586160 ### [Issue #3586161: Add entity schema fields.](https://git.drupalcode.org/project/ai_context/-/merge_requests/133) State: opened | Author: Kristen Pol (kepol) | Branch: 3586161-entity-schema | 371 diff lines Description: Closes #3586161 ### [Issue #3586162: Add post_select and post_render selection events.](https://git.drupalcode.org/project/ai_context/-/merge_requests/131) State: opened | Author: Kristen Pol (kepol) | Branch: 3586162-add-selection-events | 816 diff lines Description: Closes #3586162 ### [Issue #3586150: Add site architecture context source.](https://git.drupalcode.org/project/ai_context/-/merge_requests/126) State: opened | Author: scott falconer (scottfalconer) | Branch: 3586150-add-site-ar | 13094 diff lines Description: Work item: https://git.drupalcode.org/project/ai_context/-/work_items/3586150 Adds the ai_context_site_architecture submodule as a CCC-governed Drupal site behavior contract generator. Summary: - Compiles Drupal surfaces into structured site behavior contracts. - Keeps MCP optional while producing MCP-ready resource payloads. - Adds CCC draft writing, Drush export, schema docs, resource template support, and tests. - Refactors generation behind collector and post-processor services. Validation run locally: - PHP 8.3 syntax lint across modules/ai_context_site_architecture/src and tests/src: … ### [Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools.](https://git.drupalcode.org/project/ai_context/-/merge_requests/116) State: opened | Author: Jesse Hofmann-Smith (jessehs) | Branch: 3581955-inject-context-into | 339 diff lines Description: Closes #3581955 ### [Issue #3580910: Use proper config validation and #config_target for ai_context.settings.](https://git.drupalcode.org/project/ai_context/-/merge_requests/107) State: opened | Author: Sven Decabooter (svendecabooter) | Branch: 3580910-improve-config-validation | 252 diff lines Description: Closes #3580910 ### [Issue #3577429: Move scheduler feature.](https://git.drupalcode.org/project/ai_context/-/merge_requests/92) State: opened | Author: axioteo | Branch: 3577429-move-scheduler-feature | 1045 diff lines Description: Moves scheduler functionality into a submodule, and if enabled, sets by default the scheduling options to false. Closes #3577429 ### [Issue #3574937: Review and update CCC permissions.](https://git.drupalcode.org/project/ai_context/-/merge_requests/78) State: opened | Author: Ann Mary Sruthy (annmarysruthy) | Branch: 3574937-review-and-update | 271 diff lines Description: Closes #3574937 ### [Issue #3586145: Handle removed scope values.](https://git.drupalcode.org/project/ai_context/-/merge_requests/132) State: opened | Author: Kristen Pol (kepol) | Branch: 3586145-stale-scope-values | 867 diff lines Description: Closes #3586145 ### [Issue #3586082: Clean up after der decoupling.](https://git.drupalcode.org/project/ai_context/-/merge_requests/145) State: opened | Author: Kristen Pol (kepol) | Branch: 3586082-clean-up-follow-ups | 223 diff lines Description: Closes #3586082 --- COMMITS (24h) --- - [a13c90c7](https://git.drupalcode.org/project/ai_context/-/commit/a13c90c74b2d8f358a602d6251286d83322c9dbd) Issue #3586227: CCC navigation icon missing due to menu changes. — Kristen Pol (2026-05-11T00:36:04.000+00:00) - [3a7ce43d](https://git.drupalcode.org/project/ai_context/-/commit/3a7ce43d9c6c7a14c0aa355845986e93913d5744) Issue #3586227: Fix navigation icon. — Kristen Pol (2026-05-10T20:19:53.000+00:00) - [0c5920b6](https://git.drupalcode.org/project/ai_context/-/commit/0c5920b600f9624d44cb82a3b6afb3f4fd048d5d) Issue #3586108: Add language tests. — Kristen Pol (2026-05-10T16:21:59.000+00:00) - [9cd9f210](https://git.drupalcode.org/project/ai_context/-/commit/9cd9f210b2846da9cc5f59d52eee4e027b0aabda) Issue #3586223: Fatal errors when uninstalling CCC. — Kristen Pol (2026-05-10T16:21:02.000+00:00) ======================================================================== ## [12] generateTldr:executive ======================================================================== You are an editor distilling a Drupal AI project newsletter into its most important highlights. You are writing for a non-technical executive audience. Focus on business impact, strategic progress, and delivery milestones. Avoid all technical jargon. Read all the module summaries below. Separate the highlights into two categories: - SHIPPED: things that were merged, fixed, released, or completed during this period. - ONGOING: things that are actively in progress, under review, or blocked. Be specific — name the module, what happened, and why it matters. Do not use emoticons or mdashes. Do not include any text outside the two sections. Do not mention issue numbers (e.g. #12345) or MR IDs (e.g. !42) — they are not linked and are meaningless to readers out of context. Instead, describe what was done in plain language. Format as two HTML sections. Use exactly this structure (all
elements must be inside the
, never outside it):
Shipped

Title here — One sentence explanation.

Another title — One sentence explanation.

Ongoing

Title here — One sentence explanation.

Up to 5 items per section. Do not output any text, tags, or characters outside these two sections. Output only the HTML fragment, no surrounding tags. --- MODULE SUMMARIES ---
AI (Artificial Intelligence)

Sprint in Progress: Reliability, Usability, and Quality

The past 24 hours have seen sustained momentum across the AI module, with multiple workstreams advancing in parallel. The focus is on making AI-powered content features more reliable, consistent, and easier to configure for site builders and editors.

A significant area of activity is the Automators component, which automates AI-driven field population on content. Several efforts are converging here: work to improve how AI providers are selected and configured is progressing through two open proposals, and a separate effort aims to standardise how the Automators component processes and returns AI output -- making it more predictable and less error-prone. Alongside this, Pieter Frenssen (pfrenssen) identified and submitted a fix for a crash that occurs when automating certain core content fields, a real-world reliability issue that could affect editors using this feature today.

On the AI Agent front, Bruno Bruno (bbruno) has submitted work on a new visual editor for configuring agent tools, replacing a complex manual process with an interactive interface. This directly reduces the barrier to setting up AI agents for non-technical users.

Smaller but important progress includes a documentation improvement for developer conventions, which supports long-term project maintainability, and ongoing work to enable the AI-powered text editor to be aware of the content context it is operating within.

How can I help on this project?

Leaders can support progress by ensuring contributors working on Automators improvements have dedicated time to reach completion, as several related proposals risk stalling without coordination. Advocating for UX review resources would help unblock the agent tools editor. Encouraging organisational testing of the Automators crash fix would validate it for faster merge.
---
Drupal AI Initiative

Chicago DrupalCon Demo Preparations Underway

Activity over the past 24 hours has been focused on polishing the AI demonstration materials ahead of the Chicago DrupalCon Driesnote, a high-profile public showcase of Drupal's AI capabilities. Two issues are being addressed to ensure the demo is ready and reproducible.

First, work is underway on Update Chicago Driesnote repo to include demo prompts, which involves capturing the key AI interaction scripts in a shareable format so that anyone setting up the demo environment has clear, consistent prompts to work from. This reduces the risk of an inconsistent or underwhelming live demonstration.

Second, Kristen Pol (kepol) has picked up Fix RAG search on Chicago Driesnote repo install, addressing a known failure in the AI-powered search feature that is central to the demo. Without this fix, a core part of the showcase would not function as intended in front of a large audience.

No code was merged or committed in this period, so the immediate priority is resolving these issues before the event deadline.

How can I help on this project?

Leaders can support progress by confirming the timeline and any hard deadlines for the Chicago demo, ensuring the team has adequate capacity to resolve these issues in time. If external contributors or vendor support are needed to accelerate testing, approving that resourcing quickly would reduce risk to the public showcase.
---
Unstructured

Summary

Activity on the Unstructured module over the past 24 hours was focused on a single area of development. Ahmad Khader (Ahmad-Khader) opened a new merge request, Resolve #3582438 "Create document loader", which represents meaningful forward progress on the module's core capability. A document loader is the mechanism that allows the system to ingest and process content from various sources, a foundational requirement for any project that aims to handle unstructured data at scale. This is a substantial contribution, reflecting a significant amount of new work. However, the merge request is still open and awaiting review, meaning the work has not yet been formally accepted into the project.

No issues were updated and no commits were merged during this period, so the project's overall pace remains measured. Getting this contribution reviewed and approved in a timely manner would help maintain momentum.

How can I help on this project?

Consider whether additional reviewers or dedicated review time can be resourced to avoid contributions stalling in queue. If this module supports a broader organisational initiative, reinforcing its strategic priority to relevant teams can help accelerate decisions. Funding for a dedicated maintainer could also reduce bottlenecks significantly.
---
Drupal Canvas

Activity Summary

The past 24 hours saw meaningful development momentum on Drupal Canvas, with several merge requests either completed or actively progressing across two important capability areas.

Two merge requests were closed, indicating resolved work around how formatted text components render and how multi-value content fields behave. These fixes, contributed by Shubham Prakash (shubham.prakash), address editor-facing issues that could affect the reliability and consistency of content entry experiences.

On the translation front, Ted Bowman (tedbow) is progressing a significant piece of work via the Draft: Resolve #3583684 "Symmetric content inputs" merge request. This brings translation support for content managed through Canvas into parity with configuration-based content, an important step for teams managing multilingual sites.

Ben Mullins (bnjmnm) is driving multiple parallel proposals around the handling of multi-value fields, including Resolve #3587472 "Backend Widget solution" and a substantial wider effort tracked in Draft: Post multivalue reroll. The volume of open proposals on this topic suggests the team is working to converge on the right long-term approach, which warrants attention to avoid prolonged indecision.

How can I help on this project?

Consider encouraging decision-makers to review the competing multi-value field proposals and align on a preferred direction, as unresolved options can slow delivery. Ensuring dedicated reviewer capacity is available will help close out open drafts faster. Sponsoring or prioritising the translation work could also unlock significant value for multilingual rollouts.
---
Context Control Center (CCC)

The past 24 hours saw the Beta 2 release land and a strong wave of quality and stability work close out Sprint 9, while Sprint 10 planning and new feature development got underway in parallel.

Beta 2 Delivered and Stabilised

The Create CCC beta2 release milestone was reached and closed during this period. Immediately after the release, the team addressed several issues that surfaced, including fatal errors when uninstalling CCC and a missing navigation icon caused by a menu change -- both fixed and merged within hours by Kristen Pol (kepol). A round of beta2 QA was also completed and closed.

Significant Feature and Integration Work in Progress

Two separate contributors -- scott falconer (scottfalconer) and George Kastanis (zorz) -- have submitted proposals to add a new Site Architecture context source. This capability would automatically map how a Drupal site is structured and make that understanding available to AI agents, reducing the risk of agents taking incorrect or redundant actions. A proposal to integrate CCC with the Document Loader module is also open, which would allow users to feed PDFs, markdown files, and URLs directly as AI context sources. Jesse Hofmann-Smith (jessehs) has an open contribution to inject context into the rich text editor's AI tools, extending CCC's reach into everyday content editing.

Sprint 10 Planning and the Road to 1.0

Kristen Pol (kepol) formally opened Sprint 10 planning, which runs through 29 May. The focus is on closing remaining gaps before a Release Candidate, including updated user interface designs now being implemented by Aidan Foster (aidanfoster) and Eric Homanchuk (erichomanchuk), documentation improvements, and a QA testing script needed before the Zoocha team can carry out pre-1.0 testing. A configuration walkthrough video is also planned to address reported difficulties with the initial setup experience. Upcoming public appearances -- including presentations at the NYC Drupal AI Summit and DrupalSouth Wellington -- will help grow awareness ahead of the 1.0 release targeted for June.

How can I help on this project?

Prioritise QA resourcing: The team needs a dedicated QA effort before the Release Candidate. Confirming availability of the Zoocha testing team or equivalent resource now would prevent a bottleneck in June.

Support community visibility: Endorsing or amplifying the upcoming conference presentations would strengthen adoption ahead of the 1.0 launch.

Unblock contributor access: Ensuring regular contributors have the platform access they need to collaborate fully remains an open action that leadership can expedite.

======================================================================== ## [13] generate2026Capabilities ======================================================================== You are an editor writing a strategic section for a non-technical executive audience. The Drupal AI initiative has 8 planned capabilities for 2026. Your task is to read the module activity summaries below and explain how today's progress moves each capability forward — or note where there was no relevant progress today. Be concise and direct. Focus on what matters to a business leader: is progress happening, what is the next milestone, and are there any risks? Output an HTML fragment using exactly this structure:
2026 Capabilities Progress

Capability name — One or two sentences on how today's activity relates to this goal, or "No direct progress today" if nothing relevant occurred.

Use only the 8 capabilities listed below, in the same order. Do not add, remove, or rename them. Do not output any text outside the
and
tags. --- 2026 CAPABILITIES --- 1. Page generation — Describe what you need and get a usable page, built from your actual design system components 2. Context management — A central place to define brand voice, style guides, audience profiles, and governance rules that AI can use 3. Background agents — AI that works without being prompted, responding to triggers and schedules while respecting editorial workflows 4. Design system integration — AI that builds with your components and can propose new ones when needed 5. Content creation and discovery — Smarter search, AI-powered optimization, and content drafting assistance 6. Advanced governance — Batch approvals, branch-based versioning, and comprehensive audit trails for AI changes 7. Intelligent website improvements — AI that learns from performance data, proposes concrete changes, and gets smarter over time through editorial review 8. Multi-channel campaigns — Create content for websites, social, email, and automation platforms from a single campaign goal --- TODAY'S MODULE SUMMARIES ---
AI (Artificial Intelligence)

Sprint in Progress: Reliability, Usability, and Quality

The past 24 hours have seen sustained momentum across the AI module, with multiple workstreams advancing in parallel. The focus is on making AI-powered content features more reliable, consistent, and easier to configure for site builders and editors.

A significant area of activity is the Automators component, which automates AI-driven field population on content. Several efforts are converging here: work to improve how AI providers are selected and configured is progressing through two open proposals, and a separate effort aims to standardise how the Automators component processes and returns AI output -- making it more predictable and less error-prone. Alongside this, Pieter Frenssen (pfrenssen) identified and submitted a fix for a crash that occurs when automating certain core content fields, a real-world reliability issue that could affect editors using this feature today.

On the AI Agent front, Bruno Bruno (bbruno) has submitted work on a new visual editor for configuring agent tools, replacing a complex manual process with an interactive interface. This directly reduces the barrier to setting up AI agents for non-technical users.

Smaller but important progress includes a documentation improvement for developer conventions, which supports long-term project maintainability, and ongoing work to enable the AI-powered text editor to be aware of the content context it is operating within.

How can I help on this project?

Leaders can support progress by ensuring contributors working on Automators improvements have dedicated time to reach completion, as several related proposals risk stalling without coordination. Advocating for UX review resources would help unblock the agent tools editor. Encouraging organisational testing of the Automators crash fix would validate it for faster merge.
---
Drupal AI Initiative

Chicago DrupalCon Demo Preparations Underway

Activity over the past 24 hours has been focused on polishing the AI demonstration materials ahead of the Chicago DrupalCon Driesnote, a high-profile public showcase of Drupal's AI capabilities. Two issues are being addressed to ensure the demo is ready and reproducible.

First, work is underway on Update Chicago Driesnote repo to include demo prompts, which involves capturing the key AI interaction scripts in a shareable format so that anyone setting up the demo environment has clear, consistent prompts to work from. This reduces the risk of an inconsistent or underwhelming live demonstration.

Second, Kristen Pol (kepol) has picked up Fix RAG search on Chicago Driesnote repo install, addressing a known failure in the AI-powered search feature that is central to the demo. Without this fix, a core part of the showcase would not function as intended in front of a large audience.

No code was merged or committed in this period, so the immediate priority is resolving these issues before the event deadline.

How can I help on this project?

Leaders can support progress by confirming the timeline and any hard deadlines for the Chicago demo, ensuring the team has adequate capacity to resolve these issues in time. If external contributors or vendor support are needed to accelerate testing, approving that resourcing quickly would reduce risk to the public showcase.
---
Unstructured

Summary

Activity on the Unstructured module over the past 24 hours was focused on a single area of development. Ahmad Khader (Ahmad-Khader) opened a new merge request, Resolve #3582438 "Create document loader", which represents meaningful forward progress on the module's core capability. A document loader is the mechanism that allows the system to ingest and process content from various sources, a foundational requirement for any project that aims to handle unstructured data at scale. This is a substantial contribution, reflecting a significant amount of new work. However, the merge request is still open and awaiting review, meaning the work has not yet been formally accepted into the project.

No issues were updated and no commits were merged during this period, so the project's overall pace remains measured. Getting this contribution reviewed and approved in a timely manner would help maintain momentum.

How can I help on this project?

Consider whether additional reviewers or dedicated review time can be resourced to avoid contributions stalling in queue. If this module supports a broader organisational initiative, reinforcing its strategic priority to relevant teams can help accelerate decisions. Funding for a dedicated maintainer could also reduce bottlenecks significantly.
---
Drupal Canvas

Activity Summary

The past 24 hours saw meaningful development momentum on Drupal Canvas, with several merge requests either completed or actively progressing across two important capability areas.

Two merge requests were closed, indicating resolved work around how formatted text components render and how multi-value content fields behave. These fixes, contributed by Shubham Prakash (shubham.prakash), address editor-facing issues that could affect the reliability and consistency of content entry experiences.

On the translation front, Ted Bowman (tedbow) is progressing a significant piece of work via the Draft: Resolve #3583684 "Symmetric content inputs" merge request. This brings translation support for content managed through Canvas into parity with configuration-based content, an important step for teams managing multilingual sites.

Ben Mullins (bnjmnm) is driving multiple parallel proposals around the handling of multi-value fields, including Resolve #3587472 "Backend Widget solution" and a substantial wider effort tracked in Draft: Post multivalue reroll. The volume of open proposals on this topic suggests the team is working to converge on the right long-term approach, which warrants attention to avoid prolonged indecision.

How can I help on this project?

Consider encouraging decision-makers to review the competing multi-value field proposals and align on a preferred direction, as unresolved options can slow delivery. Ensuring dedicated reviewer capacity is available will help close out open drafts faster. Sponsoring or prioritising the translation work could also unlock significant value for multilingual rollouts.
---
Context Control Center (CCC)

The past 24 hours saw the Beta 2 release land and a strong wave of quality and stability work close out Sprint 9, while Sprint 10 planning and new feature development got underway in parallel.

Beta 2 Delivered and Stabilised

The Create CCC beta2 release milestone was reached and closed during this period. Immediately after the release, the team addressed several issues that surfaced, including fatal errors when uninstalling CCC and a missing navigation icon caused by a menu change -- both fixed and merged within hours by Kristen Pol (kepol). A round of beta2 QA was also completed and closed.

Significant Feature and Integration Work in Progress

Two separate contributors -- scott falconer (scottfalconer) and George Kastanis (zorz) -- have submitted proposals to add a new Site Architecture context source. This capability would automatically map how a Drupal site is structured and make that understanding available to AI agents, reducing the risk of agents taking incorrect or redundant actions. A proposal to integrate CCC with the Document Loader module is also open, which would allow users to feed PDFs, markdown files, and URLs directly as AI context sources. Jesse Hofmann-Smith (jessehs) has an open contribution to inject context into the rich text editor's AI tools, extending CCC's reach into everyday content editing.

Sprint 10 Planning and the Road to 1.0

Kristen Pol (kepol) formally opened Sprint 10 planning, which runs through 29 May. The focus is on closing remaining gaps before a Release Candidate, including updated user interface designs now being implemented by Aidan Foster (aidanfoster) and Eric Homanchuk (erichomanchuk), documentation improvements, and a QA testing script needed before the Zoocha team can carry out pre-1.0 testing. A configuration walkthrough video is also planned to address reported difficulties with the initial setup experience. Upcoming public appearances -- including presentations at the NYC Drupal AI Summit and DrupalSouth Wellington -- will help grow awareness ahead of the 1.0 release targeted for June.

How can I help on this project?

Prioritise QA resourcing: The team needs a dedicated QA effort before the Release Candidate. Confirming availability of the Zoocha testing team or equivalent resource now would prevent a bottleneck in June.

Support community visibility: Endorsing or amplifying the upcoming conference presentations would strengthen adoption ahead of the 1.0 launch.

Unblock contributor access: Ensuring regular contributors have the platform access they need to collaborate fully remains an open action that leadership can expedite.