https://pawal.codeberg.page/gonemaster/specifications/ui-explanations/index.htmlPlain-language explanations for DNS findings shown on the public results page. One file per module, authored for a domain owner who is not a DNS operator. The markdown files here are the source of truth. Sync them into the i18n catalogs with: node tools/i18n/sync-ui-explanations.mjs The sync script: Writes every managed key to ui-public/src/i18n/en.json. Existing English values are overwritten from the markdown. Never touches other locales. The t() store falls back to English for missing keys, and tools/i18n/missing-keys.sh doubles as the translator work queue for whatever has not been localized yet. Key families pub.tc_desc.<testcase> - per-testcase plain-language description (1-3 sentences). Rendered under the testcase <summary> on the results page. pub.tag.<module>.<TAG>.header - short (3-6 words) human-readable summary of a single finding tag. Rendered inline before the templated engine message. pub.tag.<module>.<TAG>.desc - longer (1-3 sentences) description. Rendered inside a collapsible “About this finding” disclosure under each finding row. Any of the three can be omitted; the UI degrades gracefully.Hugoen-us