Play console steps without an API as agent plans: play-store-settings (App category; play listing cannot set it), play-app-content (every card in order, one owner batch) and its cards (privacy policy, ads, sign in details, advertising ID, government, financial, health), play-production-countries and play-production-release; IARC plan with the Terms of Use agreement, follow-ups (console.contentRating.details, products[].randomRewards, social) and the Summary's final Save; config play.category / countries / managedPublishing, console.appContent; check, validate, play status and play release reminders; inPageLoop helper and material checkbox clicks; App Privacy published signal; first IAPs via apple iap-submit --with-version. Pitfalls 27, 28

skills/play-first-release/SKILL.md

@@ -66,15 +66,34 @@ products) and answers the compliance facts no file proves, all in one batch at t
    permission on any track first.
 9. **API · Data safety.** Answers in `dataSafety` of the config, `storebound play data-safety`, then check the summary
    in Policy and programs > App content > Data safety.
-10. **UI · App content.** `store-declarations` skill: privacy policy, ads, app access, content rating (IARC), target
-    audience, advertising ID, government / financial / health / news, data safety review. Behind a sign-in: App access
-    with the demo account (`review-access`); with accounts: the delete-account URL (`account-deletion`); subscriptions:
-    `storebound play subscriptions` (`store-subscriptions`).
-11. **UI · Store settings.** Category + tags, contact details.
+10. **UI · App content.** `storebound console plan play-app-content --json` lists every card of
+    `/app-content/overview` in order (Privacy policy, Ads, Sign in details, Content ratings, Target audience and
+    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
+    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
+    without it), then `storebound console plan play-store-settings`: /store-settings > the FIRST Edit > App or game >
+    the Category dropdown's `[role=option]` with exactly that name > Save. Contact details come from `play listing`.
 12. **API + UI · Production.** `storebound play release --version-code N --production draft`, then in the Console
     (you, with your browser tool):
-    Production > Countries/regions > Add countries > select all > Save; Production > the draft release > Edit >
-    Next > Save; Publishing overview > **Send changes for review** (owner).
+    a) `storebound console plan play-production-countries`: tracks/production > Countries / regions tab > Edit
+       countries / regions > the mat-checkbox "Select all rows" (or `play.countries`) > Save; a "Go to Publishing
+       overview?" dialog follows. `edits.countryAvailability` is read-only in the API; `storebound validate --play`
+       reports "production has 0 countries".
+    b) `storebound console plan play-production-release`: Releases tab > Edit release > Next (a missing
+       deobfuscation file is only a warning) > Save.
+    c) Publishing overview > "Submit N changes for review" > dialog "Send N changes for review?" > **Send changes for
+       review**: the owner's final button, and it needs a real click (a JS `.click()` did nothing on it).
+    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).
 13. **Verify.** `storebound validate --play` (no blockers), `storebound play status` (tracks, listings, products), Console dashboard has no open tasks,
     Publishing overview shows "In review".