# Prompt log — 24h 2026-06-27 ======================================================================== ## [1] summariseModule:ai:developer ======================================================================== 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Artem Dmitriiev (a.dmitriiev)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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 developer. Suggest 2-3 concrete technical actions a contributor could take right now. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- 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). ### [Config action to verify if any vector database is there and it is setup](https://git.drupalcode.org/project/ai/-/work_items/3586517) State: opened | Updated: 2026-06-27 | Author: Artem Dmitriiev (a.dmitriiev) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiCoreModule, category::feature Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1660 [Issue #3586517: Check if any Vdb provider is setup](https://git.drupalcode.org/project/ai/-/merge_requests/1660) | State: opened | Author: Artem Dmitriiev (a.dmitriiev), 75 diff lines Description: ## Summary At the moment there is a config action `verifySetupAi` that is able to check whether the specific vector database provider is there in the system and it is setup. This is possible with `vdb_provider_is_setup` payload. In the real use case the plugin name of the vdb provider is not that relevant, as it is needed to know that any vdb provider is there and it is properly configured (setup) to create a search api server. One (any) would be enough without actually specifying which one. ## Problem There is no way at the moment to check that any vdb provider is installed and configured… --- MERGE REQUESTS (24h) --- (none) --- 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. Do not name any individual people in this section. No one was active enough this period to list. 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. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- 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). ### [Drupal AI UX meeting 22 June 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3584834) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: category::task, meetings, priority::normal, state::accepted Description: ## **Meeting Overview** **Date:** Monday, June 22, 2026 **Attendees:** Aidan, Marcus, Bruno, Emma, Darren, Vidit, Ángela ### **Canvas AI build-state UX** * Generation now runs component by component; editing the canvas mid-build breaks it, so the canvas locks during a build * Build UI: a Stop and a separate Stop-and-undo on the chat, a building indicator, and an optional follow-along scroll * Planning step renders as gray placeholder boxes in the canvas (Lovable-style), with a thumbnail minimap for orientation * Model is a quality/cost/speed dial (Opus best but slow and pricey; mini models … ### [Drupal AI UX meeting 15 June 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3584833) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: category::task, meetings, priority::normal, state::accepted Description: **Attendees:** Aidan, Marcus, Rob Loach, Emma, Darren, Vidit, Kati (first time joining) ### **AI ecosystem page (RobLoach)** * New searchable, filterable list of AI modules and recipes, shipped in the AI Dashboard module * Module list is for advanced site builders and developers; recipes are the site-builder surface * AI Initiative maintained shown as a filter plus badge, not a list limiter; support flag is tiered, not Boolean * Add a GitLab API search for modules requiring drupal/ai, which finds about 40% more ### **Categories and naming** * Reconcile the page filters with the existing AI… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [3] 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- 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). ### [WSOD AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job](https://git.drupalcode.org/project/canvas/-/work_items/3591734) State: opened | Updated: 2026-06-27 | Author: Gábor Hojtsy (goba) | Assigned: Narendra Singh Rathore (NarendraR) | Labels: translation Description: I went to try Canvas 1.7.0 translation today with a brand new install of Drupal CMS Haven. I don't think the issue is due to Haven, so submitting here. I think previously this config form had separate settings under the components for the tree and inputs but that is not an option that I have for some reason, so this is how I have it set up. ![Screenshot 2026-06-26 at 11.29.44.png](https://git.drupalcode.org/-/project/19391/uploads/fe3690f7cf31f5eafd12c4cf6de93f29/Screenshot_2026-06-26_at_11.29.44.png){width="755" height="600"} I have `canvas_dev_translation` enabled and `content|config|inte… --- MERGE REQUESTS (24h) --- ### [fix(deps): update npm minor and patch](https://git.drupalcode.org/project/canvas/-/merge_requests/1238) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/npm-minor-and-patch | 77 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) | [`4.11.1` → `4.11.3`](https://renovatebot.com/diffs/npm/@axe-core%2fplaywright/4.11.1/4.11.3) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@axe-core%2fplaywright/4.11.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@axe-core%2fplaywright/4.11.1/4.11.3?slim=true) | | [@babel/parser](… ### [Draft: #3492065 move to canvas repo](https://git.drupalcode.org/project/canvas/-/merge_requests/709) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3492065-concur-2026 | 6856 diff lines Description: Closes #3492065 --- COMMITS (24h) --- (none) ======================================================================== ## [4] 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- 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). ### [Fix eslint errors in GitLab UI even when pipeline is green](https://git.drupalcode.org/project/ai_context/-/work_items/3576093) State: closed | Updated: 2026-06-28 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !197 [Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green.](https://git.drupalcode.org/project/ai_context/-/merge_requests/197) | State: merged 2026-06-28 | Author: Kristen Pol (kepol), 130 diff lines 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… ### [CCC beta3 QA](https://git.drupalcode.org/project/ai_context/-/work_items/3586296) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ## Problem/Motivation Need a QA script for beta 3 to go through and test before the release ## Proposed resolution Create script with at least all major features covered ## Target date or deadline **6 July 2026** ## Remaining tasks - Create script - Go through QA script --- ## 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 Generate… ### [Create CCC beta3 release](https://git.drupalcode.org/project/ai_context/-/work_items/3586295) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ### Problem/Motivation Create CCC beta3 release. Tag: `1.0.0-beta3` ### Proposed resolution Create the release once at least the must-haves are done here: - #3586182+s - [beta3 milestone](https://git.drupalcode.org/project/ai_context/-/milestones/5#tab-issues) ### Target date or deadline 6 July 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 … ### [CCC beta3 codebase review (pre-release)](https://git.drupalcode.org/project/ai_context/-/work_items/3586294) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ## Problem/motivation Beta3 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 (major issues will not be reported here) ## Next steps - Run security review - Run performance review - Run api/feature review - Attach findings for here (not major security issues) - Create follow-up issues as ne… ### [Test AI Best Practices skills on AI Context codebase](https://git.drupalcode.org/project/ai_context/-/work_items/3586258) State: closed | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation We have a project with skills (among other things) to help with Drupal coding called [AI Best Practices](https://www.drupal.org/project/ai_best_practices). AI Context (CCC) development heavily uses AI assigned and generated code. It may benefit from using the best practice skills. Right now there are these skills: - drupal-accessibility - drupal-automated-testing - drupal-configuration - drupal-expert-corrections - drupal-gitlab - drupal-render-pipeline - drupal-writing-documentation ## Solution Install skills from AI Best Practices and run a through code review with… ### [[Discuss] Moderation status of subcontext vs parent context items](https://git.drupalcode.org/project/ai_context/-/work_items/3586264) State: closed | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation You can unpublish a parent context item while having published subcontext items. ## Solution Discuss what makes sense for the moderation of parent/child items. ## Tasks - [x] Discuss and decide on behavior - [x] ~~Create follow-up issues as needed~~ (did MR on this issue) ### [Add warning on subcontext edit form if parent is unpublished](https://git.drupalcode.org/project/ai_context/-/work_items/3586297) State: closed | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !196 [Issue #3586297: Add warning on subcontext edit form if parent is unpublished.](https://git.drupalcode.org/project/ai_context/-/merge_requests/196) | State: merged 2026-06-27 | Author: Kristen Pol (kepol), 197 diff lines Description: ## Problem/motivation Follow-up to: #3586264+s You can unpublish a parent context item while having published subcontext items. ## Solution Show a warning. ## Acceptance criteria - [x] If parent published and subcontext unpublished, do not show warning. - [x] If parent unpublished and subcontext unpublished, do not show warning. - [x] If parent published and subcontext published, do not show warning. - [x] If parent unpublished and subcontext published, show warning. ### [Inject context into ai_ckeditor requests](https://git.drupalcode.org/project/ai_context/-/work_items/3581955) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !116 [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), 479 diff lines 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. … ### [CCC beta / pre-rc1 community testing](https://git.drupalcode.org/project/ai_context/-/work_items/3586234) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: Michael Anello (ultimike) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 11 Description: ## Problem/motivation We want to get feedback from the community on CCC as we want to lock down our features soon so we can release rc1 and ultimately 1.0 soon. ## Solution Recruit CCC testers to help with this. ## Resources - [Project page](https://www.drupal.org/project/ai_context) - [Setup instructions](https://www.drupal.org/project/ai_context#install-testing-steps) - [Documentation](https://git.drupalcode.org/project/ai_context/-/tree/1.0.x/docs?ref_type=heads) - [NYC AI summit session](https://drupal.tv/events/drupal-ai-summit-new-york-city-2026/context-driven-ai-consistent-complian… ### [Align context item full view with bundle-less entity](https://git.drupalcode.org/project/ai_context/-/work_items/3586261) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !198 [Issue #3586261: Align context item full view with bundle-less entity.](https://git.drupalcode.org/project/ai_context/-/merge_requests/198) | State: opened | Author: Kristen Pol (kepol) Description: Follow-up to: #3586220 once this is merged: ##3584775 --- ## Follow-up: Remove `ai_context_item` bundle (`ai_context_item_type`) Here’s a **view-branch-only** follow-up list for whoever lands bundle removal. Everything else in the module is their problem; this is what **this MR** introduced that still assumes a bundle. --- ## After bundle removal — reconcile with view MR (`3586220`) ### Must update (behavior/config) 1. **`hook_theme_suggestions_ai_context_item()`** (`ai_context.module`, chunk 10) Remove the two bundle lines: ```php $suggestions[] = 'ai_context_item__' . $e… ### [Add CCC beta tester info to the project page](https://git.drupalcode.org/project/ai_context/-/work_items/3586248) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 13, category::task Description: ## Problem/motivation We want beta testers, but we need to give them more info on how to get started. ## Solution Update the home page with some more information: - Links to session videos (suggest they watch one) - Link to DrupalCon Chicago Driesnote demo (they can use it and it will have example context to play with) - Point to the readme and docs - Point to how to create a support issue or bug ## Tasks - Gather session videos - Gather other links - Create a section on project page for beta testers - Add the videos and links ### [UX improvements on new context listing page](https://git.drupalcode.org/project/ai_context/-/work_items/3586274) State: closed | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation Follow up to: #3586219 Pasting from UX review call on 17 June: 1. Collapse Use Cases and Scope columns Order pills in order shown on the edit page (e.g. Use Cases first) 2. Filters - Remove Use Cases filter - Change how Scope filter works - One dropdown with the scope names, e.g. Use Cases, Site Sections, etc (ordered by order on edit page) - Dropdown defaults to "All" - Second dropdown that shows the values from what you choose from first drop down - All shows all values like now - if you choose a specific scope name, then it will restrict to that one, e… ### [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-06-27 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 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),… --- MERGE REQUESTS (24h) --- ### [Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter](https://git.drupalcode.org/project/ai_context/-/merge_requests/184) State: merged 2026-06-27 | Author: Matt Glaman (mglaman) | Branch: 3586274-issue-branch | 1135 diff lines Description: ## Description Implements the finalized UX from the 17 June review (see issue), following up #3586219. **Columns** - Merge the **Use cases** and **Scope** columns into a single **Scopes** column. Pills are ordered as on the edit page (scope plugins are weight-sorted, so Use Cases lead). **Filters** - Remove the standalone **Use cases** filter. - Replace the single scope filter with a cascade: - First select: scope name (ordered as the edit page), defaulting to **All scopes**. - Second select: values for the chosen scope, defaulting to **All**. With "All scopes" selected it lists every… --- COMMITS (24h) --- - [55bceeb9](https://git.drupalcode.org/project/ai_context/-/commit/55bceeb9efca4ea613af0bc8f632928f07a0f2db) Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green. — Kristen Pol (2026-06-28T01:30:54.000+00:00) - [da3549d8](https://git.drupalcode.org/project/ai_context/-/commit/da3549d824ac126399e2e765e673bd6e9830c81f) Issue #3586297: Add warning on subcontext edit form if parent is unpublished. — Kristen Pol (2026-06-27T21:09:55.000+00:00) - [35098852](https://git.drupalcode.org/project/ai_context/-/commit/3509885235b6c3ca00c97f34d3ec72cc9be7f689) Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter — Matt Glaman (2026-06-27T18:52:52.000+00:00) ======================================================================== ## [5] 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. When you mention a specific issue or merge request, add an inline citation using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations immediately after the relevant phrase, before any punctuation. Format as two HTML sections. Use exactly this structure (all
        • elements must be inside the
            , never outside it):

            Shipped

            1. Title here — One sentence explanation [1].
            2. Another title — One sentence explanation.

            Ongoing

            1. Title here — One sentence explanation [2].
            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. --- REFERENCE LIST --- [1] Config action to verify if any vector database is there and it is setup (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586517 [2] Issue #3586517: Check if any Vdb provider is setup (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1660 [3] Drupal AI UX meeting 22 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584834 [4] Drupal AI UX meeting 15 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584833 [5] WSOD AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591734 [6] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [7] Draft: #3492065 move to canvas repo (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/709 [8] Fix eslint errors in GitLab UI even when pipeline is green (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3576093 [9] CCC beta3 QA (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586296 [10] Create CCC beta3 release (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586295 [11] CCC beta3 codebase review (pre-release) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586294 [12] Test AI Best Practices skills on AI Context codebase (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586258 [13] [Discuss] Moderation status of subcontext vs parent context items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586264 [14] Add warning on subcontext edit form if parent is unpublished (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586297 [15] Inject context into ai_ckeditor requests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3581955 [16] CCC beta / pre-rc1 community testing (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586234 [17] Align context item full view with bundle-less entity (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586261 [18] Add CCC beta tester info to the project page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586248 [19] UX improvements on new context listing page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586274 [20] Gather CCC contribution stats for code and non-code contributions for release notes (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586222 [21] Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/197 [22] Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/116 [23] Issue #3586297: Add warning on subcontext edit form if parent is unpublished. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/196 [24] Issue #3586261: Align context item full view with bundle-less entity. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/198 [25] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/184 --- MODULE SUMMARIES ---

            AI (Artificial Intelligence)

            Activity in the AI module over the past 24 hours focused on configuration validation improvements. Work continued on Config action to verify if any vector database is there and it is setup, which extends the existing verifySetupAi config action. Currently, the action can check for a specific vector database provider using the vdb_provider_is_setup payload, but cannot verify that any configured VDB provider exists without specifying a plugin name. The related MR !1660 remains open for review, adding this capability to support use cases where any properly configured vector database provider is sufficient for creating a Search API server.

            No merge requests were merged and no commits were pushed during this period.

            How can I help on this project?

            • Review MR !1660 to provide feedback on the config action logic for detecting any configured vector database provider.
            • Test the proposed changes against different VDB provider configurations to ensure the verification works as expected.

            Contributors: Artem Dmitriiev (a.dmitriiev)

            ---

            Drupal AI Initiative

            The Drupal AI Initiative saw documentation and planning activity this period, with meeting notes published for both the Drupal AI UX meeting 15 June 2026 and Drupal AI UX meeting 22 June 2026. The June 22 meeting covered Canvas AI build-state UX improvements, including component-by-component generation with canvas locking during builds, build controls (stop and stop-and-undo), and a quality/cost/speed model selection dial. The June 15 meeting focused on the AI ecosystem page in the AI Dashboard module, which provides a searchable, filterable list of AI modules and recipes for site builders and developers, with plans to integrate GitLab API search to discover additional modules requiring drupal/ai.

            No merge requests were merged and no commits were pushed during this period. Development activity appears focused on design and coordination work rather than code changes.

            How can I help on this project?

            Review the UX meeting notes to understand current design direction and join upcoming meetings to contribute to planning. Explore the AI Dashboard module code to help implement the GitLab API search feature for discovering AI-related modules. Test existing AI functionality and report bugs or UX friction points.

            ---

            Drupal Canvas

            A translation-related issue surfaced during the reporting period. When requesting TMGMT translation jobs with Canvas 1.7.0 on a fresh Drupal CMS Haven install, an AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job was reported. The white screen of death occurs with canvas_dev_translation enabled, and the issue appears related to how component tree and input settings are configured, though previous configuration options are no longer available. The issue remains open and under investigation.

            On the dependency front, fix(deps): update npm minor and patch was opened to update @axe-core/playwright from 4.11.1 to 4.11.3 along with other npm package updates. Additionally, a draft merge request titled Draft: #3492065 move to canvas repo remains open with 6,856 diff lines, indicating a significant repository reorganization effort in progress.

            How can I help on this project?

            Review the open dependency update MR to ensure compatibility. Investigate the TMGMT translation assertion error by reproducing it with canvas_dev_translation and identifying which component configuration triggers the ComponentInputsMapping assertion failure.

            Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm) ---

            Context Control Center (CCC)

            Three merge requests landed during the reporting period, addressing UI polish and developer experience ahead of the upcoming beta3 release. Fix eslint errors in GitLab UI even when pipeline is green was merged to resolve lint warnings displayed in the GitLab test summary despite passing pipelines. Add warning on subcontext edit form if parent is unpublished was merged, introducing a form-level warning when a published subcontext has an unpublished parent, following discussion in the now-closed moderation status issue.

            The most substantial change merged was UX improvements on new context listing page, consolidating the Use Cases and Scope columns into a single Scopes column with ordered pills, and replacing the standalone filters with a cascading scope filter mechanism. The first dropdown selects scope name (defaulting to All scopes), while the second dropdown dynamically filters values.

            Preparation for the beta3 release (target 6 July 2026) is underway, with open issues for QA scripting, codebase review, and the release itself. An open merge request for Inject context into ai_ckeditor requests remains under review, introducing an EventSubscriber to bridge ai_context with ai_ckeditor's direct provider calls.

            How can I help on this project?

            Review MR !116 for ai_ckeditor context injection, which adds an EventSubscriber to handle scope-matched context items. Help finalize MR !198 aligning context item full view with the bundle-less entity refactor. Contribute to beta testing by following setup instructions and reporting findings.

            Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1]

            ======================================================================== ## [6] factcheck:tldr:developer ======================================================================== Layer-1 corrections: 0 Judge flags: 0 ======================================================================== ## [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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+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. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Artem Dmitriiev (a.dmitriiev)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- 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). ### [Config action to verify if any vector database is there and it is setup](https://git.drupalcode.org/project/ai/-/work_items/3586517) State: opened | Updated: 2026-06-27 | Author: Artem Dmitriiev (a.dmitriiev) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Product Development, aiCoreModule, category::feature Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1660 [Issue #3586517: Check if any Vdb provider is setup](https://git.drupalcode.org/project/ai/-/merge_requests/1660) | State: opened | Author: Artem Dmitriiev (a.dmitriiev), 75 diff lines Description: ## Summary At the moment there is a config action `verifySetupAi` that is able to check whether the specific vector database provider is there in the system and it is setup. This is possible with `vdb_provider_is_setup` payload. In the real use case the plugin name of the vdb provider is not that relevant, as it is needed to know that any vdb provider is there and it is properly configured (setup) to create a search api server. One (any) would be enough without actually specifying which one. ## Problem There is no way at the moment to check that any vdb provider is installed and configured… --- MERGE REQUESTS (24h) --- (none) --- 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+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. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. Do not name any individual people in this section. No one was active enough this period to list. 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. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- 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). ### [Drupal AI UX meeting 22 June 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3584834) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: category::task, meetings, priority::normal, state::accepted Description: ## **Meeting Overview** **Date:** Monday, June 22, 2026 **Attendees:** Aidan, Marcus, Bruno, Emma, Darren, Vidit, Ángela ### **Canvas AI build-state UX** * Generation now runs component by component; editing the canvas mid-build breaks it, so the canvas locks during a build * Build UI: a Stop and a separate Stop-and-undo on the chat, a building indicator, and an optional follow-along scroll * Planning step renders as gray placeholder boxes in the canvas (Lovable-style), with a thumbnail minimap for orientation * Model is a quality/cost/speed dial (Opus best but slow and pricey; mini models … ### [Drupal AI UX meeting 15 June 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3584833) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: category::task, meetings, priority::normal, state::accepted Description: **Attendees:** Aidan, Marcus, Rob Loach, Emma, Darren, Vidit, Kati (first time joining) ### **AI ecosystem page (RobLoach)** * New searchable, filterable list of AI modules and recipes, shipped in the AI Dashboard module * Module list is for advanced site builders and developers; recipes are the site-builder surface * AI Initiative maintained shown as a filter plus badge, not a list limiter; support flag is tiered, not Boolean * Add a GitLab API search for modules requiring drupal/ai, which finds about 40% more ### **Categories and naming** * Reconcile the page filters with the existing AI… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [9] 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+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. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- 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). ### [WSOD AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job](https://git.drupalcode.org/project/canvas/-/work_items/3591734) State: opened | Updated: 2026-06-27 | Author: Gábor Hojtsy (goba) | Assigned: Narendra Singh Rathore (NarendraR) | Labels: translation Description: I went to try Canvas 1.7.0 translation today with a brand new install of Drupal CMS Haven. I don't think the issue is due to Haven, so submitting here. I think previously this config form had separate settings under the components for the tree and inputs but that is not an option that I have for some reason, so this is how I have it set up. ![Screenshot 2026-06-26 at 11.29.44.png](https://git.drupalcode.org/-/project/19391/uploads/fe3690f7cf31f5eafd12c4cf6de93f29/Screenshot_2026-06-26_at_11.29.44.png){width="755" height="600"} I have `canvas_dev_translation` enabled and `content|config|inte… --- MERGE REQUESTS (24h) --- ### [fix(deps): update npm minor and patch](https://git.drupalcode.org/project/canvas/-/merge_requests/1238) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/npm-minor-and-patch | 77 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) | [`4.11.1` → `4.11.3`](https://renovatebot.com/diffs/npm/@axe-core%2fplaywright/4.11.1/4.11.3) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@axe-core%2fplaywright/4.11.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@axe-core%2fplaywright/4.11.1/4.11.3?slim=true) | | [@babel/parser](… ### [Draft: #3492065 move to canvas repo](https://git.drupalcode.org/project/canvas/-/merge_requests/709) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3492065-concur-2026 | 6856 diff lines Description: Closes #3492065 --- COMMITS (24h) --- (none) ======================================================================== ## [10] 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-06-27T05:00:05+00:00 to 2026-06-28T05:00:05+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. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. 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. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. 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. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- 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). ### [Fix eslint errors in GitLab UI even when pipeline is green](https://git.drupalcode.org/project/ai_context/-/work_items/3576093) State: closed | Updated: 2026-06-28 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !197 [Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green.](https://git.drupalcode.org/project/ai_context/-/merge_requests/197) | State: merged 2026-06-28 | Author: Kristen Pol (kepol), 130 diff lines 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… ### [CCC beta3 QA](https://git.drupalcode.org/project/ai_context/-/work_items/3586296) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ## Problem/Motivation Need a QA script for beta 3 to go through and test before the release ## Proposed resolution Create script with at least all major features covered ## Target date or deadline **6 July 2026** ## Remaining tasks - Create script - Go through QA script --- ## 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 Generate… ### [Create CCC beta3 release](https://git.drupalcode.org/project/ai_context/-/work_items/3586295) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ### Problem/Motivation Create CCC beta3 release. Tag: `1.0.0-beta3` ### Proposed resolution Create the release once at least the must-haves are done here: - #3586182+s - [beta3 milestone](https://git.drupalcode.org/project/ai_context/-/milestones/5#tab-issues) ### Target date or deadline 6 July 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 … ### [CCC beta3 codebase review (pre-release)](https://git.drupalcode.org/project/ai_context/-/work_items/3586294) State: opened | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Description: ## Problem/motivation Beta3 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 (major issues will not be reported here) ## Next steps - Run security review - Run performance review - Run api/feature review - Attach findings for here (not major security issues) - Create follow-up issues as ne… ### [Test AI Best Practices skills on AI Context codebase](https://git.drupalcode.org/project/ai_context/-/work_items/3586258) State: closed | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation We have a project with skills (among other things) to help with Drupal coding called [AI Best Practices](https://www.drupal.org/project/ai_best_practices). AI Context (CCC) development heavily uses AI assigned and generated code. It may benefit from using the best practice skills. Right now there are these skills: - drupal-accessibility - drupal-automated-testing - drupal-configuration - drupal-expert-corrections - drupal-gitlab - drupal-render-pipeline - drupal-writing-documentation ## Solution Install skills from AI Best Practices and run a through code review with… ### [[Discuss] Moderation status of subcontext vs parent context items](https://git.drupalcode.org/project/ai_context/-/work_items/3586264) State: closed | Updated: 2026-06-28 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation You can unpublish a parent context item while having published subcontext items. ## Solution Discuss what makes sense for the moderation of parent/child items. ## Tasks - [x] Discuss and decide on behavior - [x] ~~Create follow-up issues as needed~~ (did MR on this issue) ### [Add warning on subcontext edit form if parent is unpublished](https://git.drupalcode.org/project/ai_context/-/work_items/3586297) State: closed | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !196 [Issue #3586297: Add warning on subcontext edit form if parent is unpublished.](https://git.drupalcode.org/project/ai_context/-/merge_requests/196) | State: merged 2026-06-27 | Author: Kristen Pol (kepol), 197 diff lines Description: ## Problem/motivation Follow-up to: #3586264+s You can unpublish a parent context item while having published subcontext items. ## Solution Show a warning. ## Acceptance criteria - [x] If parent published and subcontext unpublished, do not show warning. - [x] If parent unpublished and subcontext unpublished, do not show warning. - [x] If parent published and subcontext published, do not show warning. - [x] If parent unpublished and subcontext published, show warning. ### [Inject context into ai_ckeditor requests](https://git.drupalcode.org/project/ai_context/-/work_items/3581955) State: opened | Updated: 2026-06-27 | Author: drupalbot | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !116 [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), 479 diff lines 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. … ### [CCC beta / pre-rc1 community testing](https://git.drupalcode.org/project/ai_context/-/work_items/3586234) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: Michael Anello (ultimike) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 11 Description: ## Problem/motivation We want to get feedback from the community on CCC as we want to lock down our features soon so we can release rc1 and ultimately 1.0 soon. ## Solution Recruit CCC testers to help with this. ## Resources - [Project page](https://www.drupal.org/project/ai_context) - [Setup instructions](https://www.drupal.org/project/ai_context#install-testing-steps) - [Documentation](https://git.drupalcode.org/project/ai_context/-/tree/1.0.x/docs?ref_type=heads) - [NYC AI summit session](https://drupal.tv/events/drupal-ai-summit-new-york-city-2026/context-driven-ai-consistent-complian… ### [Align context item full view with bundle-less entity](https://git.drupalcode.org/project/ai_context/-/work_items/3586261) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !198 [Issue #3586261: Align context item full view with bundle-less entity.](https://git.drupalcode.org/project/ai_context/-/merge_requests/198) | State: opened | Author: Kristen Pol (kepol) Description: Follow-up to: #3586220 once this is merged: ##3584775 --- ## Follow-up: Remove `ai_context_item` bundle (`ai_context_item_type`) Here’s a **view-branch-only** follow-up list for whoever lands bundle removal. Everything else in the module is their problem; this is what **this MR** introduced that still assumes a bundle. --- ## After bundle removal — reconcile with view MR (`3586220`) ### Must update (behavior/config) 1. **`hook_theme_suggestions_ai_context_item()`** (`ai_context.module`, chunk 10) Remove the two bundle lines: ```php $suggestions[] = 'ai_context_item__' . $e… ### [Add CCC beta tester info to the project page](https://git.drupalcode.org/project/ai_context/-/work_items/3586248) State: opened | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Innovation, AI Sprint 13, category::task Description: ## Problem/motivation We want beta testers, but we need to give them more info on how to get started. ## Solution Update the home page with some more information: - Links to session videos (suggest they watch one) - Link to DrupalCon Chicago Driesnote demo (they can use it and it will have example context to play with) - Point to the readme and docs - Point to how to create a support issue or bug ## Tasks - Gather session videos - Gather other links - Create a section on project page for beta testers - Add the videos and links ### [UX improvements on new context listing page](https://git.drupalcode.org/project/ai_context/-/work_items/3586274) State: closed | Updated: 2026-06-27 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 12 Description: ## Problem/motivation Follow up to: #3586219 Pasting from UX review call on 17 June: 1. Collapse Use Cases and Scope columns Order pills in order shown on the edit page (e.g. Use Cases first) 2. Filters - Remove Use Cases filter - Change how Scope filter works - One dropdown with the scope names, e.g. Use Cases, Site Sections, etc (ordered by order on edit page) - Dropdown defaults to "All" - Second dropdown that shows the values from what you choose from first drop down - All shows all values like now - if you choose a specific scope name, then it will restrict to that one, e… ### [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-06-27 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: AI Context Management, AI Initiative Sprint, AI Innovation, AI Sprint 13 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),… --- MERGE REQUESTS (24h) --- ### [Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter](https://git.drupalcode.org/project/ai_context/-/merge_requests/184) State: merged 2026-06-27 | Author: Matt Glaman (mglaman) | Branch: 3586274-issue-branch | 1135 diff lines Description: ## Description Implements the finalized UX from the 17 June review (see issue), following up #3586219. **Columns** - Merge the **Use cases** and **Scope** columns into a single **Scopes** column. Pills are ordered as on the edit page (scope plugins are weight-sorted, so Use Cases lead). **Filters** - Remove the standalone **Use cases** filter. - Replace the single scope filter with a cascade: - First select: scope name (ordered as the edit page), defaulting to **All scopes**. - Second select: values for the chosen scope, defaulting to **All**. With "All scopes" selected it lists every… --- COMMITS (24h) --- - [55bceeb9](https://git.drupalcode.org/project/ai_context/-/commit/55bceeb9efca4ea613af0bc8f632928f07a0f2db) Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green. — Kristen Pol (2026-06-28T01:30:54.000+00:00) - [da3549d8](https://git.drupalcode.org/project/ai_context/-/commit/da3549d824ac126399e2e765e673bd6e9830c81f) Issue #3586297: Add warning on subcontext edit form if parent is unpublished. — Kristen Pol (2026-06-27T21:09:55.000+00:00) - [35098852](https://git.drupalcode.org/project/ai_context/-/commit/3509885235b6c3ca00c97f34d3ec72cc9be7f689) Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter — Matt Glaman (2026-06-27T18:52:52.000+00:00) ======================================================================== ## [11] 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. When you mention a specific issue or merge request, add an inline citation using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations immediately after the relevant phrase, before any punctuation. Format as two HTML sections. Use exactly this structure (all
                  • elements must be inside the
                      , never outside it):

                      Shipped

                      1. Title here — One sentence explanation [1].
                      2. Another title — One sentence explanation.

                      Ongoing

                      1. Title here — One sentence explanation [2].
                      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. --- REFERENCE LIST --- [1] Config action to verify if any vector database is there and it is setup (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586517 [2] Issue #3586517: Check if any Vdb provider is setup (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1660 [3] Drupal AI UX meeting 22 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584834 [4] Drupal AI UX meeting 15 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584833 [5] WSOD AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591734 [6] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [7] Draft: #3492065 move to canvas repo (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/709 [8] Fix eslint errors in GitLab UI even when pipeline is green (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3576093 [9] CCC beta3 QA (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586296 [10] Create CCC beta3 release (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586295 [11] CCC beta3 codebase review (pre-release) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586294 [12] Test AI Best Practices skills on AI Context codebase (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586258 [13] [Discuss] Moderation status of subcontext vs parent context items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586264 [14] Add warning on subcontext edit form if parent is unpublished (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586297 [15] Inject context into ai_ckeditor requests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3581955 [16] CCC beta / pre-rc1 community testing (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586234 [17] Align context item full view with bundle-less entity (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586261 [18] Add CCC beta tester info to the project page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586248 [19] UX improvements on new context listing page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586274 [20] Gather CCC contribution stats for code and non-code contributions for release notes (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586222 [21] Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/197 [22] Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/116 [23] Issue #3586297: Add warning on subcontext edit form if parent is unpublished. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/196 [24] Issue #3586261: Align context item full view with bundle-less entity. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/198 [25] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/184 --- MODULE SUMMARIES ---

                      AI (Artificial Intelligence)

                      The project saw continued development activity this period. Work is underway to improve configuration validation capabilities. Specifically, a new configuration action is being developed to verify that at least one vector database provider is installed and properly configured in the system, without requiring administrators to know which specific provider is present. This addresses a practical need: when setting up search functionality, the system currently cannot automatically detect whether any suitable database backend is ready, forcing users to manually verify setup details. The enhancement will streamline deployment and reduce configuration errors by allowing automated checks to confirm the environment is ready.

                      An associated merge request containing this functionality remains open for review. No code was merged during this period, reflecting ongoing development work typical for this stage of the module.

                      How can I help on this project?

                      • Ensure the team has access to code reviewers who can evaluate and merge open contributions in a timely manner.
                      • Clarify strategic priorities for upcoming releases to help contributors focus effort on the highest-value features.

                      Contributors: Artem Dmitriiev (a.dmitriiev)

                      ---

                      Drupal AI Initiative

                      The Drupal AI Initiative held two user experience meetings during the period, focusing on interface design and ecosystem organization. The June 22 meeting reviewed progress on AI-assisted canvas building, where the interface now locks during generation to prevent editing conflicts and provides visual feedback through placeholder boxes and progress indicators. Quality and cost tradeoffs are being surfaced through a simplified model selection interface.

                      The June 15 meeting discussed a new searchable directory of AI modules and recipes designed to help site builders discover and evaluate tools. The directory will distinguish between initiative-maintained components and community contributions, with tiered support indicators to help users assess maturity and backing.

                      Both meetings signal ongoing work to make AI capabilities more discoverable and usable for non-technical site builders, which supports broader adoption of the initiative's deliverables.

                      How can I help on this project?

                      • Champion clarity on support tiers and maintenance commitments for AI modules to help users make informed decisions about which tools to trust in production.
                      • Ensure resources are available to maintain the ecosystem directory as a strategic onboarding tool for new adopters.
                      ---

                      Drupal Canvas

                      Activity this period centered on issue identification and dependency maintenance. A translation-related issue was reported involving errors when attempting to translate content using the TMGMT module. The issue appears when requesting translation jobs and results in a system failure. The problem has been identified and assigned for investigation.

                      On the maintenance front, a dependency update was opened to bring accessibility testing tools up to date. This type of routine update helps ensure the module continues to work reliably with current versions of its supporting libraries.

                      A larger draft merge request remains in progress, representing ongoing work to consolidate code into the Canvas repository. This is a significant effort involving over 6,800 lines of changes.

                      How can I help on this project?

                      • Consider prioritizing translation functionality testing, particularly for organizations using multilingual content workflows, to prevent similar issues from affecting production environments.
                      • Ensure adequate resourcing is available to complete the repository consolidation work, which represents a substantial structural change to the project.

                      Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)

                      ---

                      Context Control Center (CCC)

                      The project made progress toward its beta 3 release, targeted for 6 July 2026. A new context listing page received user experience improvements: the use cases and scope columns were merged into a single column with ordered pills, and the filter system was replaced with a cascading two-dropdown design that makes it easier to find context items by scope. A warning now appears when editing a published sub-context whose parent context is unpublished, helping authors avoid configuration errors. Code quality checks were addressed, resolving display issues in the version control interface.

                      Preparatory work for beta 3 is underway: quality assurance planning, codebase security and performance reviews, and release coordination are in progress. The project is also recruiting community testers and updating onboarding materials with session videos, documentation links, and instructions for providing feedback. Integration work continues to allow context injection into rich text editor AI tools, though this depends on changes in a related module.

                      Three issues were closed during the period: Fix eslint errors in GitLab UI even when pipeline is green, Add warning on subcontext edit form if parent is unpublished, and UX improvements on new context listing page.

                      How can I help on this project?

                      Support community testing recruitment by promoting the beta program through your networks or allocating time for staff participation. Ensure the team has dedicated time in the week leading up to 6 July for quality assurance and release tasks. Consider prioritizing resourcing decisions that affect post-beta 3 planning.

                      Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1] ======================================================================== ## [12] factcheck:tldr:executive ======================================================================== Layer-1 corrections: 0 Judge flags: 1 ======================================================================== ## [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? When you describe progress on a capability, add inline citations using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations at the end of the relevant sentence, before the closing punctuation. Output an HTML fragment using exactly this structure:

                      2026 Capabilities Progress

                      1. 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 --- REFERENCE LIST --- [1] Config action to verify if any vector database is there and it is setup (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586517 [2] Issue #3586517: Check if any Vdb provider is setup (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1660 [3] Drupal AI UX meeting 22 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584834 [4] Drupal AI UX meeting 15 June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3584833 [5] WSOD AssertionError: assert(!$data instanceof ComponentInputsMapping) in assert() when requesting tmgmt translation job (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591734 [6] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [7] Draft: #3492065 move to canvas repo (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/709 [8] Fix eslint errors in GitLab UI even when pipeline is green (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3576093 [9] CCC beta3 QA (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586296 [10] Create CCC beta3 release (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586295 [11] CCC beta3 codebase review (pre-release) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586294 [12] Test AI Best Practices skills on AI Context codebase (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586258 [13] [Discuss] Moderation status of subcontext vs parent context items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586264 [14] Add warning on subcontext edit form if parent is unpublished (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586297 [15] Inject context into ai_ckeditor requests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3581955 [16] CCC beta / pre-rc1 community testing (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586234 [17] Align context item full view with bundle-less entity (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586261 [18] Add CCC beta tester info to the project page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586248 [19] UX improvements on new context listing page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586274 [20] Gather CCC contribution stats for code and non-code contributions for release notes (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586222 [21] Issue #3576093: Fix lint errors in GitLab UI even when pipeline is green. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/197 [22] Issue #3581955: Add EventSubscriber to inject context into ai_ckeditor tools. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/116 [23] Issue #3586297: Add warning on subcontext edit form if parent is unpublished. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/196 [24] Issue #3586261: Align context item full view with bundle-less entity. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/198 [25] Issue #3586274: Merge Use cases/Scope columns and add cascading scope filter (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/184 --- TODAY'S MODULE SUMMARIES ---

                        AI (Artificial Intelligence)

                        The project saw continued development activity this period. Work is underway to improve configuration validation capabilities. Specifically, a new configuration action is being developed to verify that at least one vector database provider is installed and properly configured in the system, without requiring administrators to know which specific provider is present. This addresses a practical need: when setting up search functionality, the system currently cannot automatically detect whether any suitable database backend is ready, forcing users to manually verify setup details. The enhancement will streamline deployment and reduce configuration errors by allowing automated checks to confirm the environment is ready.

                        An associated merge request containing this functionality remains open for review. No code was merged during this period, reflecting ongoing development work typical for this stage of the module.

                        How can I help on this project?

                        • Ensure the team has access to code reviewers who can evaluate and merge open contributions in a timely manner.
                        • Clarify strategic priorities for upcoming releases to help contributors focus effort on the highest-value features.

                        Contributors: Artem Dmitriiev (a.dmitriiev)

                        ---

                        Drupal AI Initiative

                        The Drupal AI Initiative held two user experience meetings during the period, focusing on interface design and ecosystem organization. The June 22 meeting reviewed progress on AI-assisted canvas building, where the interface now locks during generation to prevent editing conflicts and provides visual feedback through placeholder boxes and progress indicators. Quality and cost tradeoffs are being surfaced through a simplified model selection interface.

                        The June 15 meeting discussed a new searchable directory of AI modules and recipes designed to help site builders discover and evaluate tools. The directory will distinguish between initiative-maintained components and community contributions, with tiered support indicators to help users assess maturity and backing.

                        Both meetings signal ongoing work to make AI capabilities more discoverable and usable for non-technical site builders, which supports broader adoption of the initiative's deliverables.

                        How can I help on this project?

                        • Champion clarity on support tiers and maintenance commitments for AI modules to help users make informed decisions about which tools to trust in production.
                        • Ensure resources are available to maintain the ecosystem directory as a strategic onboarding tool for new adopters.
                        ---

                        Drupal Canvas

                        Activity this period centered on issue identification and dependency maintenance. A translation-related issue was reported involving errors when attempting to translate content using the TMGMT module. The issue appears when requesting translation jobs and results in a system failure. The problem has been identified and assigned for investigation.

                        On the maintenance front, a dependency update was opened to bring accessibility testing tools up to date. This type of routine update helps ensure the module continues to work reliably with current versions of its supporting libraries.

                        A larger draft merge request remains in progress, representing ongoing work to consolidate code into the Canvas repository. This is a significant effort involving over 6,800 lines of changes.

                        How can I help on this project?

                        • Consider prioritizing translation functionality testing, particularly for organizations using multilingual content workflows, to prevent similar issues from affecting production environments.
                        • Ensure adequate resourcing is available to complete the repository consolidation work, which represents a substantial structural change to the project.

                        Contributors: **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Ben Mullins (bnjmnm)

                        ---

                        Context Control Center (CCC)

                        The project made progress toward its beta 3 release, targeted for 6 July 2026. A new context listing page received user experience improvements: the use cases and scope columns were merged into a single column with ordered pills, and the filter system was replaced with a cascading two-dropdown design that makes it easier to find context items by scope. A warning now appears when editing a published sub-context whose parent context is unpublished, helping authors avoid configuration errors. Code quality checks were addressed, resolving display issues in the version control interface.

                        Preparatory work for beta 3 is underway: quality assurance planning, codebase security and performance reviews, and release coordination are in progress. The project is also recruiting community testers and updating onboarding materials with session videos, documentation links, and instructions for providing feedback. Integration work continues to allow context injection into rich text editor AI tools, though this depends on changes in a related module.

                        Three issues were closed during the period: Fix eslint errors in GitLab UI even when pipeline is green, Add warning on subcontext edit form if parent is unpublished, and UX improvements on new context listing page.

                        How can I help on this project?

                        Support community testing recruitment by promoting the beta program through your networks or allocating time for staff participation. Ensure the team has dedicated time in the week leading up to 6 July for quality assurance and release tasks. Consider prioritizing resourcing decisions that affect post-beta 3 planning.

                        Contributors: Jesse Hofmann-Smith (jessehs), Kristen Pol (kepol) [2], Matt Glaman (mglaman) [1] ======================================================================== ## [14] factcheck:capabilities:executive ======================================================================== Layer-1 corrections: 1 Judge flags: 0