marketing/facebook: the Facebook APP measured; cover C to your layout (R-919)

The app is no longer the unmeasured view. Solved against the laptop frame, your
Facebook Lite shot gives a visible window of x 349..1290 and your Chrome-mobile
shot x 349..1291 -- the LITE APP CROPS EXACTLY LIKE SIGNED-IN MOBILE WEB, and
both agree with the emulator's 351..1289. Their profile circle is at x 645..1021
from y 451, LOWER than the emulator's y 369, so that figure was pessimistic
rather than wrong and the margin it bought was real. Five views measured now;
the signed-out one is still the binding constraint.

Cover C follows your draft: the wordmark big on top (88 px, was 44), a small
gap, then the catchphrase. The catchphrase is ONE line, not the two you drew,
and the measurement forces it: with the signed-out circle starting at y 232, a
wordmark that size plus two catchphrase lines cannot both sit above it. Drawn as
two lines it measured 392 sampled text pixels behind that circle -- "saját
szabályaid" read "saját szab" there, which is the R-919 defect itself. Sizing
the two lines to fit instead drops the capital to 25 px, the legibility floor.
One line keeps the wordmark big, the capital at 34 px and every measured view
clean: 0 text pixels behind any circle. The laptop moved right and shrank to
540 px to free the width; 64% of it is cropped or covered somewhere, which the
build reports and which is what the decor layer is for.

REPORT-facebook-cover-r919.md

@@ -288,6 +288,34 @@ not the commit.
 **What is NOT claimed:** that CI passed. It did not run. This commit re-triggers it, and the next run's
 verdict is the one to read.
 
+## 14. The Facebook app, measured — and cover C to the operator's layout (2026-10-09)
+
+**The app is no longer the unmeasured view.** The operator opened the live Page in **Facebook Lite** and in
+Chrome on his phone. Both screenshots were solved the same way as before, against the laptop frame whose
+position in the file is known:
+
+| view | cover band | visible window | profile circle |
+|---|---|---|---|
+| Chrome on the phone | 1.510 : 1 | **x 349 .. 1291** | x 645..1021, top y **451** |
+| **Facebook Lite app** | 1.508 : 1 | **x 349 .. 1290** | x 645..1021, top y **453** |
+
+**The app crops exactly like signed-in mobile web**, and both agree with R-919's emulator (351..1289). Their
+circle sits *lower* than the emulator's y 369, so that figure was pessimistic, not wrong — the margin it
+bought was real. Five views are measured now, and the **signed-out** one is still the binding constraint.
+
+**Cover C now follows the operator's draft:** the wordmark big on top (88 px, was 44), a small gap, then the
+catchphrase. One thing had to give, and it is written down rather than quietly decided:
+
+- Drawn as he sketched it — big wordmark **and** two catchphrase lines — the block measured **392 sampled
+  text pixels behind the signed-out circle**: „saját szabályaid" read „saját szab" in that view. That is
+  the R-919 defect itself, so it was not shipped.
+- Sizing the two lines to fit above y 232 instead works out at a **25 px capital** — exactly the legibility
+  floor, and a big step down from the 43 px the cover had.
+- **One line keeps all three things**: the wordmark big (88 px), the capital at 34 px, and **0 text pixels
+  behind any circle in any of the five views**. The laptop moved right and shrank to 540 px to free the
+  width; 64 % of it is cropped or covered somewhere, which is what the decor layer is for and what the
+  build reports.
+
 ## 10. Teardown
 
 Nothing on any host, the hub or Facebook. The work ran in the two git working trees only; the throwaway

marketing/CHANGELOG.md

@@ -1,5 +1,25 @@
 # marketing — CHANGELOG
 
