docs: localisation slice 3 CLOSED — evidence, R-558/R-555 closed, R-585 filed
gates / gates (push) Successful in 25s

Part B's live proof is a LOG LINE rather than an e-mail, and the evidence page
says why: severityNotifies drops `info`, so every safe converted producer mails
nobody, and every converted producer above `info` describes something bad that
is not true. Triggering one would mean a false record on a real box's timeline
or a state change the fences forbid. The log line was built in v0.256.1 for
exactly this, after finding there was nothing to look at on either side of the
wire.

  15:07:28  controller_started [hu-only]        — Controller elindult (0.256.1)
  15:08:25  controller_started [+household(en)] — Controller elindult (0.256.1)

The Hungarian sentence is identical in both, and the hub stored the Hungarian
in every case including the English-household push.

R-558 CLOSED, R-555 closed with it. R-585 filed: six producers still send
Hungarian only because their sentence arrives already finished from another
package — `offbox_enlarge_blocked` matters most, since it has no hub entry so
its raw sentence IS the household's whole mail.

10-localisation.md gains 10.4; STATUS rewritten for the operator with the two
decisions left (raise the floor to 0.256.1; whether to rotate the demo
password after R-584).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS
This commit is contained in:
2026-09-18 17:11:15 +02:00
parent 1637fa655d
commit 183727db9c
4 changed files with 136 additions and 29 deletions
+30 -28
View File
@@ -1,43 +1,45 @@
# STATUS — what works, what's broken, what's next
**Updated 2026-09-18 (late) — the globe you photographed is fixed.**
**Updated 2026-09-18 (evening) — your customers' e-mails now follow their language.**
> **Ready for a volunteer: yes.**
**What you saw, and why.** The globe on the sign-in page came out as a bare triangle and two plain
words, floating outside the card. Two separate faults:
**What changed.** Until today every e-mail we sent a household was Hungarian, whatever their box was
set to. The box has been telling us which language it is on for a while; nothing was listening. Now
the e-mails follow it — the nightly backup notes, the "your box has gone quiet" warning, the setup
code, the link that connects a new box, and the page that link opens.
1. **Your browser was still using the old stylesheet.** Those pages asked for the style file without a
version number on the end, so a browser that had already downloaded it kept the old copy — and the
old copy knows nothing about a globe. The main dashboard has always asked with a version number;
these pages never did. **Five pages had it, not three.**
2. **Even styled, it sat outside the card**, pinned to the corner of the window, so it read as part of
the browser rather than part of the page. It is now inside the card, centred under the footer, and
the little menu opens upward.
**You pick a language when you create a customer** (Hungarian unless you say otherwise). That is the
language their box starts in and the language of the first e-mails, which are sent before the box has
ever spoken. **The moment the household picks a language on their own dashboard, theirs wins** — your
choice is a starting point, never an override.
**A third thing I found while fixing it.** My first fix would have printed the exact software version
onto the page a guest opens from a share link — someone you sent a link to, who should not be told
which build you are running. **An existing test caught it.** Those two pages now get a scrambled tag
instead: it does the same job and says nothing.
**Nothing you read has changed.** Your own copy of every alert is still Hungarian, word for word.
That was the part I measured hardest: 56 sample e-mails were captured before a single word moved, and
all 56 Hungarian ones still match exactly.
**Checked on the demo HP box:** the page now asks for the versioned file, the file it gets back
carries the new rule, and the old rule is gone. **What I cannot check is how it looks** — there is no
browser on this machine. That part is your click.
**Proven with a real e-mail.** I pressed the demo box's own "send test notification" button twice, a
minute apart. In English it arrived as *"Dear Customer, this is a test notification…"*; switched back
to Hungarian it arrived as *"Kedves Ügyfél! Ez egy teszt értesítés…"*. Your copy was identical both
times.
**Rows.** One opened and closed the same day.
**One honest gap.** Some alerts contain a sentence the box writes itself — naming a drive, or an app.
Most of those now come in both languages. **Six do not yet**, so an English household can still see
one Hungarian line in a few e-mails. One of those six is a whole e-mail rather than one line. Nothing
breaks; it just reads wrong. It is written down.
**The floor is raised — nothing needs you.** You asked for it, so I did it: every box now must run
0.255.0 or newer. **It delivered on its own:** the N100 was never touched by hand and picked up the
new version in under five minutes. The HP box was already on it.
**Rows.** Five opened, two closed the same day.
Three machines are still on older versions. All three are switched off or blocked, and a box that is
not running cannot be told anything. Each takes the new version the moment it comes back. That is the
floor working, not failing.
**Needs you — two things, neither urgent.**
**One new row, mine, nothing for you to do.** While pressing the button I used a command option that
printed your hub password back into my own session log. It went nowhere else — no file, nothing
saved, nothing sent. I wrote down how to avoid it next time. **If you want to be thorough, change
that password**; nothing suggests you need to.
1. **Raise the floor to 0.256.1?** That is what sends the new version to every box. **If you do:**
households that chose English get English alerts. **If you do nothing:** the hub still writes in
their language, but the sentences the box composes stay Hungarian for them. Nothing is at risk.
I would raise it.
2. **Change the shared demo password?** Not because it leaked anywhere public — it did not. Earlier
today I left five of my own helper scripts on the demo box with the password written inside them,
for a few hours, and found them myself while tidying up. They are destroyed. Changing it is cheap
and would close the question; nothing suggests you must.
---