Daily Digest

Daily Digest – 11 June 2026

2026 Capabilities Progress

  1. Page generation — Active progress on AI-powered page building capabilities, with client-side orchestration infrastructure for Canvas AI now in development [94][117] and fixes merged to prevent AI prompts from being reset when page metadata changes [95]. Next milestone is completing the orchestration loop to enable iterative page generation.
  2. Context management — Significant progress across multiple fronts: redesigned context listing page with improved status indicators and scope presentation is under review [139][149], testing confirmed cost-effective AI models work for production use cases [138], and the team is preparing beta3 release with security documentation and example context items [121][125][130]. Next milestone is completing beta tester recruitment and onboarding materials to validate the system with real users.
  3. Background agents — Planning and architecture work underway with discussion on canonical agent definitions [13] and ongoing effort to integrate AI Agents architecture into the core AI module [14]. An audio transcription recipe demonstrating scheduled AI processing was proposed [45]. ECA integration advanced with draft implementations for automated summarization and text classification [46][47][48][49]. Next milestone is finalizing the agent architecture framework.
  4. Design system integration — Canvas made substantial progress with merged improvements to component workflows including translation labels in auditing UI [103], multilingual search indexing tests [76][100], and JSON formatting preservation in component properties [77][102]. Infrastructure for full-screen Canvas extensions was added to support expanded design workflows [84][105]. Next milestone is completing AI-powered component proposal capabilities currently in development.
  5. Content creation and discovery — Multiple improvements delivered: interactive refinement capability for field widgets is in active development to allow iterative improvement of AI-generated content [1][23][161], rich-text image description support was added to AI Automators [19][28][37], and AI Search Media Library tool integration is progressing [82]. Documentation for field widget actions and automators was updated and merged [20][32]. A critical bug affecting HTML formatting in translations was identified and requires resolution [162]. Next milestone is completing the interactive refinement feature and resolving the translation formatting issue.
  6. Advanced governance — Progress on guardrails and content control infrastructure: sensitive content streaming guardrail with mid-stream buffering was developed [4], configurable moderation guardrails were added [5][9], and conditional global guardrail scoping by provider/model/tags is underway [12]. Canvas advanced conflict detection for multi-user editing scenarios with merged improvements to entity normalization [104][107]. Moderation workflow bug fixes were prepared for AI Search [158][159][160]. Next milestone is completing the guardrail migration and conditional scoping work.
  7. Intelligent website improvements — Limited direct progress today, though foundational work continues on performance monitoring (Chicago demo cost optimization validated cheaper models [138]) and the Tool API advanced pre/post-execute events that will enable result tracking [66]. The RestrictToTopic guardrail added semantic topic matching to support more sophisticated content boundaries [18][29]. Next milestone requires dedicated focus on learning and feedback loop infrastructure.
  8. Multi-channel campaigns — No direct progress today. The capability depends on context management and agent infrastructure that are advancing [139][149][13][14], but no campaign-specific features were developed during this period.

Shipped

  1. AI module documentation updates — Developer guidance for Field Widget Actions and AI Automators was completed and merged, making it easier to extend the platform [20][32][33][34][35][36].
  2. AI Integration ECA action development — Draft implementations for automated summarization and text classification workflows were submitted for review [48][49].
  3. Milvus VDB Provider quality improvements — Test coverage was expanded and search filtering bugs affecting multi-value queries were resolved [52][53][54][55][56].
  4. AI Agents releases — Versions 1.3.0 and 1.2.4 were released, delivering continued stability updates to users [58].
  5. Canvas multilingual and editor fixes — Eleven improvements were merged including translation test coverage, language selector fixes, and server-side rendering compatibility [95][96][97][98][100][101][102][103][104][105][106][107][108][109][110][111][112][113][114][115][116].

Ongoing

  1. AI module interactive refinement capability — Field widget enhancement allowing iterative improvement of AI-generated content before acceptance remains under review [1][23].
  2. Canvas translation data loss fix — Critical issue causing published pages to lose non-default language translations when saved through auto-save API is under active development [75][97].
  3. Context Control Center beta3 preparation — Team is finalizing context listing redesign, bundleless entity migration, and beta tester recruitment materials ahead of release candidate [118][119][149][150].
  4. AI translate HTML formatting bug — Corruption of rich-text formatting during translation affecting content quality for multilingual sites awaits resolution [162].
  5. Tool API compatibility and flexibility enhancements — Merge request addressing AI module integration issue and work on pre/post-execute events are progressing [65][66][68].

