## Problem/motivation Follow-up to: #3586258+s Ran AI Best Practices against ai_context and found some things that need fixing: GPT 5.5 doc pulling out all the actionable things: [ai-context-actionable-fix-plan.md](/uploads/c3b583782d3be83fde707399a020b762/ai-context-actionable-fix-plan.md) ## Solution GPT 5.5 assessment: For RC1, I’d only block on items that affect **public API, config shape/defaults, installability, or release expectations**. Most accessibility, render-cache, and UI/test cleanup can happen after RC1 as bug/UX fixes. ### Should Do Before RC1 - **Context prefix default alignment** `config/install/ai_context.settings.yml`, `AiContextSystemPromptSubscriber`, and docs disagree. This is a shipped default/config behavior issue, so fix before RC1. - **Stale `getManageUrl()` docs** If this is contributor-facing API documentation, fix before RC1 so people don’t build against a nonexistent method. - **Confirm Scheduler dependency policy** Decide before RC1 whether Scheduler is truly required. If it should be optional, that is a dependency/config architecture change and should not wait. If it is intentionally required, document/leave it. - **Verify simple install config dependencies** Run the install/config import check before RC1. Only fix if it reproduces warnings/failures. If no failure, do not block. - **Test metadata convention decision** Decide before RC1 whether PHPDoc `@runTestsInSeparateProcesses` remains the convention for D10.5 compatibility. Applying metadata everywhere can happen after unless CI is failing, but the policy should be settled. ### Nice Before RC1, But Not Blocking - `AiContextOverviewController` cache metadata - Revision operation access cacheability - `AiContextRenderer` settings cache dependency - `Drupal.announce()` filter result counts - Links in `#markup` - New-tab accessible warnings - Tooltip/truncated content accessibility - Disabled selects / table captions / help-list render arrays - Test quality cleanup Those are valid bugs/UX/accessibility improvements, but they don’t need to block RC1 unless you want RC1 to represent a stricter accessibility/cacheability baseline. ### My RC1 Blocker Shortlist 1. Fix default context prefix inconsistency. 2. Fix `getManageUrl()` docs. 3. Decide Scheduler required vs optional. 4. Run config install/import verification and only fix if real. 5. Confirm test metadata policy. ### Not Included The following were intentionally excluded because they were false positives, stale, already fixed, or not reproducible in the current checkout: - Treating `MarkdownFormatter` as an XSS bug. - Forcing PHP 8 `#[RunTestsInSeparateProcesses]` attributes while Drupal 10.5 compatibility remains and PHPDoc is the documented convention. - Claims about wildcard `'*'` schema mapping in current `ai_context` schema. - Claims about `description` typed as `text` in current config schema. - Claims that `docs/contribute/testing.md` omits `SIMPLETEST_*` variables. - README grammar issue “relies several modules”. - Current-checkout cspell failure for `datestamp`. - Moving Scheduler config to optional without a maintainer decision that Scheduler should no longer be required. ## AI usage - [x] AI assisted issue