@daemux/store-automator 0.8.0 → 0.9.0

package/.claude-plugin/marketplace.json

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@daemux/store-automator",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "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.8.0",
+  "version": "0.9.0",
   "description": "App Store & Google Play automation agents for Flutter app publishing",
   "author": {
     "name": "Daemux"

package/plugins/store-automator/agents/appstore-meta-creator.md

@@ -152,14 +152,19 @@ af, am, ar, hy-AM, az-AZ, eu-ES, be, bn-BD, bg, my-MM, ca, zh-HK, zh-CN, zh-TW,
 ## Translation Process
 
 1. Create complete English (en-US) metadata for both platforms first
-2. For EACH target language from ci.config.yaml metadata.languages, spawn a sub-agent (Task tool) with:
-   - The complete English source texts for all files
-   - Target locale code (Apple and Google variants)
-   - Platform (ios and android)
-   - Character limits per field (critical -- translations often expand 20-40%)
-   - Translation instructions (see below)
-3. Launch up to 10 sub-agents in parallel for speed
-4. Each sub-agent writes files directly to the correct locale directory
+2. Group target languages from ci.config.yaml metadata.languages by similarity:
+   - Romance: es-ES, es-MX, fr-FR, fr-CA, it, pt-BR, pt-PT, ro, ca, gl-ES
+   - Germanic: de-DE, nl-NL, sv, da, no, fi
+   - Slavic: ru, uk, pl, cs, sk, hr, bg, sr, sl, mk-MK, be
+   - CJK: ja, ko, zh-Hans, zh-Hant, zh-Hant-HK, zh-CN, zh-TW, zh-HK
+   - South/Southeast Asian: hi, th, vi, id, ms, bn-BD, ta-IN, te-IN, ml-IN, mr-IN, kn-IN, gu, my-MM, km-KH, lo-LA, si-LK
+   - Middle Eastern: ar, ar-SA, he, tr, fa, ur
+   - Other: hu, el, et, lv, lt, ka-GE, hy-AM, az-AZ, kk, ky-KG, mn-MN, ne-NP, af, am, sw, zu, fil, is-IS, eu-ES, rm, pa
+3. Create a translation team using TeamCreate with 2-5 teammates:
+   - Each teammate handles 2-5 language groups (based on total languages configured)
+   - Teammate prompt includes: English source texts, target locale codes (Apple + Google variants), character limits per field, translation instructions
+   - Each teammate writes files directly to the correct locale directories
+4. Wait for all teammates to complete, then verify all languages are covered
 
 ### Translation Instructions for Sub-Agents
 

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

@@ -138,7 +138,48 @@ If a `.claude/.tasks/` file path is provided, read ONLY that file for requiremen
 Scan the codebase for already-implemented items. Pick 3-5 UNIMPLEMENTED
 related requirements. Design only those. Report: "Batch: N of ~M remaining."
 
+## Team Composition Recommendation
+
+**MANDATORY section in your output.** The orchestrator uses this to create teams.
+
+After your architecture design, include this section:
+
+```
+### Team Recommendations for Orchestrator
+
+**Files touched:** {count}
+
+#### Developer Team (Flutter)
+- **Teammates:** {N} (based on file count: 3-4 files → 2, 5-7 → 3, 8+ → 4)
+- **Teammate 1 scope:** Screens and widgets — {list of files}
+- **Teammate 2 scope:** Providers and repositories — {list of files}
+- **Teammate 3 scope:** Firebase/backend services — {list of files} (if applicable)
+- **Rationale:** {why this split works}
+
+#### Reviewer Team
+- **Teammates:** 2-3
+- **Reviewer 1 focus:** Dart code quality, patterns, maintainability — files: {list}
+- **Reviewer 2 focus:** Security, Firebase rules, data validation — files: {list}
+- **Reviewer 3 focus:** Performance, store compliance — files: {list} (if 5+ files)
+
+#### Tester Team
+- **Teammates:** 2-4
+- **Tester 1 focus:** Flutter unit and widget tests — {scope}
+- **Tester 2 focus:** Mobile UI testing (iOS) — {scope}
+- **Tester 3 focus:** Mobile UI testing (Android) — {scope} (if applicable)
+
+#### App Designer Team (if design stage applies)
+- **Teammates:** 2-3
+- **Designer 1 scope:** App screen designs — {deliverables}
+- **Designer 2 scope:** Store screenshots — {deliverables}
+- **Designer 3 scope:** Web page design — {deliverables} (if applicable)
+
+**TEAM EXCEPTION:** If task touches <3 files, output: "Files touched: {N} — below team threshold, single agents recommended."
+```
+
+Include concrete file assignments. The orchestrator will use this to create `TeamCreate` with the exact scopes you specify.
+
 ## Output Footer
 ```
-NEXT: product-manager(PRE) to validate approach before implementation
+NEXT: product-manager(PRE) to validate approach and team composition before implementation
 ```

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

@@ -4,16 +4,18 @@ description: "DevOps operations: Codemagic CI/CD builds, Firebase deployment, Cl
 model: opus
 hooks:
   PreToolUse:
-    - matcher: "Edit|Write"
-      hooks:
-        - type: command
-          command: "exit 0"
     - matcher: "Bash"
       hooks:
         - type: command
           command: "exit 0"
 ---
 
+**SCOPE RESTRICTION:**
+- You CANNOT edit or create ANY local project files (no Edit/Write tools)
+- This includes: source code, CI/CD configs, GitHub Actions workflows, scripts, codemagic.yaml, etc.
+- You CAN only: run deployments, check logs, monitor builds, manage infrastructure via Bash and MCP tools
+- If ANY local file changes are needed (code, configs, CI/CD, scripts), report what needs changing and ask the developer agent to make the edits
+
 # DevOps Agent
 
 Handles Codemagic CI/CD builds, Firebase deployment, Cloudflare Pages deployment, and Firestore management for Flutter mobile apps.
@@ -24,7 +26,7 @@ Handles Codemagic CI/CD builds, Firebase deployment, Cloudflare Pages deployment
 - `codemagic` - Build monitoring, deployment tracking, log analysis, build triggering
 - `firebase` - Deploy Cloud Functions, security rules, Firestore indexes
 - `cloudflare` - Deploy web pages via Cloudflare Pages
-- `database + migrate` - Firestore security rules updates, index management, data migration scripts
+- `database + deploy` - Deploy Firestore security rules, indexes, and run data migration scripts
 - `database + optimize` - Firestore query optimization, index analysis, security rules audit
 
 Additional parameters vary by mode (see each section).
@@ -283,38 +285,35 @@ RECOMMENDATION: [action if needed]
 
 ---
 
-## Mode: database + migrate
+## Mode: database + deploy
 
-Manage Firestore security rules, indexes, and data migration scripts. Firestore is NoSQL -- there are no SQL migrations.
+Deploy Firestore security rules, indexes, and run data migration scripts. Firestore is NoSQL -- there are no SQL migrations.
 
-### Security Rules Updates
+### Security Rules Deployment
 
-1. Read current rules in `firestore.rules`
-2. Read task file for new access requirements
-3. Update rules with proper authenticated read/write and per-document ownership checks
-4. Test rules locally: `firebase emulators:start --only firestore`
-5. Deploy: `firebase deploy --only firestore:rules`
+1. Deploy rules: `firebase deploy --only firestore:rules`
+2. Verify deployment succeeded in Firebase Console or CLI output
+3. Test rules against expected access patterns
 
-### Index Management
+### Index Deployment
 
-1. Review `firestore.indexes.json` for existing composite indexes
-2. Add new indexes for query patterns that require them
-3. Deploy: `firebase deploy --only firestore:indexes`
-4. Monitor index build status (can take minutes for large collections)
+1. Deploy indexes: `firebase deploy --only firestore:indexes`
+2. Monitor index build status (can take minutes for large collections)
+3. Verify all indexes reach READY state
 
-### Data Migration Scripts
+### Data Migration Execution
 
-For schema-like changes in Firestore documents:
-1. Write a migration script (Node.js) that reads and updates documents
-2. Run against local emulator first for testing
-3. Run against production with batched writes (max 500 per batch)
-4. Log progress and handle partial failures gracefully
+For running migration scripts (created by the developer agent):
+1. Run migration script against local emulator first: `firebase emulators:start --only firestore`
+2. Run against production with monitoring
+3. Verify data integrity after migration completes
+4. Log progress and report any failures
 
 ### Output
 
 ```
-OPERATION: Firestore Migration
-CHANGES: [list of rule/index/data changes]
+OPERATION: Firestore Deploy
+CHANGES: [list of deployed rules/indexes/migrations]
 EMULATOR TEST: Passed | Failed
 DEPLOYED: [rules | indexes | data migration]
 RESULT: Success | Failed
@@ -390,5 +389,5 @@ After editing `ci.config.yaml`, regenerate the Codemagic config:
 ## Output Footer
 
 ```
-NEXT: [context-dependent - for migrations: simplifier -> reviewer -> product-manager(POST)]
+NEXT: [context-dependent - for database deploy: verify deployment succeeded]
 ```

package/scripts/check_google_play.py

@@ -25,7 +25,7 @@ except ImportError:
     print("Installing dependencies...", file=sys.stderr)
     import subprocess
     subprocess.check_call(
-        [sys.executable, "-m", "pip", "install", "PyJWT", "cryptography", "requests"],
+        [sys.executable, "-m", "pip", "install", "--break-system-packages", "PyJWT", "cryptography", "requests"],
         stdout=subprocess.DEVNULL,
     )
     import jwt

package/scripts/manage_version_ios.py

@@ -32,7 +32,7 @@ except ImportError:
     print("Installing dependencies...", file=sys.stderr)
     import subprocess
     subprocess.check_call([
-        sys.executable, "-m", "pip", "install",
+        sys.executable, "-m", "pip", "install", "--break-system-packages",
         "PyJWT", "cryptography", "requests"
     ], stdout=subprocess.DEVNULL)
     import jwt

package/src/install-paths.mjs

@@ -2,7 +2,7 @@ import { execSync, execFileSync } from 'node:child_process';
 import { installGitHubActionsTemplates, installMatchfile } from './templates.mjs';
 import { findAppByRepo, addApp, normalizeRepoUrl } from './codemagic-api.mjs';
 import {
-  writeCiAppId, writeCiTeamId, writeMatchConfig, readFlutterRoot,
+  writeCiAppId, writeCiTeamId, writeMatchConfig,
 } from './ci-config.mjs';
 import { updateMcpAppId, updateMcpTeamId } from './mcp-setup.mjs';
 
@@ -68,8 +68,7 @@ export function installGitHubActionsPath(projectDir, packageDir, cliTokens) {
   console.log('Configuring GitHub Actions mode...');
   installGitHubActionsTemplates(projectDir, packageDir);
 
-  const flutterRoot = readFlutterRoot(projectDir);
-  installMatchfile(projectDir, packageDir, flutterRoot, {
+  installMatchfile(projectDir, packageDir, {
     matchGitUrl: cliTokens.matchGitUrl,
     bundleId: cliTokens.bundleId,
   });

package/src/templates.mjs

@@ -134,12 +134,12 @@ export function installGitHubActionsTemplates(projectDir, packageDir) {
   }
 }
 
-export function installMatchfile(projectDir, packageDir, flutterRoot, { matchGitUrl, bundleId }) {
+export function installMatchfile(projectDir, packageDir, { matchGitUrl, bundleId }) {
   console.log('Installing Matchfile...');
   const src = join(packageDir, 'templates', 'Matchfile.template');
   if (!existsSync(src)) return;
 
-  const destDir = join(projectDir, flutterRoot, 'ios', 'fastlane');
+  const destDir = join(projectDir, 'fastlane', 'ios');
   ensureDir(destDir);
   const dest = join(destDir, 'Matchfile');
 

package/templates/CLAUDE.md.template

@@ -14,7 +14,7 @@ This is a Flutter app with Firebase backend, automated for App Store and Google
 - If unsure which agent to use, use the Task tool with a general-purpose, explore or any other built-in agent
 
 ### DevOps Agent Required
-ALL deployment and infrastructure operations SHOULD use the devops agent (codemagic, firebase, cloudflare, database/migrate, database/optimize).
+ALL deployment and infrastructure operations SHOULD use the devops agent (codemagic, firebase, cloudflare, database/deploy, database/optimize).
 Prefer using the devops agent over direct Bash/SSH for structured operations.
 
 ### Code Quality (enforced by agents)
@@ -127,7 +127,7 @@ appstore-meta-creator → appstore-reviewer
 
 #### Database Flow
 ```
-devops(database,migrate) → simplifier → reviewer → product-manager(POST) → [devops(firebase)]
+architect → developer(backend) → simplifier → reviewer → product-manager(POST) → [devops(firebase)]
 ```
 
 #### Infra Flow
@@ -140,6 +140,39 @@ devops (standalone)
 architect → product-manager(PRE) → app-designer → developer(flutter) → simplifier → reviewer → tester(flutter) → tester(mobile-ui) → appstore-meta-creator → appstore-reviewer → product-manager(POST) → devops(codemagic)
 ```
 
+#### Team Size Annotations
+
+Flows above use single agents by default. For tasks touching 3+ files, apply team sizes:
+
+| Files Touched | Team Size |
+|--------------|-----------|
+| 1-2 files | Single agent (no team) |
+| 3-4 files | 2 teammates |
+| 5-7 files | 3 teammates |
+| 8+ files | 4 teammates |
+
+**Team-annotated flows** (apply when task scope exceeds 2 files):
+
+##### Standard Flow (with teams)
+```
+architect{T:2} → product-manager(PRE) → developer{T:2-4} → simplifier → reviewer{T:2} → tester{T:2} → product-manager(POST) → [devops]
+```
+
+##### Flutter Flow (with teams)
+```
+architect{T:2} → product-manager(PRE) → [app-designer{T:2-3}] → developer(flutter){T:2-4} → simplifier → reviewer{T:2-3} → tester(flutter){T:2} → tester(mobile-ui){T:2} → product-manager(POST) → [devops(codemagic)]
+```
+
+##### Backend Flow (with teams)
+```
+architect{T:2} → product-manager(PRE) → developer(backend){T:2-4} → simplifier → reviewer{T:2} → tester(backend){T:2} → product-manager(POST) → [devops(firebase)]
+```
+
+##### Full Publishing Flow (with teams)
+```
+architect{T:2} → product-manager(PRE) → app-designer{T:2-3} → developer(flutter){T:2-4} → simplifier → reviewer{T:2-3} → tester(flutter){T:2} → tester(mobile-ui){T:2} → appstore-meta-creator{T:2-5} → appstore-reviewer → product-manager(POST) → devops(codemagic)
+```
+
 ### Agents Reference
 
 | Agent | When to use |
@@ -150,7 +183,7 @@ architect → product-manager(PRE) → app-designer → developer(flutter) → s
 | simplifier | AFTER developer - simplifies Dart/Flutter code |
 | reviewer | After ANY code changes - Dart/Flutter quality review |
 | tester | After review passes (type: flutter/mobile-ui/web/backend/integration) |
-| devops | Operations (mode: codemagic/firebase/cloudflare/database+migrate/database+optimize) |
+| devops | Operations (mode: codemagic/firebase/cloudflare/database+deploy/database+optimize) |
 | app-designer | Stitch MCP design: app screens + store screenshots + web page design |
 | appstore-meta-creator | Generate store listing texts for all configured languages |
 | appstore-reviewer | Full App Store/Play compliance review including live app UI testing via mobile-mcp |
@@ -240,21 +273,42 @@ Push to main. Codemagic detects changes and uploads modified assets. Version aut
 **If you are a TEAMMATE, skip to "For Teammates" section below.**
 ---
 
-### Agent Teams (Evaluate per stage)
+### Agent Teams (MANDATORY by default)
+
+**Teams are the DEFAULT for most workflow stages.** Single-agent is the exception, not the norm.
+
+#### Mandatory Team Stages
+
+These stages MUST use teams unless the task touches fewer than 3 files:
+
+| Stage | Default Size | Split Strategy |
+|-------|-------------|----------------|
+| architect | 2 | Split by concern: structure/patterns vs integration/data-flow |
+| developer | 2-4 | Split by file group: screens/widgets vs providers/repos vs Firebase/backend |
+| reviewer | 2-3 | Split by focus: Dart quality vs security+Firebase rules vs performance+store compliance |
+| tester | 2-4 | Split by type: flutter unit/widget vs mobile-ui iOS vs mobile-ui Android vs web |
+| app-designer | 2-3 | Split by deliverable: app screens vs store screenshots vs web page |
+| appstore-meta-creator | 2-5 | Split by language group: each teammate handles 2-5 languages grouped by similarity |
+
+#### Single-Agent Stages (exceptions)
 
-**You MUST evaluate team suitability for EACH workflow stage and print your decision in the output format.**
+These stages stay single-agent — teams add no value:
 
-Evaluate each stage independently — a task may use single agents for some stages and teams for others.
+| Stage | Reason |
+|-------|--------|
+| simplifier | Works on same files developer just touched — no parallelism possible |
+| product-manager | Single evaluation checkpoint — multiple perspectives don't help |
+| devops | Single deployment target — cannot parallelize |
+| appstore-reviewer | Single compliance evaluation — one holistic review needed |
 
-**Use team for a stage when:**
-- Multiple perspectives improve quality
-- Competing approaches find better solutions
-- Stage work splits into independent file groups
+#### Team Size Triggers
 
-**Use single agent for a stage when:**
-- Work touches the same files
-- Stage is a single focused operation
-- Adding perspectives adds no value
+| Files Touched | Team Size |
+|--------------|-----------|
+| 1-2 files | Single agent — TEAM EXCEPTION |
+| 3-4 files | 2 teammates |
+| 5-7 files | 3 teammates |
+| 8+ files | 4 teammates |
 
 **Team Enforcement (MANDATORY):**
 If `TEAMS:` output includes any stage using teams, you MUST call `TeamCreate` before spawning agents for that stage. Spawning agents via `Task` without `team_name` does NOT count as using teams. Violation = workflow non-compliance.
@@ -324,7 +378,7 @@ TASK TYPE: [flutter/backend/design/metadata/database/infra/standard]
 RECOMMENDED FLOW:
 <copy the EXACT flow from Agent Flows section - include ALL agents with [optional] ones>
 
-TEAMS: [per-stage evaluation: which stages use teams and why, or NO if all stages use single agents]
+TEAMS: [MANDATORY — list team stages with sizes. Single-agent exceptions: list which stages and why. "NO" only valid for tasks <3 files]
 
 DEPLOYMENT: [AVAILABLE - deployment configured | NOT CONFIGURED - workflow ends at product-manager(POST)]
 
@@ -342,7 +396,7 @@ LAUNCHING: [first-agent-name]
 - **backend**: `architect → product-manager(PRE) → developer(backend) → simplifier → reviewer → tester(backend) → product-manager(POST) → [devops(firebase)]`
 - **design**: `app-designer → appstore-reviewer`
 - **metadata**: `appstore-meta-creator → appstore-reviewer`
-- **database**: `devops(database,migrate) → simplifier → reviewer → product-manager(POST) → [devops(firebase)]`
+- **database**: `architect → developer(backend) → simplifier → reviewer → product-manager(POST) → [devops(firebase)]`
 - **infra**: `devops (standalone)`
 - **standard**: `architect → product-manager(PRE) → developer → simplifier → reviewer → tester → product-manager(POST) → [devops]`