AI (Artificial Intelligence)

The AI module team focused on consolidating core capabilities and improving documentation during this period. Key progress includes updated guidance for developers building AI automators and fixes to ensure tests run reliably across different environments.

Several documentation updates for the Field Widget Actions and AI Automators components were completed and merged by Artem Dmitriiev and Avinash jha (avinash.jha), making it easier for developers to extend the module. A test fix by Artem Dmitriiev addressing interactive editor behavior was also merged into the development branch, improving test stability.

Development work is underway on several user-facing enhancements. Ahmad Khader and Ahmad Khalil (ahmad-khalil-imagex) are working on interactive refinement for field widgets, which will allow content editors to iteratively improve AI-generated text before accepting it. Joshua Fernandes (joshua1234511) is implementing better media rendering in the chatbot to keep images and videos properly displayed within the chat window. Levente Besenyei (LeventeB) is adding image description support to automators, enabling the system to understand visual content embedded in rich text.

Two new issues were reported: a missing submit button in configuration and a menu placement issue affecting sites that updated to version 1.4.2.

How can I help on this project?

Prioritize testing and feedback on the interactive refinement and chatbot media improvements currently in development. Help assess the ecosystem documentation proposal by Rob Loach (robloach), which could significantly improve adoption but requires stakeholder alignment on scope.

View project on GitLab: ai

Drupal AI Initiative

The AI Initiative focused on project coordination and completing administrative tasks during this period. Three template issues for partner management were closed, streamlining the process for onboarding and auditing AI partners who support the initiative. The LocalAI Provider feature and the Chicago Driesnote demo running on DrupalForge were both marked complete, delivering new provider capabilities and making the flagship demo accessible to stakeholders without technical setup requirements.

Two new items were opened for future work. A research task on abstraction layer for model fine-tuning will explore whether the platform should offer a unified interface for training custom AI models across different vendors. A recipe for audio transcription was proposed to automatically transcribe and summarize audio content, demonstrating practical AI applications for content teams.

The team also documented outcomes from their June 1 UX meeting, where they discussed performance challenges and solutions for the content creation canvas feature.

How can I help on this project?

  • Prioritize whether fine-tuning should be standardized across AI providers or handled individually, enabling the team to proceed with implementation planning.
  • Advocate for additional AI partnerships to broaden vendor support and reduce platform dependency risks.

View project on GitLab: ai_initiative

AI Integration - ECA

The AI Integration - ECA module is progressing toward its 1.0.0 release by expanding the range of AI operations that can be automated through workflow tools. Over the past 24 hours, development work continued on two new capabilities that will allow users to build automated workflows for content analysis tasks.

Two draft implementations are under review: Add ECA execute action for Summarization and Add ECA execute action for Text Classification. These will enable users to automatically generate summaries of content and categorize text without manual intervention—useful for content management, customer support, and knowledge management workflows. Joshua Fernandes (joshua1234511) has submitted implementations for both features, which are awaiting review. Ahmad Khader (Ahmad-Khader) has been assigned to the summarization work.

Both items are tagged as part of the roadmap to version 1.0.0, indicating they are priorities for reaching a stable release suitable for production use.

How can I help on this project?

  • Ensure reviewers have time allocated to assess the two pending implementations so they can be finalized or iterated on quickly.
  • Confirm whether additional testing or documentation resources are needed before the 1.0.0 release milestone.

View project on GitLab: ai_integration_eca

Anthropic Provider

The Anthropic Provider module saw progress on a significant feature enhancement during the reporting period. A new merge request for prompt caching and expanded document support was opened by Carlos Ospina (camoa), representing the second phase of work to modernize how the module integrates with Anthropic's services.

This update will deliver two key capabilities for users. First, administrators will gain the ability to enable prompt caching through a simple interface setting, allowing the system to reuse conversation context more efficiently and reduce costs. Second, the module will support PDF documents as inputs, expanding the types of content users can work with beyond plain text. These features build on earlier infrastructure improvements and are being prepared for the next release version.

The work is currently under review, with no code merged yet during this period. This is normal development activity for a module at this maturity level.

How can I help on this project?

  • Ensure there are sufficient reviewer resources available to evaluate the pending merge request and move it toward completion.
  • If this feature aligns with organizational priorities, communicate the business value to accelerate testing and adoption planning.

View project on GitLab: ai_provider_anthropic

amazee.ai Private AI Provider

