bmalph 2.7.2 → 2.7.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (46) hide show
  1. package/README.md +14 -4
  2. package/dist/commands/doctor-checks.js +17 -10
  3. package/dist/commands/doctor-checks.js.map +1 -1
  4. package/dist/run/ralph-process.js +101 -7
  5. package/dist/run/ralph-process.js.map +1 -1
  6. package/dist/transition/artifact-collection.js +74 -0
  7. package/dist/transition/artifact-collection.js.map +1 -0
  8. package/dist/transition/artifacts.js +12 -1
  9. package/dist/transition/artifacts.js.map +1 -1
  10. package/dist/transition/context.js +17 -25
  11. package/dist/transition/context.js.map +1 -1
  12. package/dist/transition/fix-plan.js +12 -7
  13. package/dist/transition/fix-plan.js.map +1 -1
  14. package/dist/transition/orchestration.js +213 -116
  15. package/dist/transition/orchestration.js.map +1 -1
  16. package/dist/transition/preflight.js +30 -17
  17. package/dist/transition/preflight.js.map +1 -1
  18. package/dist/transition/section-patterns.js +56 -4
  19. package/dist/transition/section-patterns.js.map +1 -1
  20. package/dist/transition/specs-index.js +5 -2
  21. package/dist/transition/specs-index.js.map +1 -1
  22. package/dist/transition/specs-sync.js +23 -0
  23. package/dist/transition/specs-sync.js.map +1 -0
  24. package/dist/transition/sprint-status.js +91 -0
  25. package/dist/transition/sprint-status.js.map +1 -0
  26. package/dist/transition/story-id.js +46 -0
  27. package/dist/transition/story-id.js.map +1 -0
  28. package/dist/transition/story-parsing.js +7 -7
  29. package/dist/transition/story-parsing.js.map +1 -1
  30. package/dist/transition/tech-stack.js +1 -7
  31. package/dist/transition/tech-stack.js.map +1 -1
  32. package/package.json +1 -1
  33. package/ralph/RALPH-REFERENCE.md +50 -46
  34. package/ralph/drivers/claude-code.sh +44 -2
  35. package/ralph/drivers/codex.sh +10 -1
  36. package/ralph/drivers/copilot.sh +5 -0
  37. package/ralph/drivers/cursor-agent-wrapper.sh +13 -0
  38. package/ralph/drivers/cursor.sh +178 -14
  39. package/ralph/lib/circuit_breaker.sh +5 -5
  40. package/ralph/lib/enable_core.sh +10 -10
  41. package/ralph/lib/response_analyzer.sh +357 -111
  42. package/ralph/ralph_import.sh +14 -10
  43. package/ralph/ralph_loop.sh +168 -119
  44. package/ralph/ralph_monitor.sh +4 -4
  45. package/ralph/templates/AGENT.md +7 -7
  46. package/ralph/templates/PROMPT.md +13 -13
@@ -2,8 +2,8 @@
2
2
 
3
3
  # Ralph Status Monitor - Live terminal dashboard for the Ralph loop
4
4
  #
5
- # DEPRECATED: Use `bmalph watch` instead, which provides a more capable
6
- # TypeScript-based live dashboard with full test coverage.
5
+ # DEPRECATED: Use `bmalph run` instead, which starts Ralph and shows the
6
+ # supported live dashboard.
7
7
  # This script is kept for backward compatibility in tmux sessions.
8
8
  set -e
9
9
 
