play data-safety: write the conditional required rows (PSL_ACCOUNT_DELETION_URL from accounts.deletionUrl, PSL_SUPPORT_DATA_DELETION_BY_USER from dataSafety.partialDeletion, PSL_DATA_DELETION_URL); a rule table checks every conditional row in check, declarations and --dry before Play answers 400

CHANGELOG.md

@@ -2,6 +2,19 @@
 
 ## Unreleased
 
+- Fix (`play data-safety`): apps with accounts got Play 400 "Invalid safety labels declaration: Response missing for
+  PSL_ACCOUNT_DELETION_URL". When `dataSafety.accountCreation` is not `PSL_ACM_NONE`, the CSV now carries
+  `PSL_ACCOUNT_DELETION_URL` = `accounts.deletionUrl` and `PSL_SUPPORT_DATA_DELETION_BY_USER` = the new
+  `dataSafety.partialDeletion` (delete some or all data without deleting the account; ask the owner), plus
+  `PSL_DATA_DELETION_URL` = new `dataSafety.partialDeletionUrl` (default `accounts.deletionUrl`) when that is true.
+  - Required-row rules in one table (`DATA_SAFETY_RULES`, per data type `typeRules`, `dataSafetyIssues`): account
+    creation -> deletion rows, a selected data type -> collected / shared, ephemeral, required / optional, purposes,
+    `PSL_HAS_OUTSIDE_APP_ACCOUNTS` refused with sign-up methods. `storebound check`, `project.declarations` and
+    `play data-safety --dry` say `missing: <id> (<when>; set <config field>)`; the real run stops before the POST.
+  - A `dataSafety.extra` row with a generated question id now replaces that question instead of adding a second one.
+  - Sources: support.google.com/googleplay/android-developer/answer/10787469 ,
+    support.google.com/googleplay/android-developer/answer/13327111 . Pitfall 21.
+
 - Agent-first console mode. `storebound console plan <form> [--json]` (read-only, offline; `--lookup` asks the App
   Store Connect API for the app id) gives an AI agent everything to fill a console form with its own browser tool:
   the start URL (deep links from apple.appId, play.developerId, the new play.appId and the remembered ids), ordered