admin
a76207945e
gates / gates (push) Successful in 4m31s
Your suggestion to use DevTools device mode was right; "cannot be checked" was too quick a conclusion. On an emulated Pixel 9 (412x924, mobile UA, with a reload so Facebook serves the mobile bundle) the Page's mobile header renders 412x274 = 1.504:1. Facebook keeps the cover's full height and shows only the centre 938 px of its 1640 px width -- 351 px off each side. build.py's safe area leaves 306 px clear per side, 45 px too few, and the light text in cover-c.png runs x333..x997 against a left crop edge of x351, so 18 px are lost: the headline reads "aját szabályaid" and the wordmark "elhom.eu" on every phone. Nothing re-cropped on Facebook (the task's fence). The fix is build.py's safe area (<=938 px, ~900 for margin) plus the measured 172 px centred phone profile circle, then a hand re-upload. R-919 opened; R-918 closed and moved to CLOSED-ITEMS with the recipe that made the check possible. Meta's help page is wrong about Meta's own rendering: it states 2.4:1 for the mobile cover where the header measures 1.504:1, so this session's first-pass arithmetic -- explicitly labelled arithmetic, not a check -- under-predicted the crop about fivefold. That is recorded rather than quietly deleted. Also: the evidence secret scan needed --exclude=README.md, because that README quotes the search strings and was matching itself (4 false EAA hits, 1 false access_token); with the exclusion, control 1 -> 0 and no real hit. And the Business & legal section header was already miscounted before this session (said 9/P2 4, actually held 10/P2 5) -- corrected; five other section headers drift too and are named in the report, left for a session that owns the register.
4.8 KiB
4.8 KiB
marketing — CHANGELOG
facebook — the Page's settings set by hand, and Meta's size page read first-hand (2026-10-08, evening)
Ran marketing/facebook/TASK-page-setup-windows.md from the Windows workstation through Claude in Chrome.
Evidence: documentation/audits/facebook-page-setup-2026-10-08/; report: REPORT-facebook-page-setup.md.
- Done, each read back from a different channel than the edit. Intro →
COPY.md§1 (Graphaboutnow hex-equal to §1, 99 chars); action button → „További információ" athttps://felhom.eu/; Messenger welcome →COPY.md§3, hex-equal, automation on; Page username →felhom.eu, so the Page now answers atfacebook.com/felhom.eu(Graphusernameconfirms it). The operator typed the password Facebook demanded for the username; nothing else needed a human. - Not done —
COPY.md§2 has no field to go in. Facebook's current Pages experience has no long-description field anywhere, and the Graphdescriptionreadsnulland is not writable with the robot key's scopes. Filed R-917 with four options; §2 stays inCOPY.mdunused.facebook/README.md's „What goes where" row says so. facebook/README.mdsizes grade: „READ, second-hand" → „READ, Meta's help page" — and the comparison went the other way. Meta's page (facebook.com/help/125379114252045, quoted verbatim in the audit) carries none of the 820 x 312 / 640 x 360 figures the section asserted; only the 176 px profile size matched, and Meta's mobile profile overlap is ~40 px where we assumed 24. Meta's own page contradicts itself (16:9 on a computer, 2,4:1 on a phone, one 2,70:1 file recommended for both). What we build is unchanged.- Measured on the live Page at a 1435 px viewport: fine. The cover renders whole — no crop, no distortion — the container caps at 1250 px, and the profile circle sits 16 px clear below the cover.
- Measured on an emulated Pixel 9: the cover is CUT on phones (R-919). The mobile Page header is
412 x 274 = 1,504:1, so Facebook shows only the centre 938 px of the cover's 1640 px width — 351 px
off each side.
build.py's safe area leaves 306 px clear per side, 45 px too few, so 18 px of the text is lost: the headline reads „aját szabályaid" and the wordmark „elhom.eu" on every phone. Nothing was re-cropped on Facebook; the fix isbuild.py's safe area (≤ 938 px, ~900 for margin) plus the measured 172 px centred phone profile circle, then the operator re-uploads. Meta's own page is wrong about Meta's own rendering — it states 2,4:1 for the mobile cover where the header measures 1,504:1, so the first-pass arithmetic built on Meta's figure under-predicted the crop about fivefold. - How to see Facebook's phone layout (it cost several wrong turns, recipe in the audit README): narrowing
the window never works —
www.facebook.comhas a minimum width and only grows a horizontal scrollbar, andm.facebook.comredirects towwwunder a desktop user agent. DevTools device mode with a device chosen and then a reload does it; without the reload the already-booted desktop bundle stays (content 901 px wide in a 412 px viewport).wwwthen hangs on the splash under the mobile agent —m.facebook.comloads. - Gotcha, fixed in the session, no row. In Business Suite the automatic-reply editor refused the first save with „A módosítás nincs mentve." and still created the automation and switched it on — carrying Meta's default Hungarian greeting, not ours. A red error toast was therefore a partial write. Reopening the now-existing automation, pasting §3 again and saving gave „Mentve."; the reopened automation reads back hex-equal. Anyone editing this screen must reopen it and read the text back, not trust either toast.
- Nothing was posted; no ad, no boost, no Meta Verified; the Meta app stays in development mode.
facebook — the Page's pictures and texts (2026-10-08)
marketing/facebook/build.py(Pillow only) makesout/profile-dark.png+out/profile-white.png(932 x 932, the logo PNG placed unscaled), three coversout/cover-{a,b,c}.png(1640 x 624) andout/preview.html(self-contained). Checks in the build: profile circle (today's shape 6823 pixels outside radius 0.42 x width → new pictures 0), cover safe area + profile-circle clearance (content layer only), sizes read back from the files. The site's tokens and font.COPY.md: intro (99 of 100 characters), long description, Messenger welcome, three first posts — each claim cites its website page; no price.- Fixed in the session: covers B and C first failed the safe-area check (text in the phone profile circle's corner, the
frame past the phone crop) and were moved;
logo.svgrenders with the wrong lettering here, so the PNG is the master (R-916).