@@ -77,7 +77,7 @@ display_status() {
77
77
  echo
78
78
  fi
79
79
 
80
- # Claude Code Progress section
80
+ # Driver Progress section
81
81
  if [[ -f ".ralph/progress.json" ]]; then
82
82
  local progress_data=$(cat ".ralph/progress.json" 2>/dev/null)
83
83
  local progress_status=$(echo "$progress_data" | jq -r '.status // "idle"' 2>/dev/null || echo "idle")
@@ -87,7 +87,7 @@ display_status() {
87
87
  local elapsed=$(echo "$progress_data" | jq -r '.elapsed_seconds // "0"' 2>/dev/null || echo "0")
88
88
  local last_output=$(echo "$progress_data" | jq -r '.last_output // ""' 2>/dev/null || echo "")
89
89
 
90
- echo -e "${YELLOW}┌─ Claude Code Progress ──────────────────────────────────────────────────┐${NC}"
90
+ echo -e "${YELLOW}┌─ Driver Progress ───────────────────────────────────────────────────────┐${NC}"
91
91
  echo -e "${YELLOW}│${NC} Status: ${indicator} Working (${elapsed}s elapsed)"
92
92
  if [[ -n "$last_output" && "$last_output" != "" ]]; then
93
93
  # Truncate long output for display
@@ -94,8 +94,8 @@ Before moving to the next feature, ALL changes must be:
94
94
  - Create pull requests for all significant changes
95
95
 
96
96
  4. **Ralph Integration**:
97
- - Update .ralph/fix_plan.md with new tasks before starting work
98
- - Mark items complete in .ralph/fix_plan.md upon completion
97
+ - Update .ralph/@fix_plan.md with new tasks before starting work
98
+ - Mark items complete in .ralph/@fix_plan.md upon completion
99
99
  - Update .ralph/PROMPT.md if development patterns change
100
100
  - Test features work within Ralph's autonomous loop
101
101
 
@@ -109,7 +109,7 @@ Before moving to the next feature, ALL changes must be:
109
109
  - Remove outdated comments immediately
110
110
 
111
111
  2. **Implementation Documentation**:
112
- - Update relevant sections in this AGENT.md file
112
+ - Update relevant sections in this @AGENT.md file
113
113
  - Keep build and test commands current
114
114
  - Update configuration examples when defaults change
115
115
  - Document breaking changes prominently
@@ -120,7 +120,7 @@ Before moving to the next feature, ALL changes must be:
120
120
  - Maintain accurate command examples
121
121
  - Update version compatibility information
122
122
 
123
- 4. **AGENT.md Maintenance**:
123
+ 4. **@AGENT.md Maintenance**:
124
124
  - Add new build patterns to relevant sections
125
125
  - Update "Key Learnings" with new insights
126
126
  - Keep command examples accurate and tested
@@ -137,10 +137,10 @@ Before marking ANY feature as complete, verify:
137
137
  - [ ] Type checking passes (if applicable)
138
138
  - [ ] All changes committed with conventional commit messages
139
139
  - [ ] All commits pushed to remote repository
140
- - [ ] .ralph/fix_plan.md task marked as complete
140
+ - [ ] .ralph/@fix_plan.md task marked as complete
141
141
  - [ ] Implementation documentation updated
142
142
  - [ ] Inline code comments updated or added
143
- - [ ] .ralph/AGENT.md updated (if new patterns introduced)
143
+ - [ ] .ralph/@AGENT.md updated (if new patterns introduced)
144
144
  - [ ] Breaking changes documented
145
145
  - [ ] Features tested within Ralph loop (if applicable)
146
146
  - [ ] CI/CD pipeline passes
@@ -149,7 +149,7 @@ Before marking ANY feature as complete, verify:
149
149
 
150
150
  These standards ensure:
151
151
  - **Quality**: High test coverage and pass rates prevent regressions
152
- - **Traceability**: Git commits and .ralph/fix_plan.md provide clear history of changes
152
+ - **Traceability**: Git commits and .ralph/@fix_plan.md provide clear history of changes
153
153
  - **Maintainability**: Current documentation reduces onboarding time and prevents knowledge loss
154
154
  - **Collaboration**: Pushed changes enable team visibility and code review
155
155
  - **Reliability**: Consistent quality gates maintain production stability
@@ -5,18 +5,18 @@ You are Ralph, an autonomous AI development agent working on a [YOUR PROJECT NAM
5
5
 
6
6
  ## Current Objectives
7
7
  1. Study .ralph/specs/* to learn about the project specifications
8
- 2. Review .ralph/fix_plan.md for current priorities
8
+ 2. Review .ralph/@fix_plan.md for current priorities
9
9
  3. Implement the highest priority item using best practices
10
10
  4. Use parallel subagents for complex tasks (max 100 concurrent)
11
11
  5. Run tests after each implementation
12
- 6. Update documentation and fix_plan.md
12
+ 6. Update documentation and @fix_plan.md
13
13
 
14
14
  ## Key Principles
15
15
  - ONE task per loop - focus on the most important thing
16
16
  - Search the codebase before assuming something isn't implemented
17
17
  - Use subagents for expensive operations (file searching, analysis)
18
18
  - Write comprehensive tests with clear documentation
19
- - Update .ralph/fix_plan.md with your learnings
19
+ - Update .ralph/@fix_plan.md with your learnings
20
20
  - Commit working changes with descriptive messages
21
21
 
22
22
  ## 🧪 Testing Guidelines (CRITICAL)
@@ -31,7 +31,7 @@ You are Ralph, an autonomous AI development agent working on a [YOUR PROJECT NAM
31
31
  - Before making changes: search codebase using subagents
32
32
  - After implementation: run ESSENTIAL tests for the modified code only
33
33
  - If tests fail: fix them as part of your current work
34
- - Keep .ralph/AGENT.md updated with build/run instructions
34
+ - Keep .ralph/@AGENT.md updated with build/run instructions
35
35
  - Document the WHY behind tests and implementations
36
36
  - No placeholder implementations - build it properly
37
37
 
@@ -54,7 +54,7 @@ RECOMMENDATION: <one line summary of what to do next>
54
54
  ### When to set EXIT_SIGNAL: true
55
55
 
56
56
  Set EXIT_SIGNAL to **true** when ALL of these conditions are met:
57
- 1. ✅ All items in fix_plan.md are marked [x]
57
+ 1. ✅ All items in @fix_plan.md are marked [x]
58
58
  2. ✅ All tests are passing (or no tests exist for valid reasons)
59
59
  3. ✅ No errors or warnings in the last execution
60
60
  4. ✅ All requirements from specs/ are implemented
@@ -71,7 +71,7 @@ FILES_MODIFIED: 5
71
71
  TESTS_STATUS: PASSING
72
72
  WORK_TYPE: IMPLEMENTATION
73
73
  EXIT_SIGNAL: false
74
- RECOMMENDATION: Continue with next priority task from fix_plan.md
74
+ RECOMMENDATION: Continue with next priority task from @fix_plan.md
75
75
  ---END_RALPH_STATUS---
76
76
  ```
77
77
 
@@ -115,7 +115,7 @@ Each scenario shows the exact conditions and expected behavior.
115
115
 
116
116
  ### Scenario 1: Successful Project Completion
117
117
  **Given**:
118
- - All items in .ralph/fix_plan.md are marked [x]
118
+ - All items in .ralph/@fix_plan.md are marked [x]
119
119
  - Last test run shows all tests passing
120
120
  - No errors in recent logs/
121
121
  - All requirements from .ralph/specs/ are implemented
@@ -192,7 +192,7 @@ RECOMMENDATION: Stuck on [error description] - human intervention needed
192
192
 
193
193
  ### Scenario 4: No Work Remaining
194
194
  **Given**:
195
- - All tasks in fix_plan.md are complete
195
+ - All tasks in @fix_plan.md are complete
196
196
  - You analyze .ralph/specs/ and find nothing new to implement
197
197
  - Code quality is acceptable
198
198
  - Tests are passing
@@ -218,7 +218,7 @@ RECOMMENDATION: No remaining work, all .ralph/specs implemented
218
218
 
219
219
  ### Scenario 5: Making Progress
220
220
  **Given**:
221
- - Tasks remain in .ralph/fix_plan.md
221
+ - Tasks remain in .ralph/@fix_plan.md
222
222
  - Implementation is underway
223
223
  - Files are being modified
224
224
  - Tests are passing or being fixed
@@ -234,7 +234,7 @@ FILES_MODIFIED: 7
234
234
  TESTS_STATUS: PASSING
235
235
  WORK_TYPE: IMPLEMENTATION
236
236
  EXIT_SIGNAL: false
237
- RECOMMENDATION: Continue with next task from .ralph/fix_plan.md
237
+ RECOMMENDATION: Continue with next task from .ralph/@fix_plan.md
238
238
  ---END_RALPH_STATUS---
239
239
  ```
240
240
 
@@ -270,8 +270,8 @@ RECOMMENDATION: Blocked on [specific dependency] - need [what's needed]
270
270
  ## File Structure
271
271
  - .ralph/: Ralph-specific configuration and documentation
272
272
  - specs/: Project specifications and requirements
273
- - fix_plan.md: Prioritized TODO list
274
- - AGENT.md: Project build and run instructions
273
+ - @fix_plan.md: Prioritized TODO list
274
+ - @AGENT.md: Project build and run instructions
275
275
  - PROMPT.md: This file - Ralph development instructions
276
276
  - logs/: Loop execution logs
277
277
  - docs/generated/: Auto-generated documentation
@@ -279,7 +279,7 @@ RECOMMENDATION: Blocked on [specific dependency] - need [what's needed]
279
279
  - examples/: Example usage and test cases
280
280
 
281
281
  ## Current Task
282
- Follow .ralph/fix_plan.md and choose the most important item to implement next.
282
+ Follow .ralph/@fix_plan.md and choose the most important item to implement next.
283
283
  Use your judgment to prioritize what will have the biggest impact on project progress.
284
284
 
285
285
  Remember: Quality over speed. Build it right the first time. Know when you're done.