console: Play App content card Saves are the agent's (declaration-save; Send changes for review, Submit, Publish, Restart review stay forbidden), one owner batch per plan with the IARC Terms tick before the run, console plan play-app-content --all, New App fields typed not set, play.appId from the Create app redirect (console verify --url --write) and storebound play app-id across app list pages

skills/play-first-release/SKILL.md

@@ -24,8 +24,10 @@ products) and answers the compliance facts no file proves, all in one batch at t
    App or Game and Free or Paid (material radios: click the inner `[role=radio]`, then no "Select …" hint may be
    left), and the declarations, which the owner ticks before pressing Create app. Free can never become Paid.
    `storebound console verify play-app-record` checks the form first. Afterwards the app lives at
-   `/console/u/0/developers/<developerId>/app/<appId>/app-dashboard`: put that app id in `play.appId` (the App
-   content forms deep-link from it).
+   `/console/u/0/developers/<developerId>/app/<appId>/app-dashboard`: run `storebound console verify play-app-record
+   --url "<that URL>"` (dry diff of `play.appId`), then the same with `--write` to save it (the App content forms
+   deep-link from it). Missed the redirect: `storebound play app-id` (the app list shows 10 per page and a new app is
+   not on page 1; search the package name, pipe the captures in).
    **Owner step after every Create app:** a service account's app-level permissions do NOT cover apps created later.
    Granting them is the owner's (a permission grant; agents in auto mode are blocked from it too): give the exact
    path in the same message as the Create app button, Users and permissions > the service account > Add app > the new
@@ -71,11 +73,15 @@ products) and answers the compliance facts no file proves, all in one batch at t
     content, Data safety, Advertising ID, Government apps, Financial features, Health apps), each card's page and
     start button (aria-label "Start <Name> declaration"), its own plan (`console plan play-privacy-policy`,
     `play-ads`, `play-sign-in-details`, `play-content-rating`, `play-target-audience`, `play-advertising-id`,
-    `play-government-apps`, `play-financial-features`, `play-health-apps`) and ONE batch of owner questions
-    (`askOwner`): ask them at the start, write the answers into the config (`console.contentRating.details`,
-    `console.appContent`, `social`, `products[].randomRewards`), rerun the plan. Data safety goes through the API
-    (step 9). The IARC Terms of Use box and each card's final Save are the owner's (`store-declarations` skill).
-    Behind a sign-in: the owner types the demo account in Sign in details (`review-access`); with accounts: the
+    `play-government-apps`, `play-financial-features`, `play-health-apps`) and ONE owner batch (`ownerBatch`,
+    printed first): the open answers (write them into the config: `console.contentRating.details`,
+    `console.appContent`, `social`, `products[].randomRewards`; rerun the plan) and, before you start, the IARC Terms
+    of Use box on the questionnaire's page 1 (an agreement; page 1's Next does nothing until it is ticked). Then
+    `console plan play-app-content --all` walks every card in order without a stop: you press each card's **Save**
+    (a declaration save: Google gets nothing before "Send changes for review", the owner's, verified 2026-10-13).
+    Data safety goes through the API (step 9). Behind a sign-in: you type the demo account from
+    `.storebound/credentials.json` (`reviewDemoAccount`, never printed; the owner only when it is not there;
+    `review-access`); with accounts: the
     delete-account URL (`account-deletion`); subscriptions: `storebound play subscriptions` (`store-subscriptions`).
 11. **UI · Store settings (App category).** `play listing` cannot set it (the Play API has no category field), so a
     new app shows "Not selected": set `play.category` (Play's name, e.g. "Strategy"; `storebound check` warns