@justai/cuts 0.132.0 → 0.133.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.132.0",
+  "version": "0.133.0",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {

package/src/Posts.astro

@@ -1,5 +1,5 @@
 ---
-import { tagline } from "./tagline.js";
+import { tagline, TAGLINE } from "./tagline.js";
 // ░░ POSTS cut — a persona's feed, revealed by scrolling past the Kernel. ░░
 //
 // The feed's markup, its styling, AND its runtime loader were byte-near-identical across every persona
@@ -102,8 +102,33 @@ const { handle, name, lang, footer, avatarBg, avatarBgLight, avatarSrc, avatarBa
 // (`/tr/`), so it is settled before any script runs — and the same rule the feed permalink pages
 // learned the hard way: a page whose language came from its address must not be second-guessed by
 // what the visitor last picked somewhere else.
-const feedLang = lang ?? Astro.currentLocale ?? "en";
+//
+// ── `Astro.currentLocale` IS UNDEFINED HERE, ON EVERY PERSONA IN THIS FLEET ─────────────────────
+//
+// It was written as the fallback and it has never once fired. The fleet routes languages through a
+// `[lang]` PARAMETER, not Astro's i18n config, so `currentLocale` is undefined in every persona that
+// has one — `Sheet.astro` says exactly this, in this same package, and the two comments contradicted
+// each other with the wrong one load-bearing.
+//
+// MEASURED 2026-08-21, and it is not theoretical: `time.app.zone/tr/` and `tabata.app.zone/tr/` were
+// closing their feeds with *"made to matter"* — the ENGLISH house line, on a Turkish page — because
+// neither passes `lang`. Fifteen of the twenty-five personas that render this cut are in that state.
+//
+// So there are two answers, one per surface, and neither is "ask fifteen repos to remember":
+//   the footer  → rendered by the server, so it is RE-LABELLED at runtime from `<html lang>`, which
+//                 is the pattern this package already uses for the words a cut owns
+//   the feed    → fetched by the loader, which runs at runtime and can simply read `<html lang>`
+// `lang` still wins wherever a persona states it: a stated fact beats an inferred one.
+const feedLang = lang ?? "en";
 const foot = footer ?? tagline(feedLang);
+// Only a STATED language rides on the section. An inferred "en" here would look identical to a
+// persona that really is English, and the loader could no longer tell the difference.
+const statedLang = lang ?? undefined;
+// The house line is re-labelled at runtime ONLY when the persona did not state its language and did
+// not override the sentence. A consumer's word always wins — the same rule `data-chrome` keeps.
+const RELABEL = !lang && !footer
+  ? `(function(){try{var T=${JSON.stringify(TAGLINE)},l=(document.documentElement.lang||"en").toLowerCase().split("-")[0],e=document.querySelector("[data-house-line]");if(e&&T[l])e.textContent=T[l];}catch(_){}})();`
+  : "";
 const vars = [
   avatarBg && `--feed-av-bg:${avatarBg}`,
   avatarBgLight && `--feed-av-bg-light:${avatarBgLight}`,
@@ -115,7 +140,7 @@ const vars = [
   id="posts"
   data-persona={handle}
   data-name={name}
-  data-lang={feedLang}
+  data-lang={statedLang}
   data-av={avatarSrc ?? "/icon.svg"}
   data-av-dark={avatarSrcDark}
   data-av-bare={avatarBare ? "" : undefined}
@@ -124,7 +149,7 @@ const vars = [
   <!-- filled at runtime by the loader below (lazy, on Posts-cut intersection) — single source: the console -->
   <div id="feed"></div>
   <footer class="z-foot">
-    <a href="https://justai.pro">justai.pro</a> · {foot}
+    <a href="https://justai.pro">justai.pro</a> · <span data-house-line={!lang && !footer ? "" : undefined}>{foot}</span>
     {/* the change-your-mind door: hidden until the shell's consent script labels + reveals it
         (Base owns the behavior and the localized label; this cut only owns the placement). On a
         page with no analytics — and so no consent banner — it simply never appears. */}
@@ -132,6 +157,8 @@ const vars = [
   </footer>
 </section>
 
+{RELABEL && <script is:inline set:html={RELABEL}></script>}
+
 <style>
   /* ---- POSTS cut — a conversation: ONE line descends from the post's avatar and
      connects every comment & reply (they're all replies to the post). ---- */
@@ -333,9 +360,12 @@ const vars = [
     // so it may carry markup (justai's ".pro" span). Every name that comes from the API is escaped.
     const PERSONA = section.dataset.persona || "";
     const NAME = section.dataset.name || "";
-    // THE PAGE'S LANGUAGE, set by the cut above from the same value that picked the footer. Not
-    // localStorage: on a localized home the language is in the URL and was settled before this ran.
-    const LANG = section.dataset.lang || "en";
+    // THE PAGE'S LANGUAGE. `data-lang` is present only when the persona STATED it; otherwise the
+    // document's own `lang` is read, which is the one place every persona in this fleet agrees —
+    // `Astro.currentLocale` is undefined under `[lang]` routing and cannot be the fallback it looks
+    // like. Not localStorage either: on a localized home the language is in the URL, settled before
+    // this ran, and a link shared in Turkish must open in Turkish for whoever follows it.
+    const LANG = (section.dataset.lang || document.documentElement.lang || "en").toLowerCase().split("-")[0];
     if (!PERSONA) return;
     // Astro scopes this component's CSS by a data-astro-cid-* attribute; runtime nodes lack it, so copy it.
     const scopeAttr = section.getAttributeNames().find((n) => n.startsWith("data-astro-cid-")) || null;