@kraftapps-ai/kai 1.8.3 → 1.8.6

package/kai

@@ -227,6 +227,9 @@ PRD_FILE=".kai/stories.json"
 PROGRESS_FILE=".kai/progress.txt"
 LOOP_MCP_ARGS="--mcp-config .kai/loop-mcp.json"
 
+# Cap Node.js memory to prevent test runners from consuming all RAM
+export NODE_OPTIONS="--max-old-space-size=2048"
+
 # Stream output live when running in a tmux pane
 KAI_STREAM=false
 if [ -n "${TMUX:-}" ]; then
@@ -265,11 +268,15 @@ You are an expert Shopify developer. You have access to the Shopify Dev MCP tool
 2. Read .kai/progress.txt for context on previous work.
 3. **PLAN before coding.** List files and changes before touching code.
 4. If the story involves Shopify APIs, call `learn_shopify_api` then use `introspect_graphql_schema` and `search_docs_chunks` to understand the right approach.
-5. **WRITE FAILING TESTS FIRST.** For each acceptance criterion, write a test that verifies it. Run the tests — they MUST fail (red). If a test already passes, your test is not testing the right thing.
-6. **Implement ONLY enough code to make the tests pass (green).** No more, no less.
+5. **WRITE FAILING TESTS FIRST.** For each acceptance criterion, write a test that verifies it. Run ONLY the relevant test file(s) — they MUST fail (red). If a test already passes, your test is not testing the right thing.
+6. **Implement ONLY enough code to make the tests pass (green).** No more, no less. Run only the relevant test file(s) to verify.
 7. **Refactor** if needed — clean up while keeping tests green.
-8. Validate: run full test suite, validate GraphQL with `validate_graphql_codeblocks`, validate Liquid with `validate_theme_codeblocks`.
+8. **Final validation ONCE:** Run the full test suite ONE TIME at the end. Also validate GraphQL with `validate_graphql_codeblocks`, validate Liquid with `validate_theme_codeblocks`.
 9. **SELF-REVIEW.** For each acceptance criterion, cite the test that covers it AND evidence it passes (file, line, command output). No "should work" or "probably".
+
+## IMPORTANT: Resource management
+- **NEVER run the full test suite repeatedly.** Run targeted tests during development (e.g., `npx vitest run path/to/test.ts`). Only run the full suite ONCE as a final check before committing.
+- **Always use `npx vitest run`** (not `npx vitest` without `run`) — watch mode will hang forever.
 10. Commit with a descriptive message.
 11. Update .kai/stories.json: set `passes` to `true`.
 12. Append to .kai/progress.txt.
@@ -278,7 +285,7 @@ You are an expert Shopify developer. You have access to the Shopify Dev MCP tool
 - ONE STORY PER LOOP.
 - **TDD is mandatory.** Tests first, then implementation. No exceptions.
 - No placeholders. Fully implement or report BLOCKED.
-- Do not break existing functionality. Run the FULL test suite, not just your new tests.
+- Do not break existing functionality. Run the full test suite ONCE at the end as a final check.
 - ALWAYS validate GraphQL and Liquid code using the MCP tools before marking complete.
 - If ALL stories have `passes: true`, output: <promise>COMPLETE</promise>
 
@@ -331,25 +338,51 @@ while :; do
 
     start_time=$(date +%s)
 
+    # Run worker in background with heartbeat monitor
     set +e
-    if [ "$KAI_STREAM" = true ]; then
-        claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS --system-prompt "$WORKER_PROMPT" $context_files 2>&1 | tee .kai/worker-output.tmp
-        exit_code=${PIPESTATUS[0]}
-        result=$(cat .kai/worker-output.tmp)
-    else
-        result=$(claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS --system-prompt "$WORKER_PROMPT" $context_files)
-        exit_code=$?
-        echo "$result" | tail -20
-    fi
+    touch .kai/worker-heartbeat
+    claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS --system-prompt "$WORKER_PROMPT" $context_files > .kai/worker-output.tmp 2>&1 &
+    worker_pid=$!
+
+    echo "  Worker started (PID $worker_pid)"
+    while kill -0 $worker_pid 2>/dev/null; do
+        sleep 30
+        elapsed_now=$(( $(date +%s) - start_time ))
+        mins=$((elapsed_now / 60))
+        secs=$((elapsed_now % 60))
+
+        # Detect what's running
+        activity=""
+        pgrep -f "vitest" > /dev/null 2>&1 && activity="running tests"
+        pgrep -f "esbuild" > /dev/null 2>&1 && activity="${activity:+$activity + }building"
+        pgrep -f "npm run build" > /dev/null 2>&1 && activity="${activity:+$activity + }building"
+        [ -z "$activity" ] && activity="thinking"
+
+        # Show recently changed files
+        changed=$(find . \( -name '*.ts' -o -name '*.tsx' -o -name '*.php' -o -name '*.less' -o -name '*.css' -o -name '*.json' \) \
+            -not -path './node_modules/*' -not -path './.kai/*' -not -path './vendor/*' \
+            -newer .kai/worker-heartbeat -printf '%f\n' 2>/dev/null | sort -u | head -5 | tr '\n' ', ')
+
+        echo "  [${mins}m${secs}s] ${activity}${changed:+ | files: ${changed%,}}"
+        touch .kai/worker-heartbeat
+    done
+
+    wait $worker_pid
+    exit_code=$?
+    result=$(cat .kai/worker-output.tmp)
     set -e
 
     elapsed=$(( $(date +%s) - start_time ))
 
     if [ $exit_code -ne 0 ]; then
