@daemux/store-automator 0.10.20 → 0.10.22

package/.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "App Store & Google Play automation for Flutter apps",
-    "version": "0.10.20"
+    "version": "0.10.22"
   },
   "plugins": [
     {
       "name": "store-automator",
       "source": "./plugins/store-automator",
       "description": "3 agents for app store publishing: reviewer, meta-creator, media-designer",
-      "version": "0.10.20",
+      "version": "0.10.22",
       "keywords": [
         "flutter",
         "app-store",

package/README.md

@@ -168,7 +168,7 @@ npx @daemux/store-automator \
   --track=internal \
   --rollout-fraction=1.0 \
   --in-app-update-priority=3 \
-  --domain=amazingapp-pages.workers.dev \
+  --domain=amazingapp-pages.account-subdomain.workers.dev \
   --cf-project-name=amazingapp-pages \
   --tagline="The best utility app ever" \
   --primary-color="#2563EB" \

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@daemux/store-automator",
-  "version": "0.10.20",
+  "version": "0.10.22",
   "description": "Full App Store & Google Play automation for Flutter apps with Claude Code agents",
   "type": "module",
   "bin": {

package/plugins/store-automator/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "store-automator",
-  "version": "0.10.20",
+  "version": "0.10.22",
   "description": "App Store & Google Play automation agents for Flutter app publishing",
   "author": {
     "name": "Daemux"

package/plugins/store-automator/agents/devops.md

@@ -220,10 +220,10 @@ Set via environment variables or `.mcp.json`:
 After deployment:
 1. Check the output URL is accessible
 2. Verify each page loads correctly:
-   - `https://<project>.workers.dev/marketing.html`
-   - `https://<project>.workers.dev/privacy.html`
-   - `https://<project>.workers.dev/terms.html`
-   - `https://<project>.workers.dev/support.html`
+   - `https://<project>.<account-subdomain>.workers.dev/marketing.html`
+   - `https://<project>.<account-subdomain>.workers.dev/privacy.html`
+   - `https://<project>.<account-subdomain>.workers.dev/terms.html`
+   - `https://<project>.<account-subdomain>.workers.dev/support.html`
 3. Confirm template variables were replaced (no `${VAR}` in output)
 4. Update store metadata URLs if this is the first deployment:
    - `fastlane/metadata/ios/{locale}/privacy_url.txt`
@@ -237,7 +237,7 @@ OPERATION: Deploy Cloudflare Pages
 PROJECT: [cloudflare-project-name]
 RESULT: Success | Failed
 URL: [deployment-url]
-PRODUCTION: https://[project].workers.dev
+PRODUCTION: https://[project].[account-subdomain].workers.dev
 
 Pages deployed:
 - [page]: [status]

package/templates/CLAUDE.md.template

@@ -260,7 +260,7 @@ Implement Flutter app matching designs. Set up Firebase. Fill ci.config.yaml. Ad
 appstore-meta-creator generates texts. Fill fastlane/iap_config.json if needed.
 
 ### Phase 4: Web Pages + Deployment
-app-designer designs marketing page in Stitch MCP. Develop web pages. Deploy via Cloudflare Pages (*.workers.dev domain sufficient).
+app-designer designs marketing page in Stitch MCP. Develop web pages. Deploy via Cloudflare Pages (*.account-subdomain.workers.dev domain sufficient).
 
 ### Phase 5: Finalize and CI/CD
 Create .gitignore (.claude/.tasks/, Flutter ignores; do NOT ignore *.g.dart). Push to private repo. GitHub Actions auto-triggers on push.

package/templates/ci.config.yaml.template

@@ -45,7 +45,7 @@ metadata:
 
 # === WEB PAGES ===
 web:
-  domain: "yourapp-pages.workers.dev"  # *.workers.dev domain is sufficient, no custom DNS needed
+  domain: "yourapp-pages.account-subdomain.workers.dev"  # *.workers.dev domain is sufficient, no custom DNS needed
   cloudflare_project_name: "yourapp-pages"
   tagline: "Your app tagline here"
   primary_color: "#2563EB"

package/templates/scripts/ci/android/upload-metadata.sh

@@ -63,25 +63,39 @@ if [ $FASTLANE_EXIT -ne 0 ]; then
     echo "::warning title=Google Play Draft App::First manual release required. See job summary for instructions."
     if [ -n "${GITHUB_STEP_SUMMARY:-}" ]; then
       cat >> "$GITHUB_STEP_SUMMARY" << 'SUMMARY'
-## :warning: Google Play Draft App — First-Time Setup Required
+## :warning: Google Play Draft App — Closed Testing Required (Internal Testing Is NOT Enough)
 
-Metadata and screenshots were uploaded by CI but **could not be saved** because the app hasn't completed its initial setup on Google Play Console. This is a [Google Play API limitation](https://developers.google.com/android-publisher/edits) — all API edits are rejected until the first manual release.
+Metadata and screenshots were uploaded by CI but **could not be saved** because the app is still in **draft status**. This is a [Google Play API limitation](https://developers.google.com/android-publisher/edits) — all API edits are rejected until the app exits draft status.
+
+**"Draft" is an app-level status**, not a release-level one. Internal testing bypasses Google review entirely, so it **cannot** transition your app out of draft. You must submit to **closed testing** (or higher) to trigger Google's review and remove draft status.
 
 ### One-time setup steps:
 
 1. Go to [Google Play Console](https://play.google.com/console) → Select your app
-2. **Dashboard** → Complete all required setup tasks shown in the checklist
-3. **Store listing** → Create your default store listing (title, description, screenshots)
-   - *Copy-paste the values from the **Store Listing** table below, then re-run CI after setup to auto-upload future changes.*
-4. **Content rating** → Complete the content rating questionnaire
-5. **App pricing** → Set pricing and distribution countries
-6. **First release** → Go to **Testing → Internal testing** → Click **Create new release**
-   - The AAB was already uploaded by CI — select it
-   - Add release notes
-   - Click **Review release** → **Start rollout to internal testing**
-
-### After first release:
-All subsequent CI runs will automatically upload metadata, screenshots, and new builds without manual intervention. Re-trigger the CI workflow after completing the steps above.
+2. **Dashboard** → Complete **all** required setup tasks in the checklist:
+   - **Store listing** — app name, descriptions, screenshots, app icon, feature graphic
+     - *Copy-paste the values from the **Store Listing** table below, then re-run CI after setup to auto-upload future changes.*
+   - **App Content** declarations — **all** of the following:
+     - Privacy policy
+     - Data safety
+     - Content rating questionnaire
+     - Target audience and content
+     - Ads declaration
+     - App access (instructions if login required)
+     - Government apps declaration
+     - Financial features declaration (if applicable)
+     - Health apps (if applicable)
+   - **Pricing and distribution** — countries and free/paid
+3. **Submit to Closed Testing** (not internal testing):
+   - Go to **Testing → Closed testing** → Create a track if needed → **Create new release**
+   - The AAB was already uploaded by CI — select it, add release notes
+   - Click **Review release** → **Start rollout to closed testing**
+   - This submits the app to **Google review**
+4. **Wait for Google review approval** — typically 1-7 days for new apps
+   - :information_source: *New personal developer accounts (created after Nov 2023): Google requires **20+ testers** for **14+ continuous days** of closed testing before you can request production access.*
+
+### After Google approves the review:
+The app permanently exits draft status and all API operations (metadata, builds, screenshots) work automatically. Re-trigger the CI workflow after approval.
 SUMMARY
 
       # --- Append store listing table (read from metadata files) ---