play managed publishing: console plan/verify play-publish-changes, ready-to-publish items in play status, desktop hint

skills/console-autofill/SKILL.md

@@ -45,7 +45,7 @@ the UI shows. This is the primary mode.
    `--all` / MCP `all: true` puts every card's steps inline in fix order and ends with the one owner list: tick the
    IARC Terms of Use box (before), Send changes for review (after)), its cards `play-privacy-policy`, `play-ads`, `play-sign-in-details`, `play-advertising-id`,
    `play-government-apps`, `play-financial-features`, `play-health-apps`, and the first production release:
-   `play-production-countries` and `play-production-release`. `storebound console plan` lists them.
+   `play-production-countries`, `play-production-release` and `play-publish-changes` (managed publishing). `storebound console plan` lists them.
 2. Send the owner the `ownerBatch` of every form you will fill in ONE message before you start (AGENTS.md rule 5): the
    `ask-owner` answers (write them into the config, so the plan has them; never guess them) and the `before` steps
    (Play content rating: tick the IARC Terms of Use box on the questionnaire's page 1 first; page 1's Next does

skills/play-first-release/SKILL.md

@@ -103,6 +103,9 @@ products) and answers the compliance facts no file proves, all in one batch at t
     Managed publishing is off by default: the app goes live automatically once Google approves it. If the owner wants
     to pick the moment, they turn on Publishing overview > Managed publishing first; record it in
     `play.managedPublishing` (`play release` and the plan warn while it is off).
+    With managed publishing on, `play status` shows "production X: In review / ready to publish" after approval and
+    names `storebound console plan play-publish-changes`: Publishing overview > "Changes ready to publish" > **Publish N
+    changes** (owner's final button; never Discard changes / Stop managed publishing). `console verify play-publish-changes` reads the API.
 13. **Verify.** `storebound validate --play` (no blockers), `storebound play status` (tracks, listings, products), Console dashboard has no open tasks,
     Publishing overview shows "In review".
 

skills/store-pitfalls/SKILL.md

@@ -1365,3 +1365,14 @@ that fails without the fix (see CONTRIBUTING.md).
   with what was found. Opening waits up to 15 s: on Windows for a visible top-level window of a process
   from the installed path (a running `--hidden` tray copy is shown by the single-instance handler, so a second start
   without `--hidden` opens it), elsewhere for a non-`--hidden` process or a handoff (`tests/desktop-proc.test.ts`).
+
+## 114. Managed publishing: approved, but nothing went live
+- **What happens:** with `play.managedPublishing: true` Google approves the release and it waits in Publishing overview
+  ("Changes ready to publish", button "Publish N changes", e.g. production plus Data safety). `play status` only said
+  "In review / ready to publish".
+- **Do:** `storebound console plan play-publish-changes`, drive to Publishing overview, then the owner's "Publish N
+  changes" and its confirm dialog. Never "Discard changes" or "Stop managed publishing". Check with
+  `storebound console verify play-publish-changes` (API: no production release left ready to publish).
+- **Guard:** `cli/lib/play-publish.ts` (ready list from tracks plus the public store page, the only signal the API
+  gives), the plan, the verify, the hint in `play status` / `status` / the desktop Releases tab. Non-track changes are
+  not visible to the API.