Daily Digest
Daily Digest – 14 June 2026
2026 Capabilities Progress
- Page generation — Progress on content reference selection UI [19] and improved schema editing [2][4][8][9] will make it easier to define how AI should structure generated pages, but no direct work on end-to-end page generation occurred today.
- Context management — A critical fix is under review to allow modules to extend scope values through customization hooks [23][24], which will enable downstream features like custom audience profiles and governance rules.
- Background agents — Improvements to structured output configuration for chat actions [6][7] and AI agent schema editing [8][9] will make it easier to configure agents that work autonomously, though no direct progress on triggers or scheduling occurred today.
- Design system integration — No direct progress today.
- Content creation and discovery — Testing infrastructure was enhanced with summarization support [1][3], which will improve content summarization capabilities once deployed, and schema editing improvements [2][4][8][9] will make content structuring more reliable.
- Advanced governance — Translation workflow improvements [10][16][20] and multilingual content integrity fixes [20] support governance requirements for content approval processes, though no direct work on batch approvals or versioning occurred.
- Intelligent website improvements — No direct progress today.
- Multi-channel campaigns — Translation management integration [16] will support multi-language campaign delivery, but no progress on cross-channel content distribution occurred today.
Shipped
- AI module release documentation updated — Documentation for the release process was completed to help maintain quality standards as the project evolves [5].
Ongoing
- AI module test framework expansion — Summarization support is being added to the test provider to allow developers to test their summarization functionality more reliably [1][3].
- AI module dialog interface support — Work is underway to enable the schema configuration interface to function inside off-canvas dialogs, expanding where the module can be integrated [2][4].
- AI Integration ECA structured output configuration simplified — The chat action configuration interface is being improved to reduce setup errors and make it easier for business users to define how AI responses should be structured [6][7].
- AI Agents schema editor enhancement — A dedicated editor with syntax highlighting and validation is being implemented to replace the plain text field for JSON schemas, reducing configuration errors [8][9].
- Canvas translation workflow improvements — Multiple fixes are in progress to prevent accidental loss of translated content, including auto-save corrections and delete confirmation modals, plus professional translation management integration [10][16][20].
AI (Artificial Intelligence)
The AI module saw continued development activity over the past 24 hours, focused on expanding testing capabilities and improving user interface flexibility.
Two new pieces of work are now under review. First, Ahmad Khader (Ahmad-Khader) is adding support for summarization features to the module's test framework. This will allow developers building on the AI module to test their summarization functionality more reliably, reducing the risk of bugs reaching end users. Second, Ahmad Khader is working to ensure the module's schema configuration interface works properly inside off-canvas dialogs—a common pattern in modern workflows. Currently, this interface only functions on full-page forms, which limits where it can be used. Fixing this will make the module more flexible for integrations with other tools.
Both improvements are progressing through code review. Additionally, documentation for the release process was updated by Shubham Prakash (shubham.prakash), helping maintain quality standards as the project evolves.
How can I help on this project?
- Assign additional reviewers to accelerate feedback on the two open merge requests, which are currently awaiting review.
- Clarify priority and timeline expectations for dialog support and test coverage enhancements to guide resource allocation.
AI Integration - ECA
Development work has begun on simplifying how users configure structured outputs when setting up automated chat actions. Currently, users must manually type JSON schema definitions into a plain text field, which is error-prone and difficult to review once saved. A task to streamline this configuration interface was opened by Marcus Johansson (Marcus_Johansson), with an associated merge request already submitted by Ahmad Khader (Ahmad-Khader). This change will make it easier for business users to define how AI responses should be structured, reducing setup errors and improving the clarity of saved configurations. The work is tagged as part of the Road to 1.0.0 initiative, indicating progress toward a production-ready release.
No commits were merged during this period; the improvement is under active review.
How can I help on this project?
- Prioritize review and testing of the open merge request to accelerate the path to a stable 1.0.0 release.
- Ensure sufficient resourcing for final quality assurance and documentation as the module approaches production readiness.
AI Agents
The AI Agents module saw focused work on improving the experience of defining structured outputs for AI agents. Currently, users must write JSON schemas into a basic text box, making it difficult to spot errors and hard to read saved configurations. A proposal to use a dedicated schema editor was submitted by Ahmad Khader (Ahmad-Khader), which would replace the plain text field with a purpose-built editor featuring syntax highlighting and validation. This would reduce configuration errors and make it easier for teams to build and maintain AI agents with structured outputs.
The change is under review, with a merge request already prepared. This improvement addresses a usability gap that affects anyone setting up AI agents and should streamline the configuration process once merged.
How can I help on this project?
- Assign a reviewer or technical lead to evaluate the pending merge request, ensuring the schema editor improvement can be finalized and released.
- Clarify priorities for the module roadmap to help contributors focus on the most impactful work for adoption and stability.
Drupal Canvas
Development activity over the past 24 hours centered on three key areas: translation workflow improvements, compatibility work, and data integration capabilities.
Work progressed on making the translation experience safer for users. An issue was assigned to address Missing delete translation confirmation modal, which will prevent accidental loss of translated content by requiring users to confirm before deleting translations. Separately, an important fix is in review for Auto-save should not re-create entities, but set the fields of them: otherwise translations get lost, which resolves a technical issue where saving content was unintentionally discarding translations in other languages.
Significant development continues on professional translation integration through TMGMT translation integration for content entities, which will enable organizations to send content to translation management services directly from the system.
The team is also advancing capabilities for content editors. Work is underway on content-entity-types / fields endpoints for entity reference selection UI, which will improve how users can link and reference related content when building pages.
Routine maintenance includes automated dependency updates and ongoing Drupal 12 compatibility preparation.
How can I help on this project?
- Prioritize review and testing of the translation auto-save fix, as it affects content integrity for multilingual sites
- Provide product input on the content reference selection workflow to ensure it meets real editorial needs
Context Control Center (CCC)
The Context Control Center module saw progress on two workflow and usability issues this period, both supporting the broader AI Initiative Sprint.
A visual alignment problem affecting the overview page checkbox in Drupal 11 has been identified and assigned to Juan Correa (jucs7) for correction. The fix must preserve compatibility with Drupal CMS while resolving the display issue.
Separately, work advanced on a functional gap that prevents other modules from extending the system's scope values. Joshua Fernandes (joshua1234511) documented the issue: a customization hook exists but isn't being used by the forms that need it, blocking downstream modules from adding custom use cases like empathy evaluation. Ahmad Khader (Ahmad-Khader) has submitted a merge request with a proposed solution involving over 380 lines of changes, now awaiting review.
Both issues represent normal refinement work for a module in active development, addressing integration friction and visual polish as the product matures.
How can I help on this project?
- Prioritize code review capacity for the pending scope values extension work to unblock downstream integrations.
- Confirm UI/UX expectations for cross-platform compatibility (Drupal 11 vs. Drupal CMS) to guide resolution of alignment issues.
AI Dashboard
The AI Dashboard project saw limited development activity in the past 24 hours, with one community inquiry submitted. Michael Anello (ultimike) opened a question asking How often is the ecosystem data updated? regarding the refresh frequency for the ecosystem information published on the project's website. This type of question indicates growing interest in the dashboard's data currency and reliability, which are key factors for users making decisions based on AI ecosystem insights.
No code changes, merges, or other development work occurred during this period. The question remains unanswered and unassigned, suggesting the project may benefit from clearer documentation around data update schedules and maintenance practices.
How can I help on this project?
- Ensure adequate maintainer capacity to respond to community questions and set clear service level expectations for data freshness.
- Support the development of user-facing documentation that explains update frequencies and data sources to reduce support overhead.
References
[1] Add Summarization operation type support to the echoai test provider
[2] Support the `ai_json_schema` element inside off-canvas dialogs
[3] Issue #3586537 Add Summarization operation type support to the echoai test provider
[4] Issue #3586536 Support the `ai_json_schema` element inside off-canvas dialogs
[5] Issue #3566566: Update Release Documentation
[6] Simplify structured output configuration in the Chat action
[7] Issue #3585014 Simplify structured output configuration in the Chat action
[8] Use the `ai_json_schema` editor for the AI Agent structured-output schema field
[9] Issue #3586042 Use the `ai_json_schema` editor for the AI Agent structured-output schema field
[10] Missing delete translation confirmation modal
[16] Resolve "Add TMGMT translation integration for content entities"
[23] hook_ai_context_scope_values_alter() is not honored in scope value forms
[24] Issue #3586246: hook_ai_context_scope_values_alter() is not honored in scope value forms
Shipped
Ongoing
- AI module EchoProvider summarization support — MR adds summarize() method to ai_test submodule's EchoProvider for kernel testing downstream integrations [1][3].
- AI module ai_json_schema off-canvas dialog support — MR fixes AiJsonSchema form element failures in off-canvas dialogs, currently blocking bpmn_io modeller integration [2][4].
- AI Integration ECA structured output simplification — MR replaces plain text JSON schema field with ai_json_schema form element in Chat action to improve validation and UX [6][7].
- AI Agents structured output schema editor — MR switches AI Agent form's structured_output_schema field from textarea to ai_json_schema element with CodeMirror syntax highlighting [8][9].
- Context Control Center scope values alter hook — MR ensures hook_ai_context_scope_values_alter() is honored in scope subscription UI and context item forms, currently only invoked in getAllScopeValues() [23][24].
AI (Artificial Intelligence)
Activity in the AI module over the past 24 hours focused on expanding test coverage and improving form element compatibility. Ahmad Khader (Ahmad-Khader) opened two new tasks and corresponding merge requests.
The first task, Add Summarization operation type support to the echoai test provider, aims to extend the EchoProvider mock in the ai_test submodule to support the Summarization operation type. MR !1681 implements the summarize() method to return deterministic output for kernel testing downstream integrations. The issue is currently in needs review state.
The second task addresses Support the ai_json_schema element inside off-canvas dialogs. The AiJsonSchema form element currently fails when rendered in Drupal's off-canvas dialog context, which blocks consumers like the bpmn_io modeller. MR !1680 (142 lines) is open but marked needs work, indicating it requires further iteration before merging.
How can I help on this project?
Review MR !1681 to verify the EchoProvider summarization implementation meets acceptance criteria. Test MR !1680 in off-canvas dialog contexts and provide feedback on rendering and value synchronization issues to help move it from needs work to needs review.
AI Integration - ECA
Activity over the past 24 hours centered on improving developer experience for the Chat action. Ahmad-Khader opened MR !12 to address Simplify structured output configuration in the Chat action, which replaces the plain text JSON schema field in src/Plugin/Action/Chat.php with the AI module's dedicated '#type' => 'ai_json_schema' form element. The current implementation stores the schema as a raw JSON string that gets json_decode()d at runtime (line 115), making it error-prone and difficult to validate. The 74-line diff introduces the structured form element to provide proper validation and editor affordances. The MR is currently open and awaiting review as part of the Road to 1.0.0 initiative led by Marcus Johansson (Marcus_Johansson).
No commits were merged during this period, leaving the MR as the primary blocking item for forward progress on structured output configuration.
How can I help on this project?
AI Agents
Ahmad Khader (Ahmad-Khader) opened Use the `ai_json_schema` editor for the AI Agent structured-output schema field with a corresponding merge request. The issue addresses a usability gap in AiAgentForm::buildFormMetadata() where the structured output JSON schema field currently renders as a plain textarea, making schema editing error-prone and difficult to read. The proposed change switches $form['prompt_detail']['structured_output_detail']['structured_output_schema'] to use the AI module's '#type' => 'ai_json_schema' element (Drupal\ai\Element\AiJsonSchema), which provides a CodeMirror editor with syntax highlighting and JSON linting. The issue is currently in needs review state.
No merge requests were merged and no commits were pushed during this reporting period.
How can I help on this project?
Drupal Canvas
Activity over the past 24 hours focused on dependency updates and issue triage rather than merged code. The Renovate bot opened two dependency update MRs: chore(deps): update mariadb docker tag to v10.11 and fix(deps): update npm minor and patch, updating MariaDB from 10.6 to 10.11 and various npm packages including @axe-core/playwright. The Dependency Dashboard issue was also updated, though it currently reports rate limiting issues with GitHub token configuration.
On the translation front, Ignacio Sánchez Holgueras (isholgueras) was assigned to Missing delete translation confirmation modal, which is in needs work status. The issue addresses UX concerns around accidental translation deletion without confirmation prompts.
Lee Rowlands (larowlan) opened Return early prior to evaluation of prop expressions if the user does not have access to the reference entity, proposing a performance optimization in JsComponent::getExplicitInput by checking entity access before expensive prop expression evaluation.
Several large MRs remain open, including Christian López Espínola's (penyaskito) work on auto-save translation preservation and content-entity-types / fields endpoints for entity reference selection UI.
How can I help on this project?
- Pick up Return early prior to evaluation of prop expressions if the user does not have access to the reference entity, which needs implementation of the access check optimization in
JsComponent::getExplicitInput. - Review auto-save translation preservation MR, which addresses critical translation loss during auto-save operations.
Context Control Center (CCC)
Activity remained steady on the Context Control Center module over the past 24 hours, with two issues receiving updates during the reporting period.
The hook_ai_context_scope_values_alter() is not honored in scope value forms issue saw continued attention. Joshua Fernandes (joshua1234511) identified that the alter hook is only invoked in AiContextScopeManager::getAllScopeValues() but is not consumed by the scope subscription UI (AiContextAgentForm) or context item forms. This creates friction for downstream modules trying to extend scope values, such as custom use cases in the AI Empathy Evaluation module. Ahmad Khader (Ahmad-Khader) has opened MR !177 with 383 diff lines to address the problem.
Meanwhile, the Show this overview page checkbox is misaligned on vanilla Drupal 11 issue was updated and assigned to Juan Correa (jucs7). The task involves fixing the checkbox alignment without breaking compatibility with Drupal CMS.
No merge requests were merged and no commits were pushed during this period.
How can I help on this project?
AI Dashboard
Activity remained quiet over the past 24 hours with no merge requests or commits. The primary activity was a question raised by Michael Anello (ultimike) in How often is the ecosystem data updated?, asking about the update frequency for the ecosystem data displayed at the project's dashboard page. The issue remains unassigned and awaits response from maintainers regarding the data refresh schedule.
No API changes, bug fixes, or feature merges occurred during this reporting period. Development appears to be in a quiet phase with no active blocking issues reported.
How can I help on this project?
- Answer Michael Anello's question about ecosystem data update frequency in How often is the ecosystem data updated? if you have knowledge of the project's infrastructure.
- Review open issues in the queue to identify bugs or feature requests that need attention and could benefit from patches.
References
[1] Add Summarization operation type support to the echoai test provider
[2] Support the `ai_json_schema` element inside off-canvas dialogs
[3] Issue #3586537 Add Summarization operation type support to the echoai test provider
[4] Issue #3586536 Support the `ai_json_schema` element inside off-canvas dialogs
[6] Simplify structured output configuration in the Chat action
[7] Issue #3585014 Simplify structured output configuration in the Chat action
[8] Use the `ai_json_schema` editor for the AI Agent structured-output schema field
[9] Issue #3586042 Use the `ai_json_schema` editor for the AI Agent structured-output schema field
[23] hook_ai_context_scope_values_alter() is not honored in scope value forms
[24] Issue #3586246: hook_ai_context_scope_values_alter() is not honored in scope value forms