+## facebook — the Facebook APP measured at last; cover C to the operator's layout (2026-10-09)
+
+- **The app view is no longer unmeasured.** The operator checked the live Page in **Facebook Lite** and in
+  Chrome on his phone. Solved against the laptop frame, both give a visible window of **x 349..1290** and
+  **x 349..1291** — the Lite app crops exactly like signed-in mobile web, and both agree with R-919's
+  emulator (351..1289). Their profile circle sits at **x 645..1021 from y 451**, i.e. LOWER than the
+  emulator's y 369, so the emulated figure was pessimistic and the build's margin was real. **Five views
+  are now measured and the signed-out one remains the binding constraint** (circle top y 232, bottom cut
+  at 525).
+- **Cover C now follows the operator's draft:** the wordmark **big on top** (88 px, was 44), a small gap,
+  then the catchphrase. The catchphrase is **one line**, not the two he drew, and the measurement forces
+  that: with the signed-out circle starting at y 232, a wordmark that size plus two catchphrase lines
+  cannot both sit above it. Drawn as two lines it measured **392 sampled text pixels behind that circle**
+  — „saját szabályaid" read „saját szab" there, which is exactly the R-919 defect. Shrinking the two lines
+  to fit instead drops the capital to 25 px, the legibility floor. One line keeps the wordmark big, the
+  capital at 34 px and **every measured view clean (0 text pixels behind any circle)**.
+- The laptop moved right and down to 540 px to make room for the one-line catchphrase; 64 % of it is
+  cropped or covered in some view, which the build reports and which is what decor is for.
+
+
 ## facebook — a phone has TWO views of the cover, not one; the covers fill the frame again (2026-10-09)
 
 The operator saw the cover UNCROPPED on a signed-out phone and asked why, after R-919 had said the sides

marketing/facebook/build.py

@@ -413,20 +413,27 @@ def content_c():
     c = Image.new("RGBA", (CW, CH), (0, 0, 0, 0))
     d = ImageDraw.Draw(c)
     tx = BAND[0] + 12
-    size = headline_fit(L2, 400, 58)
-    headline(c, tx, 104, L1, size, TEXT1)
-    headline(c, tx, 104 + size + 12, L2, size, BLUE_BRIGHT)
-    wordmark(c, tx, 104 + size + 26, round(size * 0.80))
+    # The operator's layout (2026-10-09): the wordmark BIG on top, a small gap, then the catchphrase.
+    # The catchphrase is ONE line, not the two he drew, and that is forced by the measurement: the
+    # SIGNED-OUT circle starts at y 232, and a wordmark this size plus two catchphrase lines cannot
+    # both sit above it. Drawn as two lines it measured 392 sampled text pixels behind that circle -
+    # „saj\u00e1t szab\u00e1lyaid" read „saj\u00e1t szab" there, which is the very defect R-919 is about. Sizing the
+    # two lines to fit instead pushes the catchphrase to a 25 px capital, the legibility floor. One
+    # line keeps the wordmark big, the catchphrase readable and every measured view clean.
+    wordmark(c, tx, 50, 88)
+    size = headline_fit(SLOGAN, 580, 48)
+    x = headline(c, tx, 190, L1 + " ", size, TEXT1)
+    headline(c, x, 190, L2, size, BLUE_BRIGHT)
     # DECOR: the dashboard, now big enough to read, running off the right edge and under the circles
     dec = Image.new("RGBA", (CW, CH), (0, 0, 0, 0))
     d = ImageDraw.Draw(dec)
     shot = Image.open(SHOT).convert("RGBA")
     # The domain chip next to the title names the demo box; covered with the page colour (copy only, source unchanged).
     ImageDraw.Draw(shot).rectangle((684, 32, 826, 70), fill=hexc("#0B1322"))
-    sw = 640
-    sh = int(round(sw * shot.height / shot.width))
+    sw = 540                                       # smaller than before: the one-line catchphrase
+    sh = int(round(sw * shot.height / shot.width))  # needs the width, so the laptop moves right
     shot = shot.resize((sw, sh), Image.LANCZOS)
-    fx, fy, b = 880, 46, 24                        # frame left/top, bezel
+    fx, fy, b = 1055, 46, 24                       # frame left/top, bezel
     d.rectangle((fx, fy, fx + sw + 2 * b, fy + sh + 2 * b), fill=BG2, outline=LINE, width=3)
     dec.alpha_composite(shot, (fx + b, fy + b))
     base_y = fy + sh + 2 * b