Daily Digest
Daily Digest – 7 August 2026
2026 Capabilities Progress
- Page generation — A critical bug was identified where the AI page builder would discard builds when referencing non-existent regions [37], and several Canvas component placement issues were addressed with one resolution merged [61] and another in progress [62]. Active development continues on the client-side orchestration loop with a new dev page builder agent and placement tools [42][49], though these implementations have not yet merged.
- Context management — The Context Control Center advanced toward a major milestone with merged documentation of scope selection and ranking logic [126], though further work on scope eligibility and limits remains in progress [127]. Priority fields for editorial control over context selection order are in development [123], and the Brand Kit color feature was merged into Canvas, enabling centralized brand palette management [64][65].
- Background agents — Two storage reliability issues were identified: one where artifact storage fails on content listing tools [28], and another where database overflow errors occur for anonymous user sessions [29]. No work on scheduling, triggers, or workflow integration was recorded today.
- Design system integration — Component version tracking received work on cache invalidation and data structure collisions [63][74][61], with cache tag inheritance merged to improve Canvas component update reliability [74]. The Brand Kit color implementation provides infrastructure for AI to work with design system tokens [64][65].
- Content creation and discovery — A reranking accuracy issue was identified where search results may be scored using full document text instead of individual chunks, reducing precision [2][6]. An issue was opened where text automators fail to send source content when input and output fields use the same format [1].
- Advanced governance — Text-based entity comparison capability was in progress, providing foundation for conflict detection workflows [77]. Work continues on expanding conflict detection beyond Page entities [55], though branch-based versioning and batch approval features saw no progress today.
- Intelligent website improvements — No direct progress today.
- Multi-channel campaigns — No direct progress today.
Shipped
- AI module maintenance release completed — Versions 1.4.6 and 1.3.11 were released [3].
- Canvas Brand Kit color support base implementation delivered — Brand owners can now define and organize central color palettes; full component configuration integration still in progress [35][64][65].
- Canvas component data cache fixes merged — Resolved widget naming collisions and array property invalidation issues that caused system failures and stale data [31][39][61][74].
- Canvas headless implementation improvements shipped — Page helpers reorganized to properly separate client and server code in JavaScript bundles [40][76].
- Context Control Center scope selection logic documented — Comprehensive review of context ranking and selection behavior completed for beta release [112][126].
Ongoing
- AI module content processing bugs under investigation — Text automators silently drop content when certain field types match [1], and reranking logic incorrectly scores chunks using full document text instead of individual chunk content [2][6].
- AI Agents storage fixes in review — Two merge requests address artifact storage errors and anonymous user session key overflow issues [26][27][28][29].
- Canvas AI orchestration architecture in planning — Multiple issues opened to document client-side agent roadmap, though no implementations in progress [42][43][44][46][47][48][49][50][51].
- Context Control Center approaching beta 4 release — Priority field addition, token budget reliance, and QA test scripts in final review before release candidate [88][89][91][123][124][125].
- Model Context Protocol OAuth scope validation under development — Security feature to restrict authentication permissions for external clients progressing through review [24][25].
AI (Artificial Intelligence)
Work this period focused on identifying and documenting quality issues in the module's content processing capabilities. Two bugs affecting accuracy have been confirmed:
- A content-dropping issue was accepted where the module's text processing features fail to send source content to the AI provider when both the input and output fields use the same long-text format. This causes the system to produce responses based on missing information.
- A reranking accuracy problem was identified in the search component. When processing chunked content, the system currently re-scores all chunks from the same document using the full document text rather than individual chunk content, reducing the precision of search result ranking. A draft fix is under review.
Additionally, a feature request to support provider-native toolsets was accepted, which would allow the module to leverage search, calculation, and other capabilities built into AI platforms rather than reimplementing them.
A maintenance release (version 1.4.6 and 1.3.11) was completed during this window.
How can I help on this project?
- Prioritise testing resources for the content-dropping bug, which affects core text processing workflows and may be impacting production use cases.
- Clarify strategic direction on provider-native tooling: should the module integrate third-party capabilities or maintain full control through custom implementations?
Contributors: Ann Mary Sruthy (annmarysruthy)
Drupal AI Initiative
The Drupal AI Initiative has completed a significant partnership expansion milestone, closing out documentation of 16 successful sponsorship engagements that have built the initiative's funding base over the past year. These partnerships range from founding-level sponsors to silver-tier contributors, representing diverse organizations across the Drupal ecosystem including hosting providers, development agencies, and enterprise platforms.
The closed engagements track the progression from initial founding sponsors in mid-2025 through continued expansion and renewals into 2026, demonstrating sustained momentum in securing financial backing for the initiative. Additionally, a Drupal AI Slide Deck for use in client pitches, conference presentations, and business development communications was finalized.
This body of work represents the completion of administrative tracking rather than new activity in the reporting period, but confirms that partnership development efforts have successfully established a diverse sponsor base to fund ongoing development work.
How can I help on this project?
- Support continued sponsor retention by championing visible deliverables and demonstrating return on investment to current partners as renewal discussions approach.
- Identify and facilitate introductions to potential new organizational sponsors who could benefit from Drupal AI capabilities.
Model Context Protocol
The Model Context Protocol module saw focused development work on improving security controls for authentication. A new validation feature for OAuth scopes is now under development to give administrators control over which authentication permissions are allowed when external clients connect to the server. Currently, clients can request any scope during authentication, which may grant broader access than intended. The new capability will allow site administrators to configure and restrict which OAuth scopes are supported, ensuring tighter security boundaries.
A merge request implementing this scope validation was opened during the period and is progressing through review. This work supports the module's broader goal of providing secure, controlled integration between Drupal and AI-powered tools.
How can I help on this project?
- Prioritize security review resources to ensure the OAuth scope validation feature meets enterprise authentication standards before release.
- Clarify governance around default scope configurations to guide what should be enabled out-of-the-box versus requiring explicit administrator action.
Contributors: Shubham Goel (shubhamgoel)
AI Agents
Over the past 24 hours, work has focused on addressing two storage and execution issues affecting agent reliability. A merge request was opened to resolve an error that occurs when Artifact Storage is enabled on the built-in content listing tool. The failure prevented agent runs from completing, while the same feature worked correctly on other tools. The fix ensures that tools which were never executed during a run are skipped when the system collects stored results, preventing premature retrieval attempts.
A second bug was identified involving how agent status is temporarily stored for anonymous users. When anonymous visitors trigger agents, the system generates long session identifiers that, when combined with internal prefixes, exceed database column limits and cause storage failures. A merge request is already in progress to address the key length overflow.
Both issues affect core agent functionality but are being actively addressed. This is typical maintenance work for a module in active development.
How can I help on this project?
- Prioritize code review bandwidth for the two open merge requests to move fixes into production quickly.
- Consider resourcing for expanded automated testing to catch storage and edge-case failures earlier in development.
Contributors: Prabhavathi Vanipenta (prabha1997)
Drupal Canvas
The past 24 hours saw several important fixes merged that resolve issues affecting both the page builder and headless implementations. A critical bug was fixed where certain field widget configurations could cause system failures due to naming collisions in the internal data prototype cache. Another fix ensures that when component data structures change, all related elements are properly invalidated and updated—previously, nested array properties could be missed during this refresh process.
The Brand Kit color management feature was merged, enabling brand owners to define and organize a central color palette. This provides the foundation for future work that will allow editors to apply brand colors when configuring components. An auto-scroll issue in the drag-and-drop interface was also resolved, and headless page helpers were reorganized to ensure client and server code remain properly separated in JavaScript bundles.
On the AI front, significant planning and architecture work is underway to support a new client-side orchestration model. Multiple issues were opened to document the roadmap, though no implementations were merged during this period. Several component version tracking issues remain open, including one where version hashes can become stale during single-process installations, and another affecting configuration import workflows. Work is in progress to address these through open merge requests.
How can I help on this project?
- Prioritize resources to complete the component version tracking fixes currently in review—these affect deployment workflows and recipe-based installations.
- Support stakeholder alignment on the AI orchestration roadmap to ensure the architecture meets production requirements before implementation begins.
Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm) [1], Canvas version bot [2], Christian López Espínola (penyaskito) [2], David Bravo (davidbp), Feliksas Mazeikis (f.mazeikis), Fons Vandamme (f0ns), Gábor Hojtsy (goba), Harumi Jang (hooroomoo) [1], Kunal Sachdev (kunal.sachdev), Lauri Timmanee (lauriii) [1], utkarsh_33 (Utkarsh_33), wotnak [1]
Context Control Center (CCC)
The Context Control Center reached an important milestone during the reporting period: a comprehensive review of how the system chooses and ranks contextual information was completed and merged. This work establishes the documented foundation for the 1.0 release, ensuring that users can predict which context items reach AI features and in what order.
Separately, Tune conditional subcontext logic was closed after testing determined the existing prompt structure is sufficient for most configurations. Failures were traced to weak guidance on the Purpose field rather than missing technical functionality, and documentation work to help authors write clearer inclusion criteria is now in progress.
Several significant updates are in late-stage review, including changes that remove overlapping configuration limits in favor of token-budget controls, add priority fields for editorial control over selection order, and improve visibility into how context fits within token budgets. These updates refine the configuration experience ahead of the 1.0 candidate releases.
Preparation for formal quality assurance is underway, with test scripts and documentation being developed to support structured pre-release validation. Beta 4 is scheduled for imminent release following a final codebase review.
How can I help on this project?
- Confirm resourcing for structured QA testing against the planned test scripts and schedule to avoid delaying the release candidate.
- Review and approve the strategic roadmap discussion scheduled with Outside AI and Labs stakeholders to align post-1.0 priorities.
AI Dashboard
No development activity was recorded during this period. One configuration issue remains under investigation: Configuring Project Browser on a standard Drupal core install (not CMS) to provide "Install" buttons for AI recipes. This issue relates to how site administrators can install recommended AI features through the interface, which currently shows command-line options rather than one-click installation buttons when using standard Drupal installations.
The module is in early release (version 1.0.3), and this type of configuration question is typical for new integrations between experimental features. The issue does not block core functionality.
How can I help on this project?
- Clarify whether one-click installation of AI features is a priority for the target user base, or whether command-line installation is acceptable for technical teams during this phase.
- Ensure the team has access to testing environments that match the deployment scenarios being reported by early adopters.
AI Search
Activity remained minimal during this period, with no code merged or committed. The module continues to evolve around a key challenge: ensuring that when users search for non-content items (such as configuration data or other structured information), the system respects access permissions before displaying results.
An issue addressing this gap—Provide an API for performing access check on non-content entities—was recently closed. The module had previously only supported content searches with built-in permission handling. Extending search capabilities to other data types required a new mechanism to verify what each user is allowed to see. This work ensures that sensitive or restricted information is not inadvertently exposed through search results, which is critical for data governance and compliance.
No development work was completed in the last 24 hours, suggesting either planning phases or resource allocation elsewhere in the project.
How can I help on this project?
- Clarify priority and timeline expectations for the module's roadmap to help contributors focus effort appropriately.
- Ensure adequate developer capacity is allocated if active progress is needed in the near term.
AG-UI
Activity this week remained limited to issue tracking. A configuration dependency issue was identified that may affect installations attempting to import configuration related to AI agent functionality. The issue was opened to address potential problems during the configuration import process, which if left unresolved could complicate deployment workflows for sites using this module.
No code changes were merged or committed during this period. The module remains in active development with this newly reported issue awaiting resolution.
How can I help on this project?
- Allocate developer time to resolve the configuration import issue, which could block smooth deployments for users.
- Clarify the project's roadmap priorities to help contributors focus on the most impactful work.
References
[2] `AiReranker::extractItemText()` should prefer chunk text over configured indexed fields
[6] bug: #3586637 should prefer chunk text over configured indexed fields
[24] Add OAuth Scope Validation for MCP Authentication
[25] #3569845: Add Oauth Scope Validation
[26] Enabling Artifact Storage on the "List content entities" tool throws error
[28] Skip tools that never executed when collecting tool result images
[29] Agent status tempstore key overflows for anonymous users
[37] Canvas AI: page builder discards the whole build when the LLM names a region that does not exist
[40] Expose headless page helpers from isomorphic package entries
[42] [META]Canvas AI: Client-side orchestration loop roadmap
[43] Canvas AI: Cover the error path that clears stored agent state
[44] Canvas AI: Add Playwright coverage for the component agent hop loop
[46] Canvas AI: Add a Drupal Canvas Agent that answers general questions
[47] Canvas AI: Research how a user can cancel a running chat turn
[48] Canvas AI: Add end-to-end kernel coverage for the dev page builder agent
[49] Canvas AI: Add a dev page builder agent and wire the placement tools
[50] Canvas AI: Add a catalog-only parameter to the get_component_context tool
[51] Canvas AI: Run the agent selected in configuration instead of a hardcoded one
[55] Expand conflict detection and resolution entity types other than Page
[62] bug: Component hover outline stays visible after a drag starts
[63] #3591916 Drain invalidated prop shapes before component generation; narrow the cold-cache guard
[64] #3591838 [PHASE 2] introduce color props
[65] #3591838 brand kit color implementation
[74] #3591917 Array prop shapes inherit their item shape's cache tags
[76] fix(Headless): #3591928 Expose headless page helpers from isomorphic package entries
[77] feat(Conflict detection): #3591668 "Text-based Page entity representation via Canvas API"
[88] Add context item Priority field and use it for selection ordering
[89] Remove max_items context limit and rely on the token budget
[91] CCC QA scripts for 1.0 testing
[112] Review and document context selection ranking factors before 1.0
[123] Issue #3586376: Add context item priority field and selection tie-breakers.
[124] Issue #3586378: Remove max_items context limit and rely on token budget.
[125] Issue #3586226: Add 1.0 QA test scripts for manual testing.
[126] Issue #3586365: Document scope selection and ranking logic.
[127] Issue #3586388: Align scope scoring and contextual detection.
Shipped
- AI module release task for 1.4.6 and 1.3.11 closed — The release task was closed, marking completion of the task [3].
- Canvas TypedData item-prototype collision fix merged — StaticPropSource widget fields are namespaced by field type to prevent different-typed prop widgets from sharing a TypedData item prototype [31][61].
- Canvas array prop shapes inherit item shape cache tags fix merged — This fixes missed invalidation when config changes affect array-of-X props [39][74].
- Canvas headless package entry refactor merged — Page helpers like PageResult and isPageRedirect() moved to isomorphic entry, preventing server code leakage into client bundles [40][76].
- CCC scope selection and ranking logic documentation merged — MR !241 merged documenting how scope eligibility, ranking, and limits work [112][126].
Ongoing
- AI module LLM text automators silently drop base field content — The llm_text_long and llm_simple_text_long automators fail to include source content from long-text base fields in AI provider requests [1].
- AI module reranker should prefer chunk text over indexed fields — AiReranker::extractItemText() reranks against entire entity field content instead of individual chunk text from getExtraData('content'), degrading chunk-level relevance; MR !1908 under review [2][6].
- Model Context Protocol OAuth scope validation in review — MR !44 adds configuration options to restrict which OAuth fields and scopes are supported during MCP authentication [24][25].
- Canvas component version hash staleness on single-process installs — Prop-shape re-resolution is deferred to teardown and skipped on a cold cache; MR !1478 drains invalidated prop shapes before component generation [38][63].
- CCC removing max_items limit in favor of token budget — MR !244 removes the max_items context limit and relies solely on the token budget for selection [89][124].
AI (Artificial Intelligence)
The AI module saw focused issue triage and refinement over the reporting period, though no merge requests were merged or commits pushed. Two bug reports were accepted: LLM: Text / LLM: Text (simple) automators silently drop Base Field content when Base Field and Target Field are both long-text types (Basic input mode) highlights a critical flaw where the llm_text_long and llm_simple_text_long automators fail to include source content from long-text base fields in AI provider requests, causing models to respond as if no input was provided. Meanwhile, AiReranker::extractItemText() should prefer chunk text over configured indexed fields documents a reranking regression in ai_search where chunk-mode results are reranked against entire entity field content instead of individual chunk text from getExtraData('content'), degrading chunk-level relevance. A merge request addressing the reranker issue is under review.
The Release 1.4.6 and 1.3.11 task was closed. Work continues on Drupal 11.4 DeepChat Block does not work with Webprofiler enabled and the newly accepted Allow Internal Tool Calling feature request proposing deny/allow lists for provider-native tools.
How can I help on this project?
Review MR !1908 fixing AiReranker chunk text extraction. Investigate and patch the llm_text_long Base Field content issue. Help scope the Internal Tool Calling feature by proposing API structure for per-operation tool configuration.
Contributors: Ann Mary Sruthy (annmarysruthy)Drupal AI Initiative
The past 24 hours saw significant administrative cleanup as 16 organizational and partnership tracking issues were closed. These covered the onboarding of various sponsors and partners to the AI Initiative, ranging from founding members to silver partners, documented over the past year. Additionally, the Drupal AI Slide Deck issue was closed, which had tracked the creation of presentation materials for pitching Drupal AI to clients and conferences.
No merge requests were merged and no commits were pushed during this period. The activity was entirely focused on issue housekeeping and documentation of past partnership activities.
How can I help on this project?
Check the AI Initiative issue queue for unassigned technical issues without existing merge requests. Consider reviewing open documentation or contributing to companion pages on Drupal.org that align with initiative materials. Test existing AI module integrations and report specific bugs with clear reproduction steps.
Model Context Protocol
The Model Context Protocol module saw development activity focused on OAuth authentication security. A merge request was opened to address Add OAuth Scope Validation for MCP Authentication, which adds validation for OAuth scopes during MCP client-to-server authentication. Currently, authentication succeeds with all dynamically requested scopes, but the proposed changes introduce configuration options to restrict which OAuth fields and scopes are supported. The #3569845: Add Oauth Scope Validation merge request is now available for review, representing 865 lines of diff.
How can I help on this project?
- Review the OAuth scope validation merge request to provide feedback on the implementation and test the authentication flow with restricted scopes.
- Test the proposed OAuth scope validation changes against various MCP client configurations to ensure backward compatibility.
Contributors: Shubham Goel (shubhamgoel)
AI Agents
Two bug fixes were advanced during the reporting period. The first addresses an error when Artifact Storage is enabled on the built-in "List content entities" tool, which causes agent runs to fail with "The action result cannot be retrieved until the action ::execute() method has been called." A merge request was opened that skips tools that never executed when collecting tool result images (Skip tools that never executed when collecting tool result images).
The second issue concerns PrivateTempStatusStorage::getTempStoreKey(), which builds agent status tempstore keys without length bounds. This causes the key to overflow the key_value_expire.name column (128-character limit) for anonymous users with long session-based identifiers. An open merge request (Agent status tempstore key overflows for anonymous users) addresses this overflow.
How can I help on this project?
Review the two open merge requests: MR !339 on artifact storage and MR !338 on tempstore key overflow. Test both patches against the reproduction steps in their linked issues to validate the fixes.
Contributors: Prabhavathi Vanipenta (prabha1997)Drupal Canvas
Several critical bug fixes merged during the reporting period. A collision in TypedData item-prototype caching was resolved by namespacing dangling prop fields by field type in StaticPropSource. Array prop shapes now inherit cache tags from their item shapes, fixing missed invalidation when config changes affect array-of-X props. A headless package entry refactor moved page helpers like PageResult and isPageRedirect() to the isomorphic entry, preventing server code leakage into client bundles.
On the feature side, Brand Kit color support shipped with phase 1 merged (MR !1385), introducing a Color entity type following the W3C color design tokens spec, a Brand Kit panel, and an entity browser. Phase 2 (color props, MR !1432) and phase 3 (usage data and deletion, MR !1479) remain in progress. The CLI tool now supports pushing components as external metadata when the Headless SDK is present, with SDK detection and explicit type: external opt-in. A reluctant vertical drag auto-scroll landed to eliminate unwanted horizontal canvas movement.
Active work continues on component version hash staleness during single-process installs (MR !1478 open), self-healing stored $id in default-relative-url prop sources (MR !1474 open), and clearing component hover outlines on drag start (MR !1483 open). The Canvas AI client-side orchestration loop roadmap has spawned multiple follow-up issues for tooling, coverage, and agent configuration.
Blocking progress: AssetResolver signature incompatibility with Drupal 11.x since core added a $with_dependencies parameter. A drush config:import failure when active_version changed was closed as fixed.
How can I help on this project?
Review MR !1478 addressing component version hash staleness by draining invalidated prop shapes before generation. Review MR !1474 which self-heals stored $id in default-relative-url prop sources. Pick up the unassigned AssetResolver signature incompatibility blocking Drupal 11.x support.
Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm) [1], Canvas version bot [2], Christian López Espínola (penyaskito) [2], David Bravo (davidbp), Feliksas Mazeikis (f.mazeikis), Fons Vandamme (f0ns), Gábor Hojtsy (goba), Harumi Jang (hooroomoo) [1], Kunal Sachdev (kunal.sachdev), Lauri Timmanee (lauriii) [1], utkarsh_33 (Utkarsh_33), wotnak [1]
Context Control Center (CCC)
The module closed Tune conditional subcontext logic after testing showed the current prompt design (parent content, task, and each child's ID and Purpose) is sufficient for well-authored configurations. The work revealed that failures stem from weak Purpose text rather than missing structural data, shifting focus to field guidance for Purpose instead of richer indexing.
The codebase review for beta4 closed after identifying no blocking issues, and MR !241 was merged documenting scope selection and ranking logic. Sprint 15 planning wrapped, with issue triage clearing several postponed items and preparing the backlog for the beta4 release cycle.
Work is underway on token budget management, priority-based selection tie-breakers, and removal of the max_items configuration in favor of token limits. Open merge requests include MR !195 (scope plugin renaming for better DX), MR !244 (max_items removal), and MR !242 (alignment of scope scoring and contextual selection). A bug was reported where the Global context checkbox description renders a literal <br> tag instead of a line break.
The beta tester recruitment issue closed, and the project page was updated with onboarding resources. QA planning continues with script preparation (MR !243) and the QA team becoming familiar with CCC functionality ahead of 1.0 testing.
How can I help on this project?
- Review MR !195 on scope plugin renaming to validate the new labels and descriptions for entity bundle and target entity plugins.
- Test the token budget changes in MR !244 and provide feedback on the removal of max_items configuration.
- Pick up the unassigned bug "Global context" checkbox description renders a literal <br> instead of a line break and submit a patch.
Contributors: Kristen Pol (kepol) [1]
AI Dashboard
No merge requests were merged or commits pushed during this reporting period.
Discussion continued on Configuring Project Browser on a standard Drupal core install (not CMS) to provide "Install" buttons for AI recipes, which addresses the challenge of enabling one-click recipe installation through Project Browser. The issue examines what configuration is needed beyond enabling Package Manager and experimental UI installation settings to surface "Install" buttons rather than "View commands" buttons for AI recipes on the dashboard configuration page.
How can I help on this project?
- Investigate the Project Browser integration requirements for Configuring Project Browser on a standard Drupal core install (not CMS) to provide "Install" buttons for AI recipes by testing the configuration steps and documenting any missing dependencies or settings.
- Review the AI Dashboard codebase to identify how recipe installation buttons are conditionally rendered and what checks determine UI availability.
AI Search
The AI Search module saw minimal activity during the reporting period, with no merge requests merged or commits pushed. The main focus remains on addressing non-content entity support.
An issue tracking access control improvements for non-content entities, Provide an API for performing access check on non-content entities, saw updates during the period. Following recent fixes to enable SearchApiAiSearchBackend to work with non-content entity SearchAPI datasources, this issue addresses the need for a new API to perform access checks on search results before they are returned to users. The issue is currently marked as closed, though its state shows as opened.
No blocking issues or API changes were reported during this period.
How can I help on this project?
Review the closed non-content entity access check issue to understand the API design patterns. Consider testing the SearchApiAiSearchBackend with various non-content datasources to identify edge cases or documentation gaps that could benefit from follow-up work.
AG-UI
Activity was light during this period. An issue was opened regarding a configuration import problem caused by ai_agents dependency settings. The issue addresses a dependency declaration that can cause config import failures, though no merge requests or commits were pushed to resolve it yet.
No merges or API changes occurred during this reporting window. The dependency configuration issue remains the primary known blocker affecting config management workflows.
How can I help on this project?
- Investigate the ai_agents dependency configuration import issue and prepare a patch addressing the dependency declaration.
- Test AG-UI's config import and export workflows to identify any additional edge cases with module dependencies.
References
[2] `AiReranker::extractItemText()` should prefer chunk text over configured indexed fields
[6] bug: #3586637 should prefer chunk text over configured indexed fields
[24] Add OAuth Scope Validation for MCP Authentication
[25] #3569845: Add Oauth Scope Validation
[40] Expose headless page helpers from isomorphic package entries
[63] #3591916 Drain invalidated prop shapes before component generation; narrow the cold-cache guard
[74] #3591917 Array prop shapes inherit their item shape's cache tags
[76] fix(Headless): #3591928 Expose headless page helpers from isomorphic package entries
[89] Remove max_items context limit and rely on the token budget
[112] Review and document context selection ranking factors before 1.0
[124] Issue #3586378: Remove max_items context limit and rely on token budget.
[126] Issue #3586365: Document scope selection and ranking logic.