docs: controller v0.255.0 — the globe fix on the sign-in-flow pages

R-579 filed and closed the same day: five shell templates loaded style.css
with no cache-buster, so a browser holding the pre-0.254.0 file rendered the
new globe unstyled; and the globe sat outside the card.

- STATUS.md rewritten for the operator: what was seen, why, the third defect
  found while fixing it (version disclosure on the guest share page, caught by
  TestShareGuest_HeadersTilesNoAdminChrome), and the one decision left —
  raise the fleet floor to 0.255.0, with what happens either way.
- 10-localisation.md §3: the shells' asset tag, and why the two guest pages get
  an opaque tag rather than the version.
- Audit D: the parity diff (91 of 106 fixtures identical, every dashboard page
  among them) and the live endpoint evidence from demo-hp guest 9201.

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

documentation/architecture/10-localisation.md

@@ -436,6 +436,16 @@ cannot inherit a language a previous visitor picked in the same browser. The rec
 measured live before it was right: an anonymous form there sets a cookie that `langFor` then ignores,
 and the button appears to do nothing.
 
+**[FACT] Where the globe SITS, and a stale-stylesheet trap that only a screenshot could show
+(v0.255.0, R-579).** On the pages outside the dashboard chrome the globe is **inside the card, centred
+under the footer**, with the menu opening upward — the shared `.lang-globe-menu` rule, so the two
+surfaces cannot drift apart. It was first placed at the corner of the VIEWPORT, which read as a stray
+browser control rather than part of the page. And five of those shells requested `style.css` with **no
+`?v=`**, so a browser holding a copy from before the globe existed kept serving CSS with no
+`.lang-globe` rules and it rendered as a bare, unstyled `<details>`. **Every test passed, because they
+all read the markup and the fault was in which CSS file the browser fetched.** `Version` is now set in
+`executeTemplateLang`, once, for every shell.
+
 **[DESIGN] `POST /lang` is CSRF-exempt, for a reason narrow enough to check.** The only achievable
 effect of a forged request is to change the language of the page the victim's own browser shows them.
 It writes one display-only cookie, reads nothing, touches no setting, and `safeBackPath` refuses a