Daily Digest
Daily Digest – 1 May 2026
Shipped
- Drupal Canvas: PostgreSQL CI fix and PHPUnit stability — A merged fix resolves PostgreSQL test collisions and restores CI stability against PHPUnit flakiness introduced in Drupal 11.2.
- Drupal Canvas: Symmetric translation for ContentTemplate and PageRegion — The config schema type for inputs was changed to support translation of ContentTemplate and PageRegion component trees through core's Config Translation UI.
- Context Control Center: Denormalized scope index table — A 1010-line refactor replaces fragile SQL LIKE queries against serialized scope data with a dedicated index table, fixing query correctness and improving performance.
- Context Control Center: loop_aware option for SystemPromptSubscriber — A new loop_aware option prevents SystemPromptSubscriber from re-injecting full context on every agent loop iteration, fixing redundant processing in agentic workflows.
- Drupal AI Initiative: Brand and content tasks closed — The Drupal AI Brand Positioning strategy task, a blog article promoting the Drupal AI Learners Club, and the Southwark Webinar promotion were all completed and closed.
Ongoing
- AI module: Elasticsearch VDB provider — A 7,000-line merge request adding Elasticsearch as a vector database provider to the provider matrix is open and awaiting technical review for interface conformance.
- amazee.ai: VDB indexing and data-integrity bugs — A fix for the major bug preventing item indexing after an index is cleared is under review, while a critical unassigned bug where clearing one search index drops data from others remains open with no owner.
- Context Control Center: RC1 blockers in triage — Sprint 9 planning is underway with several pre-RC1 tasks now tracked, including adding AiContextSelectorInterface, cleaning up DX inconsistencies, and making selection defaults deterministic.
- AI Search: Parent query conditions via boost plugin — Parallel merge requests for the 1.x and 2.x branches implement propagation of Search API query conditions into VDB queries, addressing a filtering gap in RAG chatbot use cases.
- Drupal Canvas: HTTP API endpoint for canvasData.v0 — An open merge request from Matt Glaman adds an HTTP API endpoint for canvasData.v0 and is awaiting API design review.
AI (Artificial Intelligence)
No commits landed in the 24-hour window, leaving the project without any merged work during this period. Active development is ongoing across documentation, tooling, and submodule extensibility.
Open Merge Requests Awaiting Review
Two MRs are open and awaiting attention. Ricardo Amaro (ricardoamaro) opened #3586399: Add Elasticsearch VDB provider to matrix, a sizeable 7,000-line diff adding Elasticsearch as a vector database provider to the provider matrix. A companion issue, Add Elasticsearch VDB provider to docs/providers/matris.md, has already been closed, suggesting documentation groundwork is in place. Separately, Christoph Breidert (breidert) submitted task: #3586398 Add GitLab issue and merge request templates to standardise contributor workflows with issue and MR templates.
Other Notable Activity
Rob Loach (robloach) continues work on Add event hook to ai_ckeditor to allow context injection, a feature request now at 32 comments under active sprint focus. Nick Abbott (SirClickALot) filed Existing Automator failing to work, an unassigned regression that needs a maintainer to triage.
How can I help on this project?
- Review the Elasticsearch VDB provider MR -- the large diff needs technical scrutiny on provider interface conformance.
- Pick up the unassigned Existing Automator failing to work issue and reproduce or bisect the regression.
- Join the discussion on context injection via event hook in ai_ckeditor to help drive it to a mergeable patch.
Drupal AI Initiative
Marketing and Events Sprint
No code was merged or committed in this 24-hour window. Activity was concentrated entirely in the marketing and events workstream, running under Marketing Sprint #2: April 27 - May 11 [Meta], assigned to Jeremy Chinquist (jjchinquist).
Three issues were closed: the Drupal AI Brand Positioning strategy task was resolved, a Blog article promoting Drupal AI Learners Club was completed by Matthew Saunders (jmsaunders) and Maria Fernanda Silva (mfernanda.silva), and Paul Johnson (pdjohnson) closed out Southwark Webinar promotion.
Active work includes coordination around The AI Summit London, with booth design assigned to Paul Johnson (pdjohnson) and promotional imagery to Scott Lawrence (slawrence10). Matthew Saunders (jmsaunders) opened several planning items around a DB Schenker webinar and is building a Claude Code skill for AI Initiative issue generation for podcasts and webinars, currently in needsReview. The unassigned Give d.o editors the ability to embed YouTube videos remains open and is blocking richer content publishing.
How can I help on this project?
- Review the Claude Code skill for issue generation task, which is in needsReview and needs technical feedback.
- Pick up the unassigned YouTube embed feature request for the d.o editors.
- Assess the unassigned Add the AI Summary tool to the Drupal Starforge front page and propose an implementation approach.
amazee.ai Private AI Provider
Active Work
No commits landed in the 24-hour window, but two merge requests are open and awaiting review. Dan Lemon (dan2k3k4) has raised chore(#3578014): fix vdb indexing items after index was cleared (165 diff lines) to address the major bug tracked in VDB: Unable to index items after index was cleared, which is also flagged for backport to 1.2.x. Separately, Dezső Biczó (mxr576) opened the smaller Do not override methods from parent unnecessarily (28 diff lines), targeting VdbProvider and PostgresProvider to remove redundant method overrides.
A critical unassigned bug remains open: VDB: Clearing all indexed data of search index A drops indexed data of others, also needing a 1.2.x backport. Two further unassigned issues are active -- Deleting an entity does not delete indexed data and VDB: Contextual fields does not deserve a database column -- suggesting the VDB layer still has meaningful data-integrity gaps.
How can I help on this project?
- Review and test the indexing fix MR and the method override cleanup MR to help get them merged.
- Pick up the critical unassigned cross-index data loss bug or investigate the entity deletion issue, both of which have no current owner.
Unstructured
Recent Activity
Activity over the past 24 hours consists of a single open merge request from Harsh Behl (pen). Issue-number 3571499: Adding Raw json option in text. Also added new json formatter. introduces a raw JSON output option for text fields alongside a new JSON field formatter. The MR spans 233 diff lines on branch 3571499-add-option-to and remains open pending review. No commits landed and no issues were updated during this period.
No API breakage has been reported, but the new formatter will need review for integration consistency with the existing field formatter architecture and any configuration schema requirements.
How can I help on this project?
- Review the open JSON formatter MR -- check formatter plugin structure, configuration schema, and whether a
settingsSummary()implementation is included. - Write a kernel or functional test covering the new raw JSON formatter output to help move the MR toward merge.
Drupal Canvas
Merged This Period
Two merge requests landed in the 24-hour window. Sally Young (justafish) merged Issue #3529128: Add fix for PostgresSQL collisions, fix CI caching, restore fix for 11.2 phpunit flakiness, resolving PostgreSQL test collisions and stabilising the CI pipeline against PHPUnit flakiness introduced in Drupal 11.2. Wim Leers (wimleers) merged #3582478: Support symmetric translation of ContentTemplate & PageRegion component trees, which changes the config schema type for inputs to support translation of ContentTemplate and PageRegion components through core's Config Translation UI -- a meaningful API-level change for anyone building translatable Canvas layouts.
Open Work
Dave Long (longwave) has several open MRs targeting API and tooling quality: Add validation for examples., Fix warnings., and Validate image example URLs in code components. sit alongside a push to un-ignore OpenAPI definitions. Matt Glaman (mglaman) is adding an HTTP API endpoint for canvasData.v0. Lauri Timmanee (lauriii) has opened MRs to emulate reduced motion in the Canvas preview iframe and stabilise the preview for in-place vh updates and tall content. Larger draft work includes Ted Bowman (tedbow) on symmetric content inputs (15k diff lines) and Ben Mullins (bnjmnm) on a post-multivalue reroll.
How can I help on this project?
Review Resolve #3585327 "Add HTTP API endpoint for canvasData.v0" -- it is a focused 346-line MR that would benefit from API design feedback. You could also test or add coverage for the example validation MR, or investigate whether the state managed wasm file loading MR has unresolved blockers keeping it open.
Context Control Center (CCC)
Merged This Period
Two significant merge requests landed on 2026-05-01. Abhisek Mazumdar (abhisekmazumdar) merged feat: #3574905 Add denormalized scope index table for SQL-based scope pre-filtering, a 1010-line change that closes the long-standing CCC: Refactor to denormalize scope values and replace SQL LIKE on serialized scope blocker. The refactor replaces fragile LIKE queries against serialized scope data with a dedicated index table, directly addressing query correctness and performance at the storage layer. Alex Urevick-Ackelsberg (alexua) merged Issue #3582288: Add loop_aware option to skip context re-injection on agent loops, resolving SystemPromptSubscriber re-injects full context on every agent loop iteration. The fix introduces a loop_aware option so SystemPromptSubscriber skips redundant context injection on subsequent agent loop iterations.
Sprint Transition and RC1 Planning
Sprint 8 and the CCC beta2 release planning issue closed, and Kristen Pol (kepol) opened Sprint 9 CCC roadmap updates, sprint planning, and issue triage alongside CCC beta3 release planning. Key pre-RC1 tasks now tracked include Add AiContextSelectorInterface before RC1, Clean up CCC inconsistencies and DX issues before rc1 (flagged as a stable blocker), and Make selection defaults deterministic and safe before RC1. A naming consistency task, Normalize token/item limit naming -- eliminate tokenBudget and align on maxTokens/maxItems, is also in flight under kepol.
Bugs and Blockers
Review and update CCC permissions remains open and flagged as a stable blocker. A new major-priority bug, Improve context selection cacheability and request-level scope performance, was filed, as was the straightforward ai_context overview CSS references missing external.svg asset via bad relative path. The Move scheduler feature to submodule or progressive enhancement issue, assigned to Matt Glaman (mglaman), remains open and blocker-tagged. Several unassigned test cleanup tasks were also filed, covering language scope form field rendering, taxonomy kernel tests, and subscription update logic.
How can I help on this project?
- Pick up one of the unassigned test TODO tasks -- Address todos in CCC language scope form field rendering tests or Address todos in CCC empty scope / subscription handling tests -- both are sprint candidates with no owner.
- Review the open stable blocker Review and update CCC permissions and post findings or a patch.
- Fix the one-liner bad relative path for external.svg as a low-risk first contribution.
AI Search
Merge Requests and Active Development
No commits landed in the 24-hour window, but meaningful development is in progress. Scott Euser (scotteuser) opened two parallel merge requests targeting both supported branches: 2.x branch: Passing parent query conditions via boost plugin to the vdb query and 1.x branch: Passing parent query conditions via boost plugin to the vdb query. Both carry 347 diff lines and implement the feature tracked in Allow passing parent query conditions via boost plugin to the vector database query conditions, which enables query conditions from the parent Search API query to propagate through the boost plugin into VDB queries -- addressing a real gap when filtering results in RAG chatbot use cases.
A related bug, Boost Database by AI Search: No results even when AI Search finds something, remains open and is currently marked as postponed. Documentation work for the amazee.ai VectorDB provider is accepted but unassigned per Add info about amazee.ai VectorDB provider.
How can I help on this project?
- Review the open MRs (2.x and 1.x) for condition-passing logic correctness and edge cases.
- Pick up the unassigned amazee.ai VectorDB provider documentation task.
- Investigate the postponed boost database no-results bug to determine whether the new condition-passing MR resolves it.
Shipped
- Drupal AI Brand Positioning Completed — The Drupal AI Initiative finalized its brand positioning strategy, published a blog article promoting the AI Learners Club, and promoted an upcoming webinar, marking tangible progress in public awareness of Drupal's AI capabilities.
- Context Control Center Performance and Reliability Improvements — Two significant fixes were delivered: one preventing AI agents from receiving redundant information during multi-step tasks, and another making context lookup faster and more reliable at scale, both advancing the module toward a stable release.
- Drupal Canvas Translation and Compatibility Fixes — A fix improving database compatibility and testing reliability was merged, alongside an advancement in multilingual content support, giving editors a more consistent experience when managing content in multiple languages.
Ongoing
- amazee.ai Critical Data Loss Bug Under Investigation — A critical bug where clearing one search index accidentally wipes data from other indexes is being actively worked on, but fixes have not yet been reviewed or merged, posing a risk to AI search quality for current users.
- Context Control Center Release Candidate in Preparation — The team is now planning toward a first release candidate, with administrator interface improvements, a major selection reliability bug, and several enterprise-readiness items still to be resolved before launch.
- AI Summit London Presence in Progress — Booth design and promotional materials are being prepared for a high-profile industry event, with speaker logistics for a separate DB Schenker webinar also still being coordinated.
- AI Search Filtering Accuracy Work Awaiting Review — New code to ensure AI-powered search respects the same filtering rules as the rest of a site has been submitted but not yet merged, while a related bug that causes the AI to find results that never reach the user remains postponed.
- AI Module Automation Feature Broken — An existing automation capability within the AI module has stopped working, and the issue remains open, representing a risk of disruption for any teams currently relying on it.
AI (Artificial Intelligence)
Activity Summary
The past 24 hours saw focused contributor activity across documentation, tooling, and feature development for the AI module. While no changes were merged into the codebase during this period, several meaningful efforts are in progress.
Ricardo Amaro (ricardoamaro) moved quickly to document Elasticsearch as a supported vector database provider, closing one tracking issue and opening a merge request to formalise its inclusion in the provider compatibility matrix. This expands the module's officially recognised integration options, giving organisations more flexibility in choosing infrastructure that fits their needs.
Christoph Breidert (breidert) proposed standardised templates for reporting issues and submitting contributions, which would make it easier for new contributors to engage with the project consistently. This kind of governance improvement helps the project scale its community involvement.
On the feature side, Rob Loach (robloach) continues work on adding an event hook to the AI-powered content editor tool to allow richer contextual input, a capability that could meaningfully improve AI-assisted content authoring. A separate report flags that an existing automation feature has stopped working, which warrants prompt attention to avoid disruption for current users.
How can I help on this project?
Consider advocating for dedicated review time so open merge requests do not stall before merging. If automation features are in active use within your organisation, prioritise resourcing a fix for the Existing Automator failing to work issue. Encouraging participation in the AI Initiative Sprint can also accelerate feature delivery.
Drupal AI Initiative
Marketing and Events Momentum
The past 24 hours reflect a project in active outreach and brand-building mode. The team closed out three meaningful deliverables: a completed Drupal AI Brand Positioning strategy, a published blog article promoting the Drupal AI Learners Club, and promotion of the Southwark Webinar. These represent tangible steps toward growing public awareness of Drupal's AI capabilities.
Looking ahead, the team is ramping up activity around two events. Preparations for The AI Summit London are well underway, with booth design being handled by Paul Johnson (pdjohnson) and promotional imagery progressing under Scott Lawrence (slawrence10). Separately, planning is in motion for a DB Schenker webinar, with Matthew Saunders (jmsaunders) coordinating speaker commitments and logistics.
On the content side, Rosie Gladden (rgladden) is actively pursuing real-world case studies and aligning on a video opportunity tied to DrupalCon EU. A proposal to feature the AI Summary tool on the main Drupal Starforge website, raised by Nick Opris (unqunq), is also open for consideration and currently unassigned.
How can I help on this project?
Leaders can support progress by helping secure speaker commitments from partner organisations such as DB Schenker, championing the collection of internal AI success stories that could become case studies, and endorsing increased resourcing for event presence at high-profile venues like The AI Summit London.
amazee.ai Private AI Provider
Bug Fixes and Data Integrity in Focus
Activity over the past 24 hours has been dominated by a cluster of data integrity issues affecting the module's vector database (VDB) search and indexing capabilities. These are the features that allow the AI to search and retrieve content intelligently, so the bugs being addressed have direct implications for how reliably the system serves end users.
The most pressing concern is a critical bug where clearing one search index accidentally wipes indexed data from other indexes. This kind of data loss could silently degrade AI search quality across the board. Alongside this, two further bugs flagged as major or normal priority address failures to re-index content after an index is cleared and deleted content not being removed from the search index, which could result in the AI surfacing outdated or irrelevant information.
Dan Lemon (dan2k3k4) has active fixes in progress for two of these issues, and Dezső Biczó (mxr576) has submitted a code quality improvement. No changes have been merged yet, meaning these fixes are still awaiting review and sign-off.
How can I help on this project?
Given the critical and major bugs currently open, leaders can help by ensuring sufficient reviewer capacity is available to approve and merge fixes promptly, preventing delays that could affect users. It is also worth confirming that the team has clear ownership and prioritisation for unassigned issues. If this module underpins a customer-facing AI capability, escalating urgency to relevant stakeholders may be warranted.
Unstructured
Development Activity
Activity over the past 24 hours has been modest but focused. A single contribution from Harsh Behl (pen) introduces a meaningful capability improvement: the ability to handle and display raw structured data in a more flexible way. The work, captured in Adding Raw json option in text. Also added new json formatter., would give content editors and integrators more control over how data coming from the Unstructured service is presented within a Drupal site. This kind of enhancement supports teams that need to surface complex data outputs without heavy customisation work.
No other changes were merged or committed during this period. The contribution is still open and awaiting review, meaning the improvement is not yet live for users. Progress is incremental, and the project would benefit from consistent attention to move contributions through to completion.
How can I help on this project?
Consider ensuring dedicated review time is allocated so open contributions do not stall. If the project depends on external partnerships or data workflows, aligning stakeholders around priority features can accelerate decisions. Advocating for sustained contributor resourcing, even part-time, would help maintain momentum.
Drupal Canvas
A Busy 24 Hours of Forward Momentum
The Drupal Canvas project saw strong activity over the past day, with two notable pieces of work successfully delivered and a wide range of improvements moving through review.
On the delivery side, a fix improving database compatibility and testing reliability was completed by Sally Young (justafish), strengthening the project's ability to run consistently across different environments. Separately, Wim Leers (wimleers) landed an important advancement in content translation support, meaning editors will have a more consistent experience when managing multilingual content within Canvas-built pages.
In parallel, the team is advancing several significant capabilities. Work is underway on improving accessibility for users who prefer reduced motion, and stability improvements to the live content preview are in progress. A large body of work by Ted Bowman (tedbow) and Ben Mullins (bnjmnm) is tackling how content inputs are structured, which will directly improve the editing experience. Dave Long (longwave) is contributing across several fronts, including data validation and infrastructure quality improvements.
Overall, the project is progressing steadily across both user-facing features and foundational reliability.
How can I help on this project?
Leaders can support this project by ensuring the team has sufficient dedicated time to move large in-progress pieces of work, such as the content input improvements, across the finish line. Sponsoring additional review capacity or testing resources would reduce bottlenecks. Advocating for prioritisation of accessibility features, such as the reduced-motion work, reinforces organisational commitments to inclusive design.
Context Control Center (CCC)
Momentum Toward a Stable Release
The past 24 hours represent one of the most active periods yet for the Context Control Center, with the team closing out a significant wave of foundational work and immediately pivoting to plan the road ahead. Two major improvements landed in the product: a fix for a performance problem where AI agents were receiving the same context information repeatedly during multi-step tasks (resolved via Issue #3582288: Add loop_aware option to skip context re-injection on agent loops), and a substantial overhaul to how the system looks up and filters context, making it faster and more reliable at scale (feat: #3574905 Add denormalized scope index table for SQL-based scope pre-filtering). Both were contributed by Alex Urevick-Ackelsberg (alexua) and Abhisek Mazumdar (abhisekmazumdar) respectively.
With the CCC beta2 release planning wrapped up, Kristen Pol (kepol) has already opened Sprint 9 CCC roadmap updates, sprint planning, and issue triage and is driving toward a first release candidate. Key priorities now include improving the administrator interface (with Aidan Foster (aidanfoster) leading design work on the Design Improved Context Items List View and Design for the Context Item single entity view), fixing a selection reliability issue flagged as a major bug before release, and addressing several consistency and permissions items needed to meet a stable, enterprise-ready standard. Community members Michael Anello (ultimike) and scott falconer (scottfalconer) also surfaced useful real-world feedback and a new feature proposal during the period.
A broad set of longer-horizon capabilities -- including governance controls, richer content source ingestion, and AI-powered context ranking -- have been formally scoped and documented for future sprints, signalling a well-organised roadmap beyond the immediate release.
How can I help on this project?
Leaders can make an immediate difference by ensuring the team has adequate capacity to complete quality assurance and UX review ahead of the release candidate. Sponsoring or facilitating community contributor time -- particularly for the several unassigned items in the sprint backlog -- would accelerate delivery. Amplifying awareness of the project within your organisation or partner network can also attract testers and early adopters whose feedback will shape the 1.0 release.
AI Search
Summary
Activity over the past 24 hours on the AI Search module has centred on improving the accuracy and reliability of AI-powered search results, with a mix of feature development, bug investigation, and documentation work.
The most significant contribution comes from Scott Euser (scotteuser), who has opened both an issue and two corresponding code submissions addressing a gap in how search filters are passed through when AI Search is used to boost standard database search results. This work, captured in Allow passing parent query conditions via boost plugin to the vector database query conditions and the associated merge requests, aims to make AI-assisted search respect the same filtering rules as the rest of the site -- an important step toward trustworthy, consistent results for end users.
A related bug, Boost Database by AI Search: No results even when AI Search finds something, highlights a situation where the AI finds relevant content but nothing is shown to the user. This issue is currently postponed, representing a known risk to user experience. There is also outstanding demand for clearer guidance on filtering within RAG chatbot scenarios and for documentation covering an additional provider option.
How can I help on this project?
Leaders can support progress by prioritising a review of the postponed bug, which directly affects user-facing search results. Encouraging internal teams or partners to test and validate the new filtering work would help move it toward release. Funding dedicated documentation effort would also accelerate adoption and reduce support burden.