gplay-monetizationlisted
Install: claude install-skill PollyGlot/google-play-cli-skills
# gplay monetization (subscriptions + one-time products)
`gplay subscriptions` and `gplay iap` own the **monetization catalog** as
declarative, version-controlled files (ADR-0041). Shared conventions are in
`gplay-cli-usage`. Both namespaces are `[experimental]`.
| Namespace | What it holds |
|---|---|
| `subscriptions` | subscriptions, their base plans (config + per-territory prices), their offers, lifecycle state |
| `iap` | one-time products, v2 `monetization.onetimeproducts` **∪** legacy `inappproducts` |
Both sit **outside the Edit lifecycle** (no `editId`): `gplay edits begin`
does not batch them.
## The loop
```
pull → edit the .json files → apply --dry-run → apply [--confirm]
```
One `<productId>.json` per product, holding the **API resource verbatim**
minus server-derived noise. `pull` then `apply` with no edits is a guaranteed
no-op. Commit the directory; the diff in review *is* the catalog change.
## Mirror semantics: the trap if you know `metadata`
`metadata apply` is **additive**: a locale live online but absent on disk is
left alone. Monetization is the opposite. **The directory is the complete
declared catalog**: a live subscription, product or offer with no file is a
**delete in the plan**.
- **`pull` before every `apply`.** `apply` refuses an empty directory when
the app has live products, but a *partially* populated one is a legitimate
plan full of deletes.
- **`pull` is destructive locally too**, and refuses to erase a populated
directo