## Problem The verification verdict is the module's main operator-facing output. Every sentence of it is built with `sprintf()` and never passes through the translation system, so none of it can be translated on any site, in any language, ever. This is not "no translation exists yet": there is nothing for a translator to translate, because the strings never reach the catalogue. `AuditTrailVerifier` composes the verdict in `sprintf()` throughout: ```php $message = sprintf('Chain "%s" verified: %d entries intact.', $chain_id, $count); ``` ```php 'Chain "%s" is BROKEN: a signed checkpoint names row %d, that row is gone, and no segment with a valid lifecycle signature attests a live-purge covering it. Entries have been deleted from the end of the chain.' ``` and so do `summarizeSpineForMessage()`, `summarizeUnauthenticatedAttestations()`, `summarizeExplainedPurges()`, `buildBrokenRowMessage()` and the acknowledged/archived-range summaries. ## Evidence Measured on a French site with the module installed. Triggering `/admin/reports/audit-trail/default/verify` renders: > **Message d'état** — Chain "default" verified incrementally: 30 new entries since genesis. Checkpoint refreshed. The status-message heading is French because it is core's; the verdict is English because it is ours. Asking Drupal's own string collector which of those strings it ever saw: | string | rows in `locales_source` | | --- | --- | | `verified incrementally` | 0 | | `Checkpoint refreshed` | 0 | | `Verify (full)` | 1 | | `Last checkpoint` | 1 | | `Clear chain data` | 1 | The three that are registered are the ones written with `$this->t()` on the same pages. The verdict's own sentences are absent, which is the difference between untranslated and untranslatable. ## Where it surfaces Four user-facing surfaces, not one: - `AuditTrailChainOperationsController::verify()` / `verifyAll()` — `messenger()->addStatus($result['message'])` and `addError($result['message'])`; - `AuditTrailTsaController` — the same, for the timestamp verdict. Deferred: that sentence embeds its forensic detail mid-sentence, and those details carry apostrophes and quotes, so a `@` placeholder escapes them into the drush output. Separating detail from frame there is the same change as separating `checkRow()`'s, below; - `AuditTrailRequirementsHooks::runtime()` — `/admin/reports/status`, which wraps the English in `$this->t('@message @ack', ...)`, translating the shell around a sentence it cannot translate; - `BrokenChainWarningTrait` — the banner at the top of the module's own admin pages. Drush is a fifth consumer and is fine as it is: CLI output is conventionally untranslated, and this issue does not change it. ## It also hand-rolls plurals ```php $ack_count === 1 ? 'range' : 'ranges', $arch_count === 1 ? 'archive' : 'archives', $remaining === 1 ? 'range is' : 'ranges are', ``` English-only pluralisation, in a string no catalogue can reach. `formatPlural()` is what the module uses everywhere else — `AuditTrailRequirementsHooks` alone calls it 19 times. ## Proposed fix Build the verdict as a list of translatable sentences rather than one concatenated string: - the verifier composes `TranslatableMarkup` sentences and returns them on a new `message_parts` key; - `message` stays, and is derived from those parts by casting and joining, so drush and every existing consumer keep working and the English exists in exactly one place; - the four UI surfaces read `message_parts` and render translatable sentences, with the status report listing them as items rather than gluing `@message @ack`; - the hand-rolled plurals become `formatPlural()`. `TranslatableMarkup` survives a `State` round-trip (`__sleep()` keeps the string, arguments and options, and the translation service is resolved on read), so `AuditTrailCronVerifyHooks::summarize()` can store the parts instead of casting them to a string at cron time. That matters: casting in cron would otherwise freeze the verdict in whatever language cron ran under, and the status report would render it in that language for everyone. ## Test The verdict's sentences are asserted to be `TranslatableMarkup`, and a verdict rendered under a second language is asserted to differ from the English one with a translation in place — which fails against the current code, where the two are identical whatever the language. --- AI-Generated: Yes (Claude Code was used to help draft this issue summary and to write the fix and its tests on the merge request. I reviewed and ran the work myself before posting it.)