flight-rules 0.13.2 → 0.13.4

package/dist/commands/ralph.js

@@ -136,6 +136,10 @@ async function runClaudeWithPrompt(promptContent, verbose) {
                         else if (parsed.type === 'content_block_delta' && parsed.delta?.text) {
                             process.stdout.write(parsed.delta.text);
                         }
+                        else if (parsed.type === 'content_block_stop') {
+                            // Add newline after each content block ends
+                            process.stdout.write('\n');
+                        }
                     }
                     catch {
                         // Not valid JSON or incomplete line, skip

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flight-rules",
-  "version": "0.13.2",
+  "version": "0.13.4",
   "description": "An opinionated framework for AI-assisted software development",
   "type": "module",
   "main": "dist/index.js",

package/payload/AGENTS.md

@@ -1,6 +1,6 @@
 # Flight Rules – Agent Guidelines
 
-flight_rules_version: 0.13.2
+flight_rules_version: 0.13.4
 
 This file defines how agents (Claude Code, Cursor, etc.) should work on software projects using the Flight Rules system.
 

package/payload/prompts/ralph-loop.md

@@ -11,9 +11,11 @@ You are an autonomous coding agent implementing Flight Rules task groups.
    - If ALL tasks across ALL task groups are ✅ Complete, proceed to step 2
    - Otherwise, proceed to step 3
 
-2. **If All Complete**
+2. **If ALL Tasks in ALL Task Groups Are Complete**
+   - ONLY output the completion signal when you have verified that EVERY task in EVERY task group is ✅ Complete
    - Output exactly: `<ralph-signal>COMPLETE</ralph-signal>`
    - Stop immediately - do not output anything else after this
+   - **IMPORTANT**: Do NOT output this signal just because the current task group is done. The loop will automatically continue to the next iteration.
 
 3. **If Task Group Found**
    - Read the Task Group file completely
@@ -33,6 +35,7 @@ You are an autonomous coding agent implementing Flight Rules task groups.
      git add -A
      git commit -m "feat: [Task Group ID] - [Task Group Title]"
      ```
+   - **STOP HERE** - Do NOT output the completion signal. The loop will automatically start the next iteration to find more task groups.
 
 5. **Quality Checks (Run Before Every Commit)**
    First, read `package.json` to discover available scripts. Then run the relevant ones:
@@ -84,11 +87,13 @@ Create verbose logs for each Ralph session. After completing a task group (or wh
 ## Rules
 
 - Work on ONE task group per iteration
+- NEVER output the COMPLETE signal unless ALL tasks in ALL task groups are ✅ Complete
 - NEVER ask for human input - work autonomously
 - NEVER skip quality checks
 - If blocked after 3 attempts on the same issue, document it and move on
 - Commit after completing each task group, not after each individual task
 - Keep commits atomic and CI-friendly
+- After committing a task group, just STOP - the loop will automatically continue
 
 ## Status Legend