@kraftapps-ai/kai 1.5.4 → 1.6.2

package/kai

@@ -17,7 +17,6 @@ fi
 
 PRD_FILE=".kai/stories.json"
 PROGRESS_FILE=".kai/progress.txt"
-PROMPT_FILE=".kai/PROMPT.md"
 MEMORY_FILE=".kai/memory.md"
 SESSION_FILE=".kai/session_id"
 LOOP_SCRIPT=".kai/loop.sh"
@@ -61,36 +60,6 @@ if [ ! -f "$PRD_FILE" ]; then
 EOF
 
     echo "# Kai Progress Log" > "$PROGRESS_FILE"
-
-    cat > "$PROMPT_FILE" << 'EOF'
-# Project Context
-
-Add your project-specific context here. The more you provide, the better Kai performs.
-
-## Shopify Store
-<!-- Kai auto-detects store info from shopify.app.toml and .env -->
-<!-- Only fill this in if auto-detection doesn't work for your setup -->
-<!-- Store domain: your-store.myshopify.com -->
-<!-- App handle: your-app-handle -->
-
-## Tech stack
-<!-- e.g., Remix + TypeScript, Next.js, Ruby on Rails -->
-
-## Build command
-<!-- e.g., npm run build, shopify app build -->
-
-## Test command
-<!-- e.g., npm test, shopify app test -->
-
-## Dev command
-<!-- e.g., npm run dev, shopify app dev -->
-
-## Project structure
-<!-- Key directories and files -->
-
-## Conventions
-<!-- Coding style, naming, patterns -->
-EOF
 fi
 
 # Init memory file if it doesn't exist
@@ -121,6 +90,7 @@ fi
 # Track what's already configured
 playwright_available=false
 shopify_dev_available=false
+mantle_available=false
 
 for config in \
     ".mcp.json" \
@@ -130,6 +100,7 @@ for config in \
     if [ -f "$config" ]; then
         grep -q "playwright" "$config" 2>/dev/null && playwright_available=true
         grep -q "shopify-dev" "$config" 2>/dev/null && shopify_dev_available=true
+        grep -q "mantle" "$config" 2>/dev/null && mantle_available=true
     fi
 done
 
@@ -145,7 +116,7 @@ fi
 
 # Build MCP config with all needed servers
 needs_mcp_update=false
-if [ "$playwright_available" = false ] || [ "$shopify_dev_available" = false ]; then
+if [ "$playwright_available" = false ] || [ "$shopify_dev_available" = false ] || [ "$mantle_available" = false ]; then
     needs_mcp_update=true
 fi
 
@@ -164,11 +135,18 @@ if [ "$needs_mcp_update" = true ]; then
             mcp_config=$(echo "$mcp_config" | jq '.mcpServers["shopify-dev-mcp"] = {"command": "npx", "args": ["-y", "@shopify/dev-mcp@latest"]}')
         fi
 
+        if [ "$mantle_available" = false ] && ! echo "$mcp_config" | grep -q "mantle"; then
+            echo "Setting up Mantle MCP (billing, subscriptions, analytics)..."
+            mcp_config=$(echo "$mcp_config" | jq '.mcpServers["mantle-foundations"] = {"url": "https://mcp.heymantle.com/foundations"}')
+            mcp_config=$(echo "$mcp_config" | jq '.mcpServers["mantle-core"] = {"url": "https://mcp.heymantle.com/core"}')
+        fi
+
         echo "$mcp_config" > .mcp.json
     else
         echo "Setting up MCP servers..."
         echo "  - Playwright (browser testing)"
         echo "  - Shopify Dev MCP (docs, GraphQL schemas, Liquid validation)"
+        echo "  - Mantle MCP (billing, subscriptions, analytics)"
 
         cat > .mcp.json << 'MCPEOF'
 {
@@ -180,6 +158,12 @@ if [ "$needs_mcp_update" = true ]; then
     "shopify-dev-mcp": {
       "command": "npx",
       "args": ["-y", "@shopify/dev-mcp@latest"]
+    },
+    "mantle-foundations": {
+      "url": "https://mcp.heymantle.com/foundations"
+    },
+    "mantle-core": {
+      "url": "https://mcp.heymantle.com/core"
     }
   }
 }
@@ -197,7 +181,6 @@ set -e
 
 PRD_FILE=".kai/stories.json"
 PROGRESS_FILE=".kai/progress.txt"
-PROMPT_FILE=".kai/PROMPT.md"
 
 WORKER_PROMPT='You are an autonomous AI developer specializing in Shopify app and theme development.
 
@@ -255,7 +238,7 @@ You are an expert Shopify developer. You have access to the Shopify Dev MCP tool
 | "Skip review" | Simple code has bugs. | Always self-review. |
 | "I know the API" | APIs change. Schema is truth. | Introspect first. |'
 
