ship-prlisted

# Simon's PR standard — Deploy TLDR first Whenever you create a PR, or finalize/flip one to ready-for-review, the body must START with a deployment TLDR, before any template sections. ## The Deploy TLDR block - Heading: `## 🚀 Deploy TLDR`, as the very first content of the PR body. - Human-readable numbered steps in the imperative mood. - **Only what to DO.** Never what not to do — no warnings, no prohibitions, no rollback caveats in this block. If a hazard genuinely must be recorded, it goes in Dev Notes, not the TLDR. - Cover, in this order, only the items the diff actually needs: 1. Cross-repo merges/deploys and their order, linking companion PRs (e.g. "Merge and deploy your-work-org/some-service#NN first"). 2. Build prerequisites (codebase example: `cd packages/sdk && yarn build` before any API deploy when the SDK changed). 3. The exact deploy command per changed artifact (codebase examples: `yarn fb:deploy:prod` when apps/serverless changed; `firebase deploy --only firestore` when indexes/rules changed; the app box `./update` (awb) for API + portal). 4. Config/env/index/migration steps the diff introduced, as concrete commands. **Audit the diff for a CROSS-ACCOUNT data migration** — a collection or field the change consolidates, renames, or stops reading — and give it its own step with the strict order (migrate FIRST, deploy the code SECOND) and the blast radius named. The new code reads only the new shape, so e