## Summary Status is stored per translation. `AiContextLanguageService::translateItem()` returns a requested translation whenever it exists, without checking whether it is published. Selection, List, and Load check `access('view')` on the default translation before the language switch. A kernel test as a user with only **Use Published AI Context in AI Features** confirmed these effects on `1.0.x`: - The List tool prints the label and purpose of an Archived translation. - The Load tool returns no content for an item whose request-language translation is Archived. - Selection throws an `AccessException` when a selected item has an Archived translation in the request language, so context push fails for that user. - A published translation of a draft source is not delivered, because the view check runs on the draft. The conditional subcontext prompt sends parent text to the AI provider. It uses the translated parent, so it was exposed to the same problem. Sites with moderated translations often start a translation as Draft, so many multilingual sites are affected. Part of #3586615+s. Target: 1.0.0. ## Proposed resolution - In `translateItem()`, return the requested translation only when it is published. Otherwise return the default translation. The fallback does not depend on the current user. - In `translateItems()`, keep the item only when the chosen translation is published and the current user can view it. - Remove the view checks on the default translation in the selector, List, and Load. All delivery paths and the budget estimate already call `translateItems()`. The selector, the Load tool, and the budget estimate also pass subcontext children through `translateItems()`. So with this fix, a child whose delivered translation is unpublished, or that the current user cannot view, is dropped on those paths. #3586617+s replaces this boolean check for children with one that keeps the access cacheability, and also filters children before the conditional decision. ## Remaining tasks - [x] Kernel: `AiContextSelectorTranslationTest` reader cases (published translation of a draft source; Archived translation of a published source). - [x] Kernel: `AiContextTranslationPublishedTest` covers List, Load, the conditional prompt on the selector and Load paths, the reverse case in both languages, exact empty List output, and administrative access, including an administrator who must not get a draft source. - [x] EchoAI kernel: an agent run in Spanish as a non-admin user gets the English text and the other selected items. - [x] Docs: `docs/features/multilingual.md`. - [x] Docs: correct the sentences that said the translation is used "when one exists" in `context_selection.md`, `multilingual.md`, `scopes.md`, and `function_calls.md`. - [x] Release note. - [x] Kernel: selection as a user without context permissions returns no items (`AiContextSelectorTranslationTest::testUserWithoutContextPermissionGetsNoItems`). - [x] Open the MR (!350). - [x] Run the functional tests and do the browser check. @Pravesh_Poonia ran the functional tests, and @kieran.cott did the browser check (2026-10-19). - [x] Merge `1.0.x` into the branch and re-run the kernel tests. - [ ] Merge this before the subcontext child access fix, which must then add a published check for children (see #3586617+s). ## Release note On multilingual sites, an unpublished translation of a context item (for example, Draft or Archived) is no longer delivered to AI prompts or tool output. The published default-language text is used instead, and the item is left out when that is not published either. This applies to every user. Users with **Administer AI Context** or permission to view unpublished items no longer receive unpublished translations in prompts. A published translation of a draft source is now delivered to non-admin users in that language. Context push no longer fails for non-admin users when a selected item has an unpublished translation in the request language. ## Environment - Module version: 1.0.0-rc1 (8a57807). Reproduced on `1.0.x` at that commit. > [!note] > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [ ] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > > * [x] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._