-context_files="@${PROMPT_FILE} @${PRD_FILE} @${PROGRESS_FILE}"
+context_files="@${PRD_FILE} @${PROGRESS_FILE}"
 if [ -f ".kai/context.txt" ]; then
     while IFS= read -r file; do
         [ -n "$file" ] && [ -f "$file" ] && context_files="$context_files @${file}"
@@ -357,23 +340,25 @@ $(jq -r '.userStories[] | "- [\(if .passes then "DONE" else "TODO" end)] #\(.id)
     fi
 fi
 
-project_context=""
-[ -f "$PROMPT_FILE" ] && project_context="
-
-Project context (.kai/PROMPT.md):
-$(cat "$PROMPT_FILE")"
-
 progress=""
-[ -f "$PROGRESS_FILE" ] && [ "$(wc -l < "$PROGRESS_FILE")" -gt 2 ] && progress="
+if [ -f "$PROGRESS_FILE" ] && [ "$(wc -l < "$PROGRESS_FILE")" -gt 2 ]; then
+    progress="
 
 Recent progress (.kai/progress.txt):
-$(tail -30 "$PROGRESS_FILE")"
+$(tail -15 "$PROGRESS_FILE")"
+fi
 
+# Only inject memory if it has real content (not just the default template)
 memory=""
-[ -f "$MEMORY_FILE" ] && memory="
+if [ -f "$MEMORY_FILE" ]; then
+    stripped_mem=$(sed 's/<!--.*-->//g' "$MEMORY_FILE" | sed '/^$/N;/^\n$/d')
+    if echo "$stripped_mem" | grep -qvE '^(#|$)'; then
+        memory="
 
 ## Kai Memory (from previous sessions)
 $(cat "$MEMORY_FILE")"
+    fi
+fi
 
 dev_name=$(git config user.name 2>/dev/null || echo "")
 dev_greeting=""
@@ -392,18 +377,18 @@ else
     mkdir -p .kai
     echo "$KAI_SESSION" > "$SESSION_FILE"
 fi
-CLAUDE_ARGS="$CLAUDE_ARGS --session-id $KAI_SESSION --name kai"
+CLAUDE_ARGS="$CLAUDE_ARGS --name kai"
 
 # ── Launch the PM ─────────────────────────────────────
 
-exec claude $CLAUDE_ARGS --system-prompt "You are Kai — an AI product manager, tech lead, and **Shopify expert**. You work directly with the developer to plan and ship Shopify apps, themes, and integrations.
+SYSTEM_PROMPT="You are Kai — an AI product manager, tech lead, and **Shopify expert**. You work directly with the developer to plan and ship Shopify apps, themes, and integrations.
 
 ## Session persistence
 
 You maintain a memory file at \`.kai/memory.md\` that preserves context between sessions. This is critical — it's how you remember what happened in previous conversations.
 
 ### Reading memory
-- **All context is already loaded in this system prompt** — story status, project context, progress log, and memory are all below. Do NOT read files on startup.
+- **All context is already loaded in this system prompt** — story status, progress log, and memory are all below. Do NOT read files on startup.
 - Use the loaded memory to greet the developer with instant awareness of where you left off
 - If memory has content, reference it naturally: \"Hey {name} — picking up where we left off on X\"
 
@@ -452,7 +437,15 @@ Every Shopify store exposes a Storefront MCP endpoint at \`https://{shop}.myshop
 - **search_shop_policies_and_faqs** — Query store policies, shipping, returns
 - **get_cart** / **update_cart** — Manage shopping carts
 
-If the developer's store domain is in \`.kai/PROMPT.md\`, you can point them to this endpoint for storefront integrations.
+If the developer's store domain is in memory, you can point them to this endpoint for storefront integrations.
+
+### Mantle MCP (billing & analytics)
+You have access to Mantle MCP servers for Shopify app billing and analytics:
+
+- **mantle-foundations** — Code generation for Mantle integration: billing UI, customer identification, usage event tracking, feature gating, plan/feature/entitlement configuration. Use this when implementing or modifying billing, subscriptions, or paywalls.
+- **mantle-core** — Customer analytics, subscription details, revenue metrics (50+ metrics including churn, retention, MRR), sales CRM, transaction history. Use this to look up customer data, analyze revenue, or check subscription status.
+
+OAuth authentication happens automatically via browser on first use — no API keys needed.
 
 ### Your Shopify knowledge includes
 - **App development**: Remix apps, App Bridge, session tokens, OAuth, webhooks, GDPR compliance, app extensions
@@ -463,6 +456,7 @@ If the developer's store domain is in \`.kai/PROMPT.md\`, you can point them to
 - **Polaris**: Shopify's design system and React components for app UIs
 - **App extensions**: Theme app extensions, checkout UI extensions, admin UI extensions, Shopify Functions
 - **Hydrogen & Oxygen**: Shopify's headless framework and hosting
+- **Mantle**: App billing, subscriptions, usage-based pricing, feature gating, customer analytics via Mantle MCP
 
 ## What you can do
 
@@ -498,26 +492,27 @@ When the developer asks you to test or QA the app, proactively navigate to every
 
 ### Navigating to the Shopify app
 
-**NEVER guess the app URL. Auto-detect it from the repo.**
+**NEVER guess the app URL. NEVER make up a store name.**
+
+Shopify apps are **embedded inside Shopify Admin**. Pages are NOT directly accessible at localhost. You need TWO pieces of info to build the URL:
+
+1. **Store name** — the subdomain from \`{store-name}.myshopify.com\`
+2. **App handle** — the app's URL slug from \`shopify.app.toml\` \`handle\` field
+
+**IMPORTANT: Store name and app handle are DIFFERENT things. Do not use one for the other.**
 
-Shopify apps are **embedded inside Shopify Admin**. Pages are NOT directly accessible at localhost. Before navigating, you MUST read the repo config files to build the correct URL:
+To find these, read the repo config files:
+- **\`shopify.app.toml\`** (or \`shopify.app.*.toml\`):
+  - \`handle\` → the app handle (for \`/apps/{handle}\`)
+  - \`[build] dev_store_url\` → the store domain (e.g., \`my-store.myshopify.com\` → store name is \`my-store\`)
+- **\`.env\`**:
+  - \`SHOP\` → the store domain (e.g., \`my-store.myshopify.com\` → store name is \`my-store\`)
 
-1. **Read \`shopify.app.toml\`** (or \`shopify.app.*.toml\`) to get:
-   - \`handle\` — the app's URL slug (used in \`/apps/{handle}\`)
-   - \`[build] dev_store_url\` — the dev store domain (e.g., \`my-store.myshopify.com\`)
-   - \`application_url\` — the app's hosted URL
-   - \`name\`, \`client_id\` — app identity
-2. **If not in TOML, check \`.env\`** for:
-   - \`SHOP\` — store domain
-   - \`SHOPIFY_API_KEY\` — app API key
-   - \`HOST\` — app host URL
-3. **Build the Admin URL**: \`https://admin.shopify.com/store/{STORE_NAME}/apps/{HANDLE}/{PAGE}\`
-   - Extract STORE_NAME from \`dev_store_url\` (strip \`.myshopify.com\`)
-   - Use \`handle\` from the TOML
-4. When the developer says \"check /designs\", translate that to \`https://admin.shopify.com/store/STORE/apps/APP/designs\`
-5. For theme previews, use the store's preview URL, not localhost
+Then build: \`https://admin.shopify.com/store/{STORE_NAME}/apps/{HANDLE}/{PAGE}\`
 
-**Do NOT ask the developer for store info if it can be found in these files. Only ask as a last resort if none of the config files exist.**
+**If \`dev_store_url\` is NOT in the TOML and \`SHOP\` is NOT in .env, you MUST ask the developer for their store name. Do NOT guess or infer it from the app name, handle, or any other field.**
+
+When the developer says \"check /designs\", translate that to the full URL using the store name + app handle you found.
 
 ## Rules for good stories
 - Each story: independently committable, 5-15 min of work
@@ -536,4 +531,22 @@ Shopify apps are **embedded inside Shopify Admin**. Pages are NOT directly acces
 - When unsure about an API, introspect the schema instead of guessing
 - **On startup with existing memory (returning session):** All context is already loaded below. DO NOT read files. Greet the developer by name immediately with awareness of where you left off. Be instant — no tool calls before your first response. Keep it to 2-3 lines.
 - **On startup without memory (fresh start):** Explore the repo first to understand the project. Read \`package.json\`, \`shopify.app.toml\` (or \`shopify.app.*.toml\`), scan the directory structure, check the README, and any other key files. Then greet the developer with a summary of what you found: the app name, what it does, tech stack, Shopify APIs used, etc. Save this to \`.kai/memory.md\` so you remember next time. Then ask what they want to plan or build. This first greeting should feel like a knowledgeable colleague who just reviewed the codebase.
-${status}${project_context}${progress}${memory}${dev_greeting}" "${@:-Hey Kai}"
+${status}${progress}${memory}${dev_greeting}"
+
+err_file=$(mktemp)
+set +e
+claude --session-id "$KAI_SESSION" $CLAUDE_ARGS --system-prompt "$SYSTEM_PROMPT" "${@:-Hey Kai}" 2>"$err_file"
+exit_code=$?
+set -e
+
+if [ $exit_code -ne 0 ] && grep -qi "already in use" "$err_file" 2>/dev/null; then
+    rm -f "$err_file"
+    echo ""
+    echo "Kai is already running in another terminal."
+    echo ""
+    echo "  1) Start a new session here:  kai --new"
+    echo "  2) Continue in the other terminal where Kai is running"
+    echo ""
+    exit 1
+fi
+rm -f "$err_file"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kraftapps-ai/kai",
-  "version": "1.5.4",
+  "version": "1.6.2",
   "description": "Autonomous AI developer loop for Claude Code",
   "bin": {
     "kai": "kai"