console plans: guardrails from a real run (2026-10-21): health none label and Sign in details Yes/No + Add details (old labels as altLabels, verify accepts both), finance boxes on step 1, App Privacy Additional Setup Required OK, verify from DOM input states (verify.capture, --from), Save + confirm before every Next on Play pages, IARC Digital purchases boxes and an exact-label in-page helper that refuses patterns and blanket answers; review contact found in parent folders, the profile and more key shapes with the files checked listed; one-line errors for missing required values (Args.required); pitfalls 86-87, tests
This commit is contained in:
parent
a6dab8f3aa
commit
335a4124ab
23 changed files with 486 additions and 74 deletions
|
|
@ -117,8 +117,9 @@ the UI shows. This is the primary mode.
|
|||
the Category dropdown's `[role=option]` with exactly the category name (`play.category`) > Save.
|
||||
- **Play App content** (2026-10-12): `/app-content/overview`; each card has a button aria-label="Start <Name>
|
||||
declaration". Pages: privacy-policy, ads-declaration, testing-credentials (Sign in details), ad-id-declaration,
|
||||
government-apps, finance (2 steps; the last has "My app doesn't provide any financial features"; Next, Save),
|
||||
health (2 steps; the last step's "Other" box was the no-features answer on that run; Next, Save),
|
||||
government-apps, finance (2 steps, 2026-10-21: the checkboxes, "My app doesn't provide any financial features"
|
||||
among them, are on step 1; step 2 is an information page only), health (2 steps; 2026-10-21: the last step offers
|
||||
"My app does not have any health features", tick that; only an older page without it took "Other"),
|
||||
target-audience-content (age checkboxes; with 13+ only it went straight to the Summary, no appeal question; Save),
|
||||
content-rating-overview > "Start questionnaire" > content-rating-iarc-questionnaire. Each card's Save is yours
|
||||
(2026-10-13: nothing goes to Google before the owner's "Send changes for review").
|
||||
|
|
@ -131,6 +132,21 @@ the UI shows. This is the primary mode.
|
|||
terrorism, crimes). The answers come from `console.contentRating.answers` and `.details`, `products[].randomRewards`
|
||||
and `social`. Save, then Next to the Summary with per-authority ratings; its button is **Save**, not Submit: yours
|
||||
(a declaration save). Example: PEGI 7, ESRB E10+, USK 12, ClassInd 18 (paid random items), Google Play 7+.
|
||||
- **Save after every page** (Play, 2026-10-21): on a multi-step Play form with a Save next to Next (the IARC
|
||||
questionnaire, finance, target audience), answer the page, press **Save**, wait for "Your changes have been saved",
|
||||
and only then press Next. The plan steps and the rule line say so on every such step.
|
||||
- **IARC Digital purchases** (2026-10-21): Yes on "Digital purchases" reveals checkboxes ("Purchases of digital goods"
|
||||
and others); tick them first, the loot-box and trading follow-ups show only after that. Answer every IARC question
|
||||
by its exact console label: a keyword helper answered this one No because its text also mentions "cash rewards". The
|
||||
in-page helper refuses patterns, radios without their exact question (`within`) and blanket group answers.
|
||||
- **Sign in details** (2026-10-21): the first question reads "Is any part of your app restricted?" with Yes / No; the
|
||||
dialog button is "Add details" (older pages: the long radio labels and "Add instructions"; the plan keeps both).
|
||||
- **App Privacy "Additional Setup Required"** (2026-10-21): after saving the data types this message appears; its OK
|
||||
sometimes opens the first type's setup dialog by itself. That dialog IS the first type's setup: carry on from step 1
|
||||
there, do not press its Set Up again.
|
||||
- **Verify reads input states** (2026-10-21): Yes / No radios and unticked boxes are not in page text. Run the plan's
|
||||
`verify.capture` snippet (it returns every radio / checkbox with aria-checked, checked or aria-selected as JSON) and
|
||||
pipe it to `storebound console verify <form> --from -`; the page-text path stays for text answers.
|
||||
- **App Privacy Publish** (2026-10-12): a `<dialog>` "Publish Your App Privacy Responses?" with Cancel / Publish (the
|
||||
owner's); afterwards the page shows "Published a few seconds ago by …", which `console verify` reads.
|
||||
- **Play first production release** (2026-10-12): countries are console-only (`edits.countryAvailability` is
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue