i18n starter: 10-localisation.md, live evidence, capability row, STATUS + CONTEXT

Design written after the spike ran (controller v0.247.0 live on demo-hp): mechanism,
flow, fallback, gates per language, catalog model, sliced plan with costs, operator
rulings 1-4 recorded, CC decisions 5-6, open decisions 1b and 7.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS

STATUS.md

@@ -1,5 +1,57 @@
 # STATUS — what works, what's broken, what's next
 
+**Updated 2026-09-17 (afternoon) — the dashboard can speak English on three pages, and the Hungarian pages did not change by a single byte.**
+
+> **Ready for a volunteer: yes, unchanged.** A household sees nothing new. English is switched on per
+> box and covers the launcher, the backup overview and an app's page. No recruiting sentence yet:
+> English is a proof of the method, not a feature.
+
+**Decisions I took** (you may reverse either):
+1. **How the text is stored.** One word list per language, filled into the page before the page is
+   built. The other way changes Hungarian characters on the page, so it breaks the „Hungarian must not
+   change" rule.
+2. **The language switch is hidden on Hungarian pages for now.** Only three pages are English, so
+   showing it to every household would put a half-English dashboard one click away. It appears once the
+   rest of the pages are done.
+
+**What I exercised, on the demo box.**
+- I saved the three pages in Hungarian before the update and again after it. They are the same,
+  except the version number and a security token.
+- I switched the box to English with the real switch. The pages came up in English. The hub received
+  „en" in the box's report. I switched it back; the pages are Hungarian again and the hub received „hu".
+- What stays Hungarian on the English pages: some messages built by the program, and the app
+  descriptions from the catalog. Both are later steps of the plan.
+
+**What broke, and whether it is fixed.**
+- Moving the text out of the pages made **one copy check fail and three others blind** to it (for
+  example the check that stops a promise we cannot keep). Fixed in the same release; each check was
+  shown to catch a planted mistake in the moved text.
+- My text-moving tool **missed eight Hungarian words that have no accents**. I found them by reading
+  the result, and fixed the tool.
+- The hub's field check passed the new field for a wrong reason (the word appears in a comment). Filed,
+  not fixed.
+- The count of all Hungarian text: about **1 900 strings in the pages, 1 100 in the program, 65 in the
+  hub e-mails, 830 in the app catalog, and a 1 600-word guide**. The prompt's two rough counts were
+  not reproduced; the difference is named in the inventory.
+
+**Rows.** Ten opened, none closed. The register went from **248** open rows to **258** (the register
+gate's count). Six of the ten are the plan's steps; one is four places where the program decides
+something by reading Hungarian words — those must be fixed before any program text is translated.
+
+**Needs you.**
+1. **Are the console screen and the download page in scope?** Your answer named the dashboard, the
+   e-mails, the guide and the catalog, and not these two. If you do nothing, they wait at the end of
+   the plan; nothing else is blocked.
+2. **Do screen names translate?** I translated them („Indítópult" became „Launcher"). The other choice
+   keeps the Hungarian names so support and household use the same word. If you do nothing, the
+   translation stays.
+3. **For information:** the demo HP box runs the new controller, put there by hand. The other boxes
+   stay on the previous version until you raise the floor. Nothing changes for them if you do not.
+
+---
+
+## Previous note
+
 **Updated 2026-09-17 (midday) — the four things chaos night found are fixed, and three of them were proven on the demo box.**
 
 > **Ready for a volunteer: yes.** Nothing here was blocking; all four made the box more honest or less