A user has reported inconsistent behavior across development environments where different AI models are available depending on when the installation was created. The issue, titled Different models available based on installation date?, was opened by Michael Anello (ultimike) and remains unresolved. Two environments running identical software versions are seeing different sets of models, with newer installations having access to a different selection than older ones.

This raises questions about how model availability is determined and whether there is an upgrade path for existing installations to access newer models. The issue could affect organizations planning their AI feature rollout, as they may not have consistent capabilities across their sites. No work has been started on this issue yet, and it is currently unassigned.

How can I help on this project?

  • Assign developer resources to investigate and document the model availability logic so teams can plan deployments with confidence.
  • Clarify the project's policy on model lifecycle and backwards compatibility to help users understand what to expect as new models become available.

View project on GitLab: ai_provider_amazeeio

Milvus VDB Provider

The Milvus VDB Provider project saw significant progress over the past 24 hours, with the team delivering improvements to both quality and functionality.

Scott Euser (scotteuser) merged substantial test coverage additions to the module, bringing new functional and unit tests that will help ensure reliability as the project evolves. This quality investment strengthens confidence in the module's behaviour and makes future changes safer to implement.

The team also resolved filtering issues where certain query types were not producing correct results. Scott Euser merged fixes addressing Filter syntax for IN/NOT IN not always correct, ensuring that searches across multiple values now work as users expect. These corrections were applied across supported versions of the module.

Shiraz Dindar (Shiraz) opened Resolve #3568651 "Batch inserts beta4", which updates earlier work on inserting multiple records efficiently to align with recent changes. This ensures performance optimisation work can move forward without conflicting with the filter improvements just delivered.

How can I help on this project?

  • Review and approve the pending batch insert work to unlock performance improvements for users handling large data volumes.
  • Ensure the team has dedicated time for continued test expansion to support a stable production release.

View project on GitLab: ai_vdb_provider_milvus

AI Agents

Over the past 24 hours, activity on the AI Agents project focused on release preparation and incremental improvements to quality and functionality.

Two new versions were released: 1.3.0 and 1.2.4, marking continued delivery of stable updates to users. This progress demonstrates ongoing maintenance and feature advancement for the module.

Several quality improvements are moving forward. A spelling error in help text has been identified and marked ready for final review through Spelling fix: "You will have to provider a JSON schema of the output wanted." This ensures clearer guidance for users configuring agents. Automated compatibility work for Drupal 12 has begun via Automated Drupal 12 compatibility fixes for ai_agents 1.4.x-dev, positioning the module for future platform updates.

Two feature enhancements remain in development. Work continues on allowing agents to handle tool errors gracefully rather than stopping execution, which would improve reliability for multi-role deployments. Additionally, progress is being made on tracking which user or system initiated an agent, enabling better customization of agent behavior based on context.

How can I help on this project?

  • Review and approve the spelling fix currently awaiting final sign-off to improve user-facing documentation quality.
  • Provide feedback on prioritization between Drupal 12 compatibility work and new feature development to guide resource allocation.

View project on GitLab: ai_agents

Tool API

The Tool API project saw significant planning and development activity over the past 24 hours, with four issues advancing work that will improve how AI systems use Drupal-based tools.

Three issues focus on making the module more flexible and reliable for AI integrations. Marcus Johansson submitted a merge request for Add contextdefinitionoverrides to the ToolPluginBase, which resolves a compatibility issue with the AI module that was preventing proper integration. Separately, Marcus Johansson opened Add pre-execute and post-execute events to ToolBase::execute() to alter inputs and results, which will allow other modules to customize how tools behave without modifying core functionality. Work also continued on Allow controlling Tool return format, now assigned to Abhisek Mazumdar (abhisekmazumdar), which will give developers more control over how tool results are formatted for different AI systems.

Additionally, progress was made on Introduce support for Discovery, Planning and Execute calls for MCP and Agents, addressing a key limitation where AI systems become less reliable when working with large numbers of tools.

How can I help on this project?

  • Prioritize review and testing resources for the pending merge request on context definition overrides to accelerate AI module compatibility.
  • Ensure the team has adequate capacity to complete the tool return format work, as multiple AI integration patterns depend on this feature.

View project on GitLab: tool

Drupal Canvas

Canvas made significant progress on multilingual capabilities and editor reliability over the past 24 hours, with eleven improvements merged to production.

