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/store-pitfalls/SKILL.md

@@ -763,7 +763,8 @@ that fails without the fix (see CONTRIBUTING.md).
   bundleIdCapabilities answers, lag, a write that never sticks).
 
 ## 66. `storebound api apple ... --body f.json --yes` only dry-ran from an agent
-- **Do:** expected: writes through `storebound api` are sent only from an interactive terminal, by design. Use the
+- **Do:** expected: writes through `storebound api` are sent only from an interactive terminal, by design (since
+  pitfall 78 it is a loud refusal with exit 1, not a dry run). Use the
   dedicated command the message names (bundle id capabilities: `apple signing ensure`; IAPs: `apple iap`; listing:
   `apple listing`, ...), which runs anywhere with its own dry run and read-back.
 - **Guard:** `dedicatedCommand` (cli/api/gate.ts), `tests/signing-capabilities.test.ts`.
@@ -925,3 +926,26 @@ that fails without the fix (see CONTRIBUTING.md).
   Uploading and selecting are normal steps, not owner buttons; the version's Submit for Review stays the owner's.
 - **Guard:** `cli/apple/creative-assets.ts`, `tests/creative-assets.test.ts` (fake App Store Connect: dry run, upload,
   waiting, select, replace on a changed file, nothing on the same file).
+
+## 77. What's New shared with Play rejected on the App Store (2.3.10)
+- **Symptom:** a Mac App Store version was rejected under Guideline 2.3.10 (Accurate Metadata): its What's New came
+  from release notes shared with Google Play and had "Google Play Games" and "Android" lines. storebound wrote it
+  without a word (the old check was a warning in the editor only).
+- **Cause:** one notes source for both stores, no per-store split, and no write that refused other platforms. Google
+  Play's Metadata policy is the mirror case (iOS, iPhone, App Store, Game Center, TestFlight in Play text).
+- **Do:** tag store-specific lines `[play]` / `[apple]` in shared notes (whats-new skill); `storebound check` must
+  show no `other platform` line. A functional mention (a "Continue with Google" / "Sign in with Apple" button) is the
+  owner's call: `listing.allowPlatformMentions: [{ store, text, reason }]`. Never add an entry yourself.
+- **Guard:** `cli/lib/cross-store.ts` (term lists, per locale / field / line, the allowlist, `notesForStore`).
+  Refused before anything is sent, dry runs included: `apple listing`, `play listing`, `play release` /
+  `play upload` (release notes), `listing set`, `whats-new check` / `apply`, the desktop editor and `storebound edit`
+  (`appleLocaleIssues` / `playLangIssues` errors). `check` / `validate` blockers (`other-platforms`), `scan` rules
+  `other-platforms` (2.3.10) and `play-other-platforms` (Play: Metadata). `tests/cross-store.test.ts`.
+
+## 78. `storebound api ... --yes` piped or redirected became a silent dry run
+- **Symptom:** `storebound api apple <write> --yes | tail` (or `> out.json`) printed a dry run and exited 0; the
+  owner thought it was sent. Happened twice.
+- **Cause:** writes need an interactive terminal; without one the gate fell back to a dry run.
+- **Do:** run writes without a pipe or redirect in a terminal, or use the dedicated storebound command.
+- **Guard:** `decide` in `cli/api/gate.ts` refuses (`NOT_A_TTY`): exit 1, the message on stderr, nothing sent, the
+  dedicated command named. Without `--yes` a write is still a plain dry run. `tests/api.test.ts`.