-        echo "Failed (code ${exit_code}). Restarting..."
+        echo "  Worker failed (code ${exit_code}). Last output:"
+        echo "$result" | tail -10
+        echo "  Restarting..."
         continue
     fi
 
+    echo "$result" | tail -20
+
     if [[ "$result" == *"<promise>COMPLETE</promise>"* ]]; then
         echo "All stories complete after $iteration iterations!"
         exit 0
@@ -358,6 +391,7 @@ while :; do
     # Review
     STORY_PASSES=$(jq -r --arg id "$NEXT_ID" '.userStories[] | select(.id == $id) | .passes' "$PRD_FILE")
     if [ "$STORY_PASSES" = "true" ]; then
+        echo "  Reviewing story #${NEXT_ID}..."
         last_commit=$(git log --oneline -1 2>/dev/null || echo "no git")
         ACCEPTANCE=$(jq -r --arg id "$NEXT_ID" '.userStories[] | select(.id == $id) | .acceptanceCriteria | join("\n- ")' "$PRD_FILE")
 
@@ -372,15 +406,21 @@ If ANY fails: REVIEW_FAIL: [reason]
 If all pass: REVIEW_PASS"
 
         set +e
-        if [ "$KAI_STREAM" = true ]; then
-            claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS "$REVIEW_PROMPT" 2>&1 | tee .kai/review-output.tmp
-            review=$(cat .kai/review-output.tmp)
-        else
-            review=$(claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS "$REVIEW_PROMPT")
-            echo "$review" | tail -5
-        fi
+        claude -p --dangerously-skip-permissions $LOOP_MCP_ARGS "$REVIEW_PROMPT" > .kai/review-output.tmp 2>&1 &
+        review_pid=$!
+
+        while kill -0 $review_pid 2>/dev/null; do
+            sleep 15
+            elapsed_now=$(( $(date +%s) - start_time ))
+            echo "  [${elapsed_now}s] reviewing..."
+        done
+
+        wait $review_pid
+        review=$(cat .kai/review-output.tmp)
         set -e
 
+        echo "$review" | tail -5
+
         if [[ "$review" == *"REVIEW_FAIL"* ]]; then
             jq --arg id "$NEXT_ID" '(.userStories[] | select(.id == $id)).passes = false' "$PRD_FILE" > "${PRD_FILE}.tmp" && mv "${PRD_FILE}.tmp" "$PRD_FILE"
             echo "REVIEW FEEDBACK: $review" >> "$PROGRESS_FILE"
@@ -452,12 +492,16 @@ The developer's name is: ${dev_name}"
 
 # ── Build loop run instructions for PM ────────────────
 
+LOOP_MONITOR="After starting the loop, IMMEDIATELY run \`/loop 5m\` with a prompt that reads .kai/stories.json and .kai/progress.txt to check progress, then report a brief status update to the developer (e.g., \"Story #X complete, working on #Y, 3 remaining\"). Stop the /loop when all stories are done or the loop has stopped."
+
 if [ "$KAI_TMUX" = true ] || [ -n "${TMUX:-}" ]; then
     LOOP_INSTRUCTIONS="To run implementation, execute: \`tmux send-keys -t ${KAI_TMUX_SESSION}:0.1 '.kai/loop.sh 2>&1 | tee .kai/loop.log' Enter\`
 The dev loop output streams live in the right tmux pane. You can also check \`tail -f .kai/loop.log\`.
-To stop the loop: \`tmux send-keys -t ${KAI_TMUX_SESSION}:0.1 C-c\`"
+To stop the loop: \`tmux send-keys -t ${KAI_TMUX_SESSION}:0.1 C-c\`
+${LOOP_MONITOR}"
 else
-    LOOP_INSTRUCTIONS="To run implementation, execute: \`nohup .kai/loop.sh > .kai/loop.log 2>&1 &\` then monitor with \`tail -f .kai/loop.log\`"
+    LOOP_INSTRUCTIONS="To run implementation, execute: \`nohup .kai/loop.sh > .kai/loop.log 2>&1 &\` then monitor with \`tail -f .kai/loop.log\`
+${LOOP_MONITOR}"
 fi
 
 # ── Build Claude args ─────────────────────────────────

package/package.json

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