The team strengthened translation workflows by adding test coverage for multilingual search indexing (Ignacio Sánchez Holgueras) and fixing display issues in the language selector for content templates (Kunal Sachdev). The component auditing interface now correctly labels translations, making it easier to track changes across languages (Ben Mullins).

Several editor experience improvements were delivered: select menus in the sidebar now align properly (Vipin Mittal), and text fields containing JSON-formatted content now preserve their formatting (Ben Mullins). A rendering compatibility issue affecting server-side environments was resolved (Harumi Jang), and the development toolchain was updated to address dependency conflicts (Wim Leers).

The team also advanced conflict detection infrastructure to support multi-user editing scenarios (Feliksas Mazeikis).

Active work continues on critical translation issues: a bug causing published pages to lose non-default translations when saved through the editor is under review (three team members assigned), and integration with professional translation management tools is in development (Wim Leers). New AI-powered page generation capabilities and full-screen extension support are also progressing through code review.

How can I help on this project?

  • Prioritize testing and sign-off on the translation data loss fix, which affects multilingual production sites and has an open merge request awaiting review.
  • Validate whether professional translation workflow integration (TMGMT) aligns with organizational translation strategy before the feature is finalized.

View project on GitLab: canvas

Context Control Center (CCC)

The team closed Sprint 11 planning activities this period and is preparing for a beta3 release focused on stability and developer experience improvements. Several foundational refinements are underway to strengthen the module before moving to release candidate status.

Key progress includes completed work on switching context item text fields to string_long, which resolves conflicts with the markdown editor in Drupal CMS, and adding AGENTS.md to .gitignore to support developer workflows. Testing confirmed that cheaper AI models can produce acceptable results for the Chicago Driesnote demonstration, reducing per-page costs from up to $2 USD to more affordable alternatives. The team also evaluated the AI Knowledge Connector module for potential integration opportunities.

A redesigned context listing page is in active development, with a merge request delivering improved column structure, token estimation, status tags, and scope presentation. Work also continues on removing the single-bundle architecture in favor of a bundleless entity model, now that Scheduler supports this approach.

The team is actively recruiting beta testers and preparing supporting materials including video tutorials, updated project documentation, and example context items to lower the learning curve for new users. Security documentation, issue templates, and developer API boundaries are being formalized ahead of the stable release.

How can I help on this project?

View project on GitLab: ai_context

AI Dashboard

Development activity this week focused on expanding the module's ecosystem visibility and resolving administrative tasks. Work is underway on an AI ecosystem browser that would help users discover and evaluate available AI-related modules directly from their own site. Rob Loach (robloach) is developing a filterable catalog drawing from Drupal.org data, with automated updates planned via scheduled processes. This feature aims to simplify module selection and reduce the research burden on site administrators.

The team also completed testing on issue migration workflows between projects, which will streamline how work items are organized as the initiative scales.

The ecosystem browser remains in draft, with ongoing refinements to usability (readability of filters and text sizing) and the accuracy of automatic categorization. This work supports the broader goal of making AI capabilities more accessible and discoverable within the Drupal platform.

How can I help on this project?

  • Advocate for the AI Dashboard within the broader Drupal community to increase adoption and gather feedback on the ecosystem browser concept.
  • Ensure the team has design or UX support to refine the usability issues identified in the catalog interface.

View project on GitLab: ai_dashboard

Field Widget Actions

The Field Widget Actions module saw active development during this period, with work beginning on a new capability that will help users improve AI-generated content before it's finalized. Edward Zwart (ezeedub) opened a merge request to add interactive refinement capability, which introduces an optional feature allowing users to iteratively refine AI-generated suggestions through a modal interface before accepting them into a field.

This enhancement represents a meaningful step forward in user control and content quality. Rather than accepting AI output as-is, users will be able to review and request improvements in an interactive workflow. The feature is designed as opt-in, meaning it won't disrupt existing implementations while offering teams the flexibility to enable more careful content creation processes where needed.

The merge request is substantial, with approximately 1,800 lines of changes, and remains under review. No issues were updated or commits merged during this reporting period.

How can I help on this project?

  • Allocate reviewer time to evaluate the interactive refinement merge request, as its size suggests it may benefit from dedicated attention to move toward completion.
  • Clarify product priorities around AI content workflows to help guide whether this capability should be fast-tracked or refined further based on user feedback.

View project on GitLab: field_widget_actions

AI translate

The AI translate module saw four new issues opened during this period, reflecting both forward-looking strategic work and immediate quality concerns.

