kappmaker-publishlisted

# KAppMaker — Publish ## Shipping order — read this first Publishing is a chain, and the first release differs from later ones. **Android, first ever release** 1. **Keystore** — `generate-keystore` (below). One per app, forever. Losing it means you can never update that app again, so back it up before continuing. 2. The Play app record must exist → **kappmaker-gpc**. 3. `android-release-build` (below) — signed AAB. 4. `publish` (below) — upload. **Android, every release after that** Skip the keystore, it already exists. Bump the version first (**kappmaker-version**), then `android-release-build` → `publish`. **iOS** The App Store Connect record must exist first → **kappmaker-asc**. Signing is handled by Fastlane (`fastlane configure` below), not by a keystore. **No Mac?** Xcode is the only genuinely Mac-locked step, and it can run on a GitHub macOS runner instead: `kappmaker publish --platform ios --remote`, or `kappmaker ios-ci build` directly. One-time setup is `kappmaker ios-ci init` — see **kappmaker-ios-ci**. On a non-Mac, plain `publish --platform ios` now fails with a pointer there rather than an opaque Xcode error. If a step fails because something upstream is missing, go to that skill and come back — do not improvise around it. ## Before running any command 1. **Prerequisites** — `kappmaker --version` (install: `npm i -g kappmaker`). If a credential is missing the CLI says so; re-run `kappmaker config init`. 2. **Read `AiGuidelines/` first** — the PRD,