facebook: the Meta app is LIVE (R-915 closed); website lockup entry

R-915 closed and moved to CLOSED-ITEMS in the same commit. What it had waited on was R-813's Terms of Service URL, which did not exist until the closed-test legal set went live this morning. Filled in the app's Basic settings and verified they persisted across a full reload (not from the save toast): Privacy policy URL https://felhom.eu/adatkezeles Terms of Service URL https://felhom.eu/feltetelek Data deletion instructions URL https://felhom.eu/adatkezeles Category "Vallalkozasok es oldalak" THE APP ICON WAS NOT REQUIRED. The original row listed it among the Live blockers; Meta answered "All required app settings are complete" with it still empty. Recorded so the next session does not go hunting for one -- and it could not be uploaded from here anyway: the icon control creates its file input only on click, and clicking opens a native dialog the browser tooling cannot drive. Published, and READ BACK FROM A FULL PAGE RELOAD rather than the success toast, because Meta's toasts have lied on this Page before: the badge reads Published, the string Unpublished is gone, and the page now offers Unpublish. Nothing was granted. No permission added, no use case changed; the scopes stay "Ready for testing", which is all a system user needs for the business's own Page. Going Live changes WHO CAN SEE what the app posts, not what it may do. R-917 and R-920 are unblocked by this -- both were waiting on posting starting. R-813's next action (a) is spent. Also carries the marketing CHANGELOG entry for the header/footer change pushed in 625d38645c. CI for the three commits before this one: #875 SUCCESS (after a re-run -- the first attempt was R-887's lost-job flake, "Set up job" 11m48s then every step 0s), #876 SUCCESS, #877 SUCCESS.
2026-10-09 14:06:35 +02:00
parent 625d38645c
commit de52bcbdc8
5 changed files with 73 additions and 5 deletions
@@ -26,6 +26,16 @@

 ---

+## 2026-10-09 — the Meta app is Live: the Facebook Page can post in public
+
+The full text of the row below: `git show 625d38645c:documentation/backlog/OPEN-ITEMS.md`.
+
+| Row | What | Closed | Evidence |
+|---|---|---|---|
+| **R-915** | **The Meta app `felhom.eu` was in development mode, so anything it posted was visible only to people with a role on the app.** (P4) | CLOSED 2026-10-09 — the app is **Published**. What it had been waiting for was R-813's Terms of Service URL, which did not exist until the closed-test legal set went live that morning. Filled in Basic settings: **Privacy policy URL** `https://felhom.eu/adatkezeles`, **Terms of Service URL** `https://felhom.eu/feltetelek`, **User data deletion → Data deletion instructions URL** `https://felhom.eu/adatkezeles` (the notice says how: write to `info@felhom.eu`), **Category** „Vállalkozások és oldalak". Meta then reported **„All required app settings are complete"** — the app **icon turned out NOT to be required**, which is worth recording because the original row listed it among the blockers. **Read back from a full page reload, not from the success toast** (Meta's toasts have lied on this Page before): the sidebar badge reads `Published`, the string `Unpublished` is gone, and the page now offers `Unpublish`. No permission was added and no use case changed — `business_management` et al. stay „Ready for testing", which is all a system user needs for the business's own Page. | `audits/facebook-page-details-2026-10-09/E1-meta-app-published.jpg` |
+
+**Reasoning kept.** Going Live is about *who can see what the app posts*, not about new powers: the system user already had the Page scopes, and nothing was granted here. The app icon, display name and contact e-mail were listed as Live blockers in the original row; only the two URLs and the category actually were.
+
 ## 2026-10-09 — can the business survive losing DooPlex: Gitea + secrets off-site, Gitea and the hub restored into throwaways

 The full text of every row below: `git show 59f1ad2b86:documentation/backlog/OPEN-ITEMS.md`.