A significant bug was identified where HTML formatting is corrupted when translating rich-text content. This means translated pages may display broken layouts or lose important formatting like bold text, links, or lists—directly affecting content quality for multilingual sites. The issue has been accepted and is awaiting resolution.

On the strategic front, contributor Sven Decabooter (svendecabooter) opened a planning issue to explore refactoring the module's architecture to support AI agent-driven translation. This would enable more flexible, automated translation workflows and reduce code duplication across different use cases.

Two automated compatibility issues were created to prepare both active development branches for Drupal 12, ensuring the module remains compatible with the platform's evolution.

No code was merged or committed during this period; activity focused on issue identification and planning.

How can I help on this project?

  • Prioritize allocation of developer time to resolve the HTML formatting bug, which affects all users translating formatted content.
  • Clarify strategic direction on the AI agent refactoring proposal to guide architectural decisions and resource planning.

View project on GitLab: ai_translate

ElevenLabs

The ElevenLabs module saw minimal activity during this period. An automated maintenance update was submitted by the Project Update Bot (Project-Update-Bot) via a merge request addressing project fixes. This type of routine maintenance helps keep the module aligned with current Drupal standards and dependencies, reducing technical debt over time.

No issues were updated, no code was merged, and no significant development occurred during the 24-hour window. This appears to be a quiet period for the module with only automated tooling activity.

How can I help on this project?

  • Review whether the module aligns with current organizational priorities and allocate developer time accordingly if it remains strategically important.
  • Consider identifying and funding specific features or improvements that would increase adoption or deliver business value.

View project on GitLab: elevenlabs

References

[1] Add interactive refinement capability to Field Widget Actions (ai, Issue)

[4] Add SensitiveContentStream guardrail and kernel test for StreamableGuardrailInterface mid-stream buffering and evaluation (ai, Issue)

[5] Add a Moderation Guardrail plugin (configurable moderation provider/model as a guardrail) (ai, Issue)

[9] Migrate external moderation config to guardrail sets and deprecate the moderation runner (ai, Issue)

[12] Scope global guardrails by request provider id, model and/or tags (conditional global guardrail sets) (ai, Issue)

[13] [Discuss] Define the canonical agent definition (informed by other agent frameworks) (ai, Issue)

[14] [META] Move AI Agents architecture into the AI module (ai, Issue)

[18] RestrictToTopic guardrail: add semantic topic matching mode (ai, Issue)

[19] Add rich-text image description support to AI Automators (ai, Issue)

[20] Update documentation for FWA and ai_automators (ai, Issue)

[23] Issue #3586468: "Add interactive refinement capability to Field Widget Actions Automation" (ai, MR)

[28] Issue #3586478: "Add rich-text image description support to AI Automators" (ai, MR)

[29] Issue #3584977: RestrictToTopic guardrail: add semantic topic matching mode. (ai, MR)

[32] Issue #3586514: Update documentation for FWA and ai_automators (ai, MR)

[33] Issue #3586514 cherry-pick fa46b94dcf6b506c0098bb623504345c4c730fa2 (ai, MR)

[34] Issue #3586514 cherry-pick fa46b94dcf6b506c0098bb623504345c4c730fa2 (ai, MR)

[35] Issue #3586514: Update documentation for FWA and ai_automators (ai, MR)

[36] Issue #3586514: Update documentation for FWA and ai_automators (ai, MR)

[37] Issue #3586478: "Add rich-text image description support to AI Automators" (ai, MR)

[45] Create ai_recipe_audio_transcription: transcribe + summarize audio media via cron (ai_initiative, Issue)

[46] Add ECA execute action for Summarization (ai_integration_eca, Issue)

[47] Add ECA execute action for Text Classification (ai_integration_eca, Issue)

[48] Issue #3585009: Added ECA execute action for Summarization. (ai_integration_eca, MR)

[49] Issue #3585010: Added ECA execute action for Text Classification. (ai_integration_eca, MR)

[52] Resolve #3568651 "Batch inserts beta4" (ai_vdb_provider_milvus, MR)

[53] #3595971 Add test coverage (functional + unit) - 1x branch (ai_vdb_provider_milvus, MR)

[54] #3595971 Add test coverage (functional + unit) - 2x branch (ai_vdb_provider_milvus, MR)

[55] #3572792 Filter syntax for IN/NOT IN not always correct (ai_vdb_provider_milvus, MR)

[56] Fix IN and NOT IN syntax (ai_vdb_provider_milvus, MR)

