cross-store text: other platforms named in App Store text (2.3.10: Android, Google Play, ...) or Play text (Metadata: iOS, App Store, Game Center, ...) are refused by every text write (apple / play listing, play release / upload notes, listing set, whats-new, storebound edit, desktop editor), blockers in check / validate, scan other-platforms / play-other-platforms; listing.allowPlatformMentions for the owner's functional mentions; whats-new splits [apple] / [play] lines per store; storebound api --yes without a TTY is refused (exit 1, stderr) instead of a silent dry run; pitfalls 77, 78

skills/review-rejections/SKILL.md

@@ -87,6 +87,11 @@ Plain, polite, specific; one guideline per paragraph; no blame, no threats, no "
 - **2.3 Accurate metadata**: screenshots must show the real app (for a game: real gameplay); no prices, no "free"
   claims for paid items, no other platforms' UI; keywords without competitor names; age rating answers that match
   the content.
+- **2.3.10 Accurate Metadata (other platforms)**: "Android", "Google Play", "Google Play Games" or another store in
+  any App Store text, often a What's New copied from notes shared with Play (store-pitfalls 77). Fix: remove the
+  lines (tag shared notes `[play]` / `[apple]`, `storebound whats-new apply`), `storebound check` must show no
+  `other platform` blocker, push with `apple listing --version x.y.z`, reply "removed the references to other
+  platforms" and resubmit. Play's mirror case is the Metadata policy (iOS, App Store, Game Center in Play text).
 - **2.3.1 Hidden or undocumented features** (Play: Deceptive behavior): remote config, feature flags or a remote
   paywall the review notes did not mention (`storebound scan` rule `remote-features`, store-pitfalls 74). Fix: say in
   the notes which SDK changes what remotely; a business-model change needs a new review and a description update.