@litmers/cursorflow-orchestrator 0.1.0 → 0.1.2

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.
@@ -1,181 +1,181 @@
1
- # CursorFlow Resume
2
-
3
- ## Overview
4
- 중단되거나 실패한 레인을 재개합니다. 상태를 복구하거나 처음부터 다시 시작할 있습니다.
5
-
6
- ## Steps
7
-
8
- 1. **레인 상태 확인**
9
- ```bash
10
- cursorflow monitor
11
- ```
12
-
13
- 2. **레인 재개**
14
- ```bash
15
- cursorflow resume <lane-name>
16
- ```
17
-
18
- 3. **브랜치 정리 재시작**
19
- ```bash
20
- cursorflow resume <lane-name> --clean
21
- ```
22
-
23
- 4. **처음부터 다시 시작**
24
- ```bash
25
- cursorflow resume <lane-name> --restart
26
- ```
27
-
28
- ## 옵션
29
-
30
- | 옵션 | 설명 |
31
- |------|------|
32
- | `--run-dir <path>` | 특정 run 디렉토리 지정 |
33
- | `--clean` | 브랜치 정리 재시작 |
34
- | `--restart` | 처음부터 다시 시작 |
35
- | `--force` | 확인 없이 진행 |
36
-
37
- ## 예제
38
-
39
- ### 기본 재개
40
- ```bash
41
- # 최신 run에서 해당 레인 재개
42
- cursorflow resume 01-dashboard
43
- ```
44
-
45
- ### 특정 run에서 재개
46
- ```bash
47
- cursorflow resume --run-dir _cursorflow/logs/runs/my-run/ 01-dashboard
48
- ```
49
-
50
- ### 브랜치 충돌 해결 재개
51
- ```bash
52
- # 기존 브랜치 정리 재시작
53
- cursorflow resume 01-dashboard --clean
54
- ```
55
-
56
- ### 완전히 새로 시작
57
- ```bash
58
- # 모든 상태 초기화 재시작
59
- cursorflow resume 01-dashboard --restart
60
- ```
61
-
62
- ## 재개 프로세스
63
-
64
- 1. **상태 확인**
65
- - `state.json` 파일 로드
66
- - 마지막 태스크 위치 확인
67
- - Worktree 상태 확인
68
-
69
- 2. **환경 복구**
70
- - Worktree 접근 가능 여부 확인
71
- - 브랜치 체크아웃
72
- - 미커밋 변경사항 확인
73
-
74
- 3. **실행 재개**
75
- - 중단된 태스크부터 계속
76
- - 또는 새로 시작 (--restart)
77
-
78
- 4. **완료**
79
- - 남은 태스크 모두 수행
80
- - 변경사항 커밋 푸시
81
-
82
- ## 상태 파일 예시
83
-
84
- ```json
85
- {
86
- "label": "01-dashboard",
87
- "status": "failed",
88
- "currentTaskIndex": 1,
89
- "totalTasks": 3,
90
- "worktreeDir": ".cursorflow/logs/worktrees/01-dashboard-abc123",
91
- "pipelineBranch": "feature/dashboard-abc123",
92
- "error": "Build failed",
93
- "startTime": 1734567890000,
94
- "endTime": null
95
- }
96
- ```
97
-
98
- ## Checklist
99
- - [ ] 레인이 실제로 중단되었는가?
100
- - [ ] 상태 파일이 존재하는가?
101
- - [ ] 브랜치 충돌은 없는가?
102
- - [ ] Worktree가 존재하는가?
103
- - [ ] 미커밋 변경사항이 있는가?
104
-
105
- ## 트러블슈팅
106
-
107
- ### 상태 파일이 없는 경우
108
- ```bash
109
- # 최신 run 디렉토리 확인
110
- ls -lt _cursorflow/logs/runs/
111
-
112
- # 특정 run 지정
113
- cursorflow resume --run-dir _cursorflow/logs/runs/latest/ 01-dashboard
114
- ```
115
-
116
- ### 브랜치 충돌
117
- ```bash
118
- # 기존 브랜치 확인
119
- git branch | grep dashboard
120
-
121
- # 정리 재개
122
- cursorflow resume 01-dashboard --clean
123
- ```
124
-
125
- ### Worktree 문제
126
- ```bash
127
- # Worktree 목록 확인
128
- git worktree list
129
-
130
- # 문제 있는 worktree 제거
131
- git worktree remove <path> --force
132
-
133
- # 재개
134
- cursorflow resume 01-dashboard --restart
135
- ```
136
-
137
- ### 의존성 블록
138
- ```bash
139
- # 의존성이 해결되었는지 확인
140
- cursorflow monitor
141
-
142
- # 의존성 해결 후 재개
143
- cursorflow resume 01-dashboard
144
- ```
145
-
146
- ## 재개 시나리오
147
-
148
- ### 시나리오 1: 네트워크 오류로 중단
149
- ```bash
150
- # 단순 재개 (같은 위치부터 계속)
151
- cursorflow resume 01-dashboard
152
- ```
153
-
154
- ### 시나리오 2: 빌드 에러로 실패
155
- ```bash
156
- # 코드 수정
157
- cd .cursorflow/logs/worktrees/01-dashboard-xxx/
158
- # ... 코드 수정 ...
159
- git add -A
160
- git commit -m "fix: build error"
161
-
162
- # 다음 태스크부터 계속
163
- cursorflow resume 01-dashboard
164
- ```
165
-
166
- ### 시나리오 3: 브랜치 충돌
167
- ```bash
168
- # 브랜치 정리 새로 시작
169
- cursorflow resume 01-dashboard --clean
170
- ```
171
-
172
- ### 시나리오 4: 처음부터 다시
173
- ```bash
174
- # 모든 상태 초기화
175
- cursorflow resume 01-dashboard --restart
176
- ```
177
-
178
- ## Next Steps
179
- 1. 재개 `cursorflow monitor --watch`로 모니터링
180
- 2. 완료 PR 확인
181
- 3. 반복 실패 태스크 설정 검토
1
+ # CursorFlow Resume
2
+
3
+ ## Overview
4
+ Resume lanes that were interrupted or failed. You can restore the previous state or restart from scratch.
5
+
6
+ ## Steps
7
+
8
+ 1. **Check lane status**
9
+ ```bash
10
+ cursorflow monitor
11
+ ```
12
+
13
+ 2. **Resume a lane**
14
+ ```bash
15
+ cursorflow resume <lane-name>
16
+ ```
17
+
18
+ 3. **Clean branches before resuming**
19
+ ```bash
20
+ cursorflow resume <lane-name> --clean
21
+ ```
22
+
23
+ 4. **Restart from the beginning**
24
+ ```bash
25
+ cursorflow resume <lane-name> --restart
26
+ ```
27
+
28
+ ## Options
29
+
30
+ | Option | Description |
31
+ |------|------|
32
+ | `--run-dir <path>` | Use a specific run directory |
33
+ | `--clean` | Clean branches before restarting |
34
+ | `--restart` | Start over from the beginning |
35
+ | `--force` | Continue without confirmation |
36
+
37
+ ## Examples
38
+
39
+ ### Resume the latest run
40
+ ```bash
41
+ # Resume the lane from the latest run
42
+ cursorflow resume 01-dashboard
43
+ ```
44
+
45
+ ### Resume from a specific run
46
+ ```bash
47
+ cursorflow resume --run-dir _cursorflow/logs/runs/my-run/ 01-dashboard
48
+ ```
49
+
50
+ ### Resolve branch conflicts then resume
51
+ ```bash
52
+ # Clean up existing branches before restarting
53
+ cursorflow resume 01-dashboard --clean
54
+ ```
55
+
56
+ ### Start completely fresh
57
+ ```bash
58
+ # Reset all state before restarting
59
+ cursorflow resume 01-dashboard --restart
60
+ ```
61
+
62
+ ## Resume process
63
+
64
+ 1. **Check state**
65
+ - Load `state.json`
66
+ - Locate the last task index
67
+ - Inspect the worktree state
68
+
69
+ 2. **Restore the environment**
70
+ - Verify worktree accessibility
71
+ - Check out the branch
72
+ - Check for uncommitted changes
73
+
74
+ 3. **Resume execution**
75
+ - Continue from the interrupted task
76
+ - Or restart from the beginning (`--restart`)
77
+
78
+ 4. **Complete**
79
+ - Finish remaining tasks
80
+ - Commit and push changes
81
+
82
+ ## Sample state file
83
+
84
+ ```json
85
+ {
86
+ "label": "01-dashboard",
87
+ "status": "failed",
88
+ "currentTaskIndex": 1,
89
+ "totalTasks": 3,
90
+ "worktreeDir": ".cursorflow/logs/worktrees/01-dashboard-abc123",
91
+ "pipelineBranch": "feature/dashboard-abc123",
92
+ "error": "Build failed",
93
+ "startTime": 1734567890000,
94
+ "endTime": null
95
+ }
96
+ ```
97
+
98
+ ## Checklist
99
+ - [ ] Was the lane actually interrupted?
100
+ - [ ] Does the state file exist?
101
+ - [ ] Are there any branch conflicts?
102
+ - [ ] Does the worktree still exist?
103
+ - [ ] Are there uncommitted changes?
104
+
105
+ ## Troubleshooting
106
+
107
+ ### State file missing
108
+ ```bash
109
+ # Check the latest run directory
110
+ ls -lt _cursorflow/logs/runs/
111
+
112
+ # Specify a run explicitly
113
+ cursorflow resume --run-dir _cursorflow/logs/runs/latest/ 01-dashboard
114
+ ```
115
+
116
+ ### Branch conflicts
117
+ ```bash
118
+ # Inspect existing branches
119
+ git branch | grep dashboard
120
+
121
+ # Clean up and resume
122
+ cursorflow resume 01-dashboard --clean
123
+ ```
124
+
125
+ ### Worktree issues
126
+ ```bash
127
+ # List worktrees
128
+ git worktree list
129
+
130
+ # Remove problematic worktree
131
+ git worktree remove <path> --force
132
+
133
+ # Resume
134
+ cursorflow resume 01-dashboard --restart
135
+ ```
136
+
137
+ ### Dependency blocks
138
+ ```bash
139
+ # Verify dependencies are resolved
140
+ cursorflow monitor
141
+
142
+ # Resume after resolving
143
+ cursorflow resume 01-dashboard
144
+ ```
145
+
146
+ ## Resume scenarios
147
+
148
+ ### Scenario 1: Interrupted by network errors
149
+ ```bash
150
+ # Simply resume from the same position
151
+ cursorflow resume 01-dashboard
152
+ ```
153
+
154
+ ### Scenario 2: Failed due to build errors
155
+ ```bash
156
+ # After fixing code
157
+ cd .cursorflow/logs/worktrees/01-dashboard-xxx/
158
+ # ... apply fixes ...
159
+ git add -A
160
+ git commit -m "fix: build error"
161
+
162
+ # Continue from the next task
163
+ cursorflow resume 01-dashboard
164
+ ```
165
+
166
+ ### Scenario 3: Branch conflicts
167
+ ```bash
168
+ # Clean branches then restart
169
+ cursorflow resume 01-dashboard --clean
170
+ ```
171
+
172
+ ### Scenario 4: Start over
173
+ ```bash
174
+ # Reset all state
175
+ cursorflow resume 01-dashboard --restart
176
+ ```
177
+
178
+ ## Next steps
179
+ 1. After resuming, monitor with `cursorflow monitor --watch`.
180
+ 2. Check the PR when the run finishes.
181
+ 3. If failures repeat, review the task configuration.