diff --git a/plugin-designs/regions-dashboard/src/useRegionsI18n.js b/plugin-designs/regions-dashboard/src/useRegionsI18n.js
index ac86ad260..ca3bcc8db 100644
--- a/plugin-designs/regions-dashboard/src/useRegionsI18n.js
+++ b/plugin-designs/regions-dashboard/src/useRegionsI18n.js
@@ -11,9 +11,14 @@
  * is the point.
  *
  * FALLS BACK TO THE KEY. A missing string renders the English sentence rather than 'regions.Foo'.
- * That matters here: our repo ships 11 locales and DX-life translates 8, so it/ro/zh have no
- * regions.json at all and resolve through this fallback (library/i18n README: a missing area file
- * is fine, fallbackLocale 'en' handles it).
+ * ✗ THE REASON GIVEN HERE IS NOW STALE, corrected 2026-09-27. It read: "our repo ships 11 locales and
+ * DX-life translates 8, so it/ro/zh have no regions.json at all and resolve through this fallback."
+ * MEASURED: all ELEVEN locales now carry a regions.json, it/ro/zh included. The fallback is still
+ * right and still load-bearing — a key absent from a catalogue renders its English sentence, which is
+ * exactly what a reader should see — but it is no longer three whole languages leaning on it.
+ * COVERAGE, measured the same day: 61 of the 61 keys this plugin actually calls are present in all 11
+ * locales. The 62nd that a raw source scan reports is t('Region') appearing only inside two COMMENTS,
+ * which say themselves that DX-life never needed the key (they have no all-regions state).
  *
  * PLACEMENT: plugin-local on purpose. It is four lines shaped entirely by how THESE pages were
  * written, and the repo's rule is to default to the plugin folder and promote to library/ only