feat(docs): localize structured metadata and gate coverage

README.md

@@ -82,7 +82,8 @@ module, or every module checkout in a workspace, with:
 govoplan-docs-export-public \
   --workspace-root /mnt/DATA/git \
   --output public/docs/v1/catalog.json \
-  --coverage-output docs/DOCUMENTATION_COVERAGE.md
+  --coverage-output docs/DOCUMENTATION_COVERAGE.md \
+  --coverage-baseline docs/DOCUMENTATION_COVERAGE_BASELINE.json
 ```
 
 Use `--check` in publication CI to reject a stale checked-in catalog. Dynamic
@@ -90,6 +91,15 @@ Use `--check` in publication CI to reject a stale checked-in catalog. Dynamic
 on permissions, policy, configuration, and live provider state; the export
 records which modules have such additional documentation.
 
+Static topics localize title, summary, and body through `translations`.
+Rendered metadata such as steps, fields, limitations, consequences, and
+verification uses Core's opt-in `structured_translation_version="1"` plus
+`structured_translations` contract. The registry validates exact shape before
+Docs overlays the requested locale. The public catalog reports structured
+adoption separately. A reviewed coverage-baseline file sets monotonic minima
+and maxima so publication CI also rejects localization or coverage regressions
+after generated output is refreshed.
+
 Pressing `F1` resolves the focused field or action first, then its containing
 dialog or section, current page, and owning module. The shell sends the focused
 context together with `fallback_context` and `module`; Docs selects the first