[58] Release 1.3.0 and 1.2.4 (ai_agents, Issue)

[65] Add contextdefinitionoverrides to the ToolPluginBase (tool, Issue)

[66] Add pre-execute and post-execute events to ToolBase::execute() to alter inputs and results (tool, Issue)

[68] Resolve "Add contextdefinitionoverrides to the ToolPluginBase" (tool, MR)

[75] Publishing a canvas_page via auto-save API drops all non-default-language translations (canvas, Issue)

[76] Add search api tests for translated canvas Page indexing and retrieval (canvas, Issue)

[77] Allow text area to have JSON formatted string and have it remain a string (canvas, Issue)

[82] Provide the AI Search Media Library as a tool/Agent (canvas, Issue)

[84] Add "page" extension type for full-screen Canvas extensions (canvas, Issue)

[94] Canvas AI: Client-side orchestration loop for Canvas AI(POC) (canvas, Issue)

[95] Fix Canvas AI prompt reset on metadata changes (canvas, MR)

[96] Use globalThis.window to avoid window reference errors (canvas, MR)

[97] fix: #3591584 Auto-save should not re-create entities, but set the fields of them: otherwise translations get lost (canvas, MR)

[98] Resolve "Add TMGMT translation integration for content entities" (canvas, MR)

[100] Resolves #3591644: "Add search api tests for translated canvas Page indexing and retrieval" (canvas, MR)

[101] bug: #3591642 Fix LogicException on component instance updates and config... (canvas, MR)

[102] #3591661 allow JSON formatted string in textarea to remain a string (canvas, MR)

[103] #3591612 auditing UI to include translation labels (canvas, MR)

[104] feat(Conflict detection): #3589076 "Detect conflicts during auto-save polling" (canvas, MR)

[105] Add "page" extension type for full-screen Canvas extensions (canvas, MR)

[106] #3591649: "Missing delete translation confirmation modal" (canvas, MR)

[107] fix(Conflict detection): Exclude computed internal fields from Page entity normalization (canvas, MR)

[108] fix(Redux-integrated field widgets): #3591651 Misaligned select options in right side panel of canvas editor (canvas, MR)

[109] Issue #3591332: [CI] Playwright Report job skipped when Playwright test fails (canvas, MR)

[110] feat(Drush): #3585531 Add commands to list, audit, and generate Canvas components (canvas, MR)

[111] #3591654 "Update the delete link generation in ApiLayoutController.php to use canvas.api.config.translation.delete in the template context" (canvas, MR)

[112] Bump PHPStan to 2.2 + its deps. (canvas, MR)

[113] Resolve #3591583 "Agents.md" (canvas, MR)

[114] #3591645 "Missing checkmark for languages with translations for Content Templates" (canvas, MR)

[115] chore: #3588803 Upgrade to Astro 6 (canvas, MR)

[116] feat: #3581692 MaybeUrl lacks __toString(), causes fatal error when token... (canvas, MR)

[117] POC-Phase -1 (canvas, MR)

[118] Sprint 11 CCC roadmap updates, sprint planning, and issue triage (ai_context, Issue)

[119] CCC beta3 release planning (ai_context, Issue)

[121] Create SECURITY.md file for AI Context (CCC) (ai_context, Issue)

[125] Provide example context items (ai_context, Issue)

[130] Add CCC beta tester info to the project page (ai_context, Issue)

[138] Test Chicago Driesnote repo with cheaper models (ai_context, Issue)

[139] Update context listing page per new design (ai_context, Issue)

[149] Issue #3586219: Update context listing page per new design (ai_context, MR)

[150] Issue #3584775: Remove AiContextItemType and make ai_context_item bundleless (ai_context, MR)

[158] Moderation skipping should call enable and disable on the provider when available (ai_search, Issue)

[159] #3584022: Moderation skipping should call enable and disable on the provider when available [1x] (ai_search, MR)

[160] #3584022: Moderation skipping should call enable and disable on the provider when available [2x] (ai_search, MR)

[161] feat: #3547306 Add interactive refinement capability to Field Widget Actions (field_widget_actions, MR)

[162] HTML markup is corrupted/not preserved when translating formatted text fields (text_with_summary, text_long) (ai_translate, Issue)

Period: 11 June 2026 to 12 June 2026  |  Generated: 12 June 2026 05:00 GMT

To view the full AI prompts used to generate this digest check this file: 24h_2026-06-11_prompts.txt

Looking for older digests? Browse all digests here.