@litmers/cursorflow-orchestrator 0.1.37 → 0.1.39

package/src/utils/logger.ts

@@ -144,9 +144,9 @@ export function withContext(context: string) {
  */
 export function section(message: string): void {
   console.log('');
-  console.log(`${COLORS.cyan}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${COLORS.reset}`);
+  console.log(`${COLORS.cyan}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${COLORS.reset}`);
   console.log(`${COLORS.cyan}  ${message}${COLORS.reset}`);
-  console.log(`${COLORS.cyan}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${COLORS.reset}`);
+  console.log(`${COLORS.cyan}━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━${COLORS.reset}`);
   console.log('');
 }
 

package/commands/cursorflow-add.md

@@ -1,159 +0,0 @@
-# cursorflow add
-
-Lane에 Task를 추가합니다.
-
-## 사용법
-
-```bash
-cursorflow add <FlowName> <LaneName> --task "name=...|model=...|prompt=..." [--after ...]
-```
-
-## 설명
-
-지정된 Flow의 Lane에 Task를 추가합니다.
-`--task` 옵션은 여러 번 사용하여 여러 태스크를 순차적으로 추가할 수 있습니다.
-
-## --task 형식
-
-```
-"name=<이름>|model=<모델>|prompt=<프롬프트>"
-```
-
-### 필수 필드
-
-| 필드 | 설명 | 예시 |
-|------|------|------|
-| `name` | 태스크 이름 (영문, 숫자, -, _) | `name=implement` |
-| `prompt` | 태스크 프롬프트/지시사항 | `prompt=API 구현` |
-
-### 선택 필드
-
-| 필드 | 설명 | 예시 |
-|------|------|------|
-| `model` | AI 모델 (생략 시 기본 모델 사용) | `model=<your-model>` |
-
-기본 모델 설정: `cursorflow config defaultModel <model-name>`
-
-## --after 형식 (의존성 설정)
-
-첫 번째 태스크가 시작되기 전에 완료되어야 할 태스크를 지정합니다.
-
-| 형식 | 설명 |
-|------|------|
-| `"lane"` | 해당 레인의 **마지막 태스크** 완료 후 시작 |
-| `"lane:task"` | 특정 태스크 완료 후 시작 |
-| `"a:t1, b:t2"` | **여러 태스크가 모두 완료**된 후 시작 |
-
-## 예시
-
-### 기본 사용: 단일 태스크 추가 (기본 모델 사용)
-
-```bash
-cursorflow add SearchFeature api \
-  --task "name=implement|prompt=검색 API 구현"
-```
-
-### 여러 태스크 추가
-
-```bash
-cursorflow add SearchFeature api \
-  --task "name=plan|prompt=API 설계" \
-  --task "name=implement|prompt=검색 API 구현" \
-  --task "name=test|prompt=테스트 코드 작성"
-```
-
-### 의존성 설정: 특정 태스크 완료 후 시작
-
-```bash
-# api 레인의 implement 태스크 완료 후 시작
-cursorflow add SearchFeature web \
-  --task "name=ui|prompt=검색 UI 구현" \
-  --after "api:implement"
-```
-
-### 의존성 설정: 레인 전체 완료 후 시작
-
-```bash
-# api 레인의 마지막 태스크 완료 후 시작
-cursorflow add SearchFeature web \
-  --task "name=ui|prompt=검색 UI 구현" \
-  --after "api"
-```
-
-### 다중 의존성: 여러 태스크 완료 후 시작
-
-```bash
-# web과 mobile 모두 완료된 후 시작
-cursorflow add SearchFeature e2e \
-  --task "name=verify|prompt=E2E 테스트" \
-  --after "web:ui, mobile:app"
-```
-
-## 출력 예시
-
-```
-✅ 3개 태스크 추가 완료
-
-  📄 01-api.json
-
-  ├── plan (<default-model>)
-  ├── implement (<default-model>)
-  └── test (<default-model>)
-
-전체 태스크 목록:
-  1. plan (new)
-  2. implement (new)
-  3. test (new)
-
-다음 단계:
-  cursorflow run SearchFeature    # Flow 실행
-  cursorflow doctor SearchFeature # 설정 검증
-```
-
-## 생성되는 Lane 파일 구조
-
-```json
-{
-  "laneName": "api",
-  "tasks": [
-    {
-      "name": "plan",
-      "model": "<your-model>",
-      "prompt": "API 설계"
-    },
-    {
-      "name": "implement",
-      "model": "<your-model>",
-      "prompt": "검색 API 구현"
-    },
-    {
-      "name": "test",
-      "model": "<your-model>",
-      "prompt": "테스트 코드 작성"
-    }
-  ]
-}
-```
-
-### 의존성이 있는 경우
-
-```json
-{
-  "laneName": "web",
-  "tasks": [
-    {
-      "name": "ui",
-      "model": "<your-model>",
-      "prompt": "검색 UI 구현",
-      "dependsOn": ["01-api:implement"]
-    }
-  ]
-}
-```
-
-## 관련 명령어
-
-- [cursorflow new](cursorflow-new.md) - Flow와 Lane 생성
-- [cursorflow run](cursorflow-run.md) - Flow 실행
-- [cursorflow doctor](cursorflow-doctor.md) - 설정 검증
-

package/commands/cursorflow-clean.md

@@ -1,84 +0,0 @@
-# CursorFlow Clean
-
-## Overview
-Clean up temporary resources created by CursorFlow, including Git worktrees, feature branches, log files, and task definitions.
-
-## Usage
-
-```bash
-cursorflow clean <type> [options]
-```
-
-## Clean Types
-
-| Type | Description |
-|------|------|
-| `branches` | Remove local feature branches created by CursorFlow |
-| `worktrees` | Remove temporary Git worktrees |
-| `logs` | Clear all run and terminal logs |
-| `tasks` | Remove task definition directories (keeps `example/`) |
-| `all` | Clean everything (branches, worktrees, logs, and tasks) |
-
-## Options
-
-| Option | Description |
-|------|------|
-| `--run <id>` | Clean resources linked to a specific run |
-| `--older-than <time>` | Clean resources older than a specific time (e.g., `24h`, `7d`) |
-| `--orphaned` | Clean orphaned resources (worktrees without runs, etc.) |
-| `--dry-run` | Show what would be removed without actually deleting anything |
-| `--force` | Force removal (ignore uncommitted changes in worktrees) |
-| `--include-latest` | Also remove the most recent item (by default, latest is kept) |
-| `--help`, `-h` | Show help |
-
-## Examples
-
-### Review before deleting (latest is kept by default)
-```bash
-cursorflow clean all --dry-run
-```
-
-### Clean only worktrees (keeps the latest worktree)
-```bash
-cursorflow clean worktrees
-```
-
-### Force clean everything including the latest
-```bash
-cursorflow clean all --force --include-latest
-```
-
-### Remove all worktrees including the latest
-```bash
-cursorflow clean worktrees --include-latest
-```
-
-### Clean resources for a specific run
-```bash
-cursorflow clean all --run run-1734873132
-```
-
-### Clean logs and tasks older than 7 days
-```bash
-cursorflow clean logs --older-than 7d
-cursorflow clean tasks --older-than 7d
-```
-
-### Clean orphaned worktrees and branches
-```bash
-cursorflow clean all --orphaned
-```
-
-## Notes
-
-1. **Safety**: It is highly recommended to run with `--dry-run` first to see exactly what will be deleted.
-2. **Worktrees**: The command identifies CursorFlow worktrees by their location (usually in `_cursorflow/worktrees/`) or their prefix.
-3. **Branches**: Only branches starting with the configured `branchPrefix` (default: `cursorflow/`) are targeted.
-4. **Irreversible**: Once logs are deleted, they cannot be recovered.
-5. **Default Behavior**: By default, the most recent item is preserved. The "most recent" is determined by:
-   - **Worktrees**: Directory modification time
-   - **Branches**: Latest commit timestamp
-   - **Logs**: File/directory modification time
-   - **Tasks**: Directory modification time
-   
-   Use `--include-latest` to remove everything including the most recent item.

package/commands/cursorflow-doctor.md

@@ -1,102 +0,0 @@
-# CursorFlow Doctor
-
-## Overview
-Verify that your environment and flow configurations are properly set up for CursorFlow.
-
-## Usage
-
-```bash
-cursorflow doctor [flow-name] [options]
-```
-
-## Checks Performed
-- **Environment**: Git repository status, remote availability, and worktree support.
-- **Cursor IDE**: Verifies `cursor-agent` is installed and authenticated.
-- **Flow/Tasks**: (Optional) Validates flow JSON files for schema errors or missing fields.
-
-## Options
-
-| Option | Description |
-|------|------|
-| `[flow-name]` | Flow name to validate (e.g., `SearchFeature`) |
-| `--tasks-dir <path>` | Validate flow/tasks in a specific directory (legacy) |
-| `--executor <type>` | Check environment for `cursor-agent` \| `cloud` |
-| `--test-agent` | Run an interactive agent test (to approve permissions) |
-| `--no-cursor` | Skip Cursor Agent installation and auth checks |
-| `--json` | Output the report in machine-readable JSON format |
-
-## Flow Validation
-
-When a flow name or `--tasks-dir` is provided, the doctor performs comprehensive validation:
-
-### Structure Validation
-- **tasks array**: Must exist and be non-empty
-- **task.name**: Required, must be alphanumeric with `-` and `_` only, unique within lane
-- **task.prompt**: Required, should be descriptive (warns if < 10 chars)
-- **task.model**: Optional, must be string if provided
-- **task.dependsOn**: Optional, task-level dependencies
-
-### Dependency Validation (DAG)
-- **Unknown dependencies**: Reports if `dependsOn` references non-existent lanes/tasks
-- **Circular dependencies**: Detects cycles (e.g., A→B→A) that would cause deadlock
-- Reports the exact cycle path for easy debugging
-
-### Branch Validation
-- **Prefix collision**: Warns if multiple lanes use the same `branchPrefix`
-- **Existing branch conflicts**: Detects if existing branches match a lane's prefix
-- **Duplicate lane names**: Ensures each lane file has a unique name
-
-## Examples
-
-```bash
-# Basic environment check
-cursorflow doctor
-
-# Validate a specific flow by name
-cursorflow doctor SearchFeature
-
-# Test agent permissions
-cursorflow doctor --test-agent
-
-# Validate a specific flow directory
-cursorflow doctor --tasks-dir _cursorflow/flows/001_SearchFeature
-
-# Skip cursor checks (faster)
-cursorflow doctor SearchFeature --no-cursor
-
-# Output as JSON
-cursorflow doctor SearchFeature --json
-```
-
-## Example Output
-
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-  🩺 CursorFlow Doctor
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-cwd: /home/user/project
-repo: /home/user/project
-tasks: /home/user/project/_cursorflow/flows/001_SearchFeature
-
-✅ All checks passed
-
-💡 Tip: If this is your first run, we recommend running:
-   cursorflow doctor --test-agent
-```
-
-## Common Issues & Fixes
-
-| Issue | Potential Fix |
-|-------|---------------|
-| `Cursor Agent not found` | Ensure Cursor IDE is installed and `cursor` command is in PATH. |
-| `Not authenticated` | Open Cursor IDE and log in to your account. |
-| `Worktree not supported` | Upgrade your Git version (requires Git >= 2.5). |
-| `Circular dependency` | Check the `dependsOn` fields in your task JSON files. |
-| `Flow not found` | Verify flow name or create with `cursorflow new`. |
-
-## Related Commands
-
-- [cursorflow new](cursorflow-new.md) - Create Flow and Lanes
-- [cursorflow add](cursorflow-add.md) - Add Tasks to Lanes
-- [cursorflow run](cursorflow-run.md) - Run Flow

package/commands/cursorflow-models.md

@@ -1,51 +0,0 @@
-# CursorFlow Models
-
-## Overview
-List available AI models supported by CursorFlow and their recommended use cases. These models are discovered from your local `cursor-agent` installation.
-
-## Usage
-
-```bash
-cursorflow models [options]
-```
-
-## Options
-
-| Option | Description |
-|------|------|
-| `--list`, `-l` | List models in a table (default) |
-| `--json` | Output model list as JSON |
-
-## Available Models
-
-| ID | Name | Provider | Recommended Use |
-|----|------|----------|-----------------|
-| `sonnet-4.5` | Claude 3.7 Sonnet | Anthropic | General implementation, fast work (Most versatile) |
-| `sonnet-4.5-thinking` | Claude 3.7 Sonnet (Thinking) | Anthropic | Code review, deeper reasoning (Thinking model) |
-| `opus-4.5` | Claude 4.0 Opus | Anthropic | Complex tasks, high quality (Advanced) |
-| `opus-4.5-thinking` | Claude 4.0 Opus (Thinking) | Anthropic | Architecture design (Premium) |
-| `gpt-5.2` | GPT-5.2 | OpenAI | General tasks |
-| `gpt-5.2-high` | GPT-5.2 High Reasoning | OpenAI | Advanced reasoning (High performance) |
-
-## Model Configuration
-
-In your task `.json` files, specify the model like this:
-
-```json
-{
-  "model": "sonnet-4.5",
-  "tasks": [
-    {
-      "name": "implement",
-      "prompt": "..."
-    }
-  ]
-}
-```
-
-## Tips
-
-- Use the `ID` from the `cursorflow models` output in your JSON files.
-- You can set a default model in `cursorflow.config.js`.
-- Individual tasks within a lane can override the lane-level model.
-

package/commands/cursorflow-monitor.md

@@ -1,90 +0,0 @@
-# CursorFlow Monitor
-
-## Overview
-The `cursorflow monitor` command provides a powerful, interactive terminal-based dashboard to track the execution status of all lanes in real-time. It allows you to visualize dependencies, stream live terminal output, and intervene in running tasks.
-
-## Usage
-
-```bash
-# Monitor the most recent run
-cursorflow monitor
-
-# List all runs (Multiple Flows Dashboard)
-cursorflow monitor --list
-
-# Monitor a specific run directory
-cursorflow monitor run-2025-12-21T10-00-00
-```
-
-## Options
-
-| Option | Description |
-|--------|-------------|
-| `[run-dir]` | Run directory or ID to monitor (default: latest) |
-| `--list`, `-l` | Show all runs dashboard (interactive list) |
-| `--interval <n>` | Refresh interval in seconds (default: 2) |
-| `--help`, `-h` | Show help |
-
-## Dashboard Controls
-
-### List View (Main)
-- **Navigation**: Use `↑` and `↓` to move between lanes.
-- **Details**: Press `→` or `Enter` to enter the **Lane Detail View**.
-- **Flow View**: Press `F` to see the task dependency graph (DAG).
-- **All Runs**: Press `M` to switch to the **All Flows Dashboard**.
-- **Unified Logs**: Press `U` to see a merged log stream of all lanes.
-- **Quit**: Press `Q` to exit.
-
-### All Flows Dashboard
-- **Navigation**: Use `↑` and `↓` to select a flow.
-- **Switch**: Press `→` or `Enter` to switch the monitor to the selected flow.
-- **Delete**: Press `D` to delete a completed flow's logs (requires confirmation).
-- **Refresh**: Press `R` to refresh the list of flows.
-- **Back**: Press `M` or `Esc` to return to the List View.
-
-### Lane Detail View
-- **History Browsing**: Use `↑` and `↓` to scroll through conversation history.
-- **Message Detail**: Press `→` or `Enter` on a message to see its full content.
-- **Live Terminal**: Press `T` to enter the **Full Terminal View**.
-- **Intervention**: Press `I` to send a manual prompt to the agent (requires `enableIntervention: true`).
-- **Kill Process**: Press `K` to forcefully terminate a stuck agent process.
-- **Back**: Press `←` or `Esc` to return to the List View.
-
-### Full Terminal View
-- **Scrolling**: Use `↑` and `↓` to scroll through the entire agent output log.
-- **Back**: Press `T`, `←`, or `Esc` to return to the Lane Detail View.
-
-### Intervention View
-- **Typing**: Type your message directly.
-- **Send**: Press `Enter` to send the intervention message.
-- **Cancel**: Press `Esc` to cancel and return.
-
-## Key Concepts
-
-### Lane Statuses
-| Status | Icon | Description |
-|--------|------|-------------|
-| `pending` | ⚪ | Lane is waiting to start |
-| `waiting` | ⏳ | Waiting for parent dependencies to complete |
-| `running` | 🔄 | Agent is currently executing tasks |
-| `reviewing` | 👀 | AI Reviewer is checking the task results |
-| `completed` | ✅ | All tasks and reviews finished successfully |
-| `failed` | ❌ | A task or review failed with an error |
-| `blocked` | 🚫 | Blocked by a failed dependency |
-
-### Dependency Flow View
-A visual representation of the Directed Acyclic Graph (DAG). It shows which lanes must finish before others can start, helping you understand the execution pipeline.
-
-### Heartbeat Logs
-CursorFlow monitors agent activity and logs status every few seconds. If a lane shows `0 bytes received` for a long period, it may be stuck or thinking deeply.
-
-## Troubleshooting
-
-### Lane is stuck
-1. Enter the **Lane Detail View**.
-2. Check the **PID** to ensure the process is still alive.
-3. Check the **Live Terminal** preview or enter **Full Terminal View (T)**.
-4. If it's truly stuck, press `K` to kill it, then use `cursorflow resume <lane>` to restart.
-
-### Sending Instructions
-If the agent is heading in the wrong direction, use the **Intervention (I)** feature to guide it without stopping the run. Note that this requires `enableIntervention: true` in the task's JSON configuration.

package/commands/cursorflow-new.md

@@ -1,87 +0,0 @@
-# cursorflow new
-
-Flow와 Lane을 생성합니다.
-
-## 사용법
-
-```bash
-cursorflow new <FlowName> --lanes "lane1,lane2,..."
-```
-
-## 설명
-
-새로운 Flow 디렉토리를 생성하고, 지정된 Lane 파일들의 뼈대를 만듭니다.
-각 Lane에 실제 Task를 추가하려면 `cursorflow add` 명령을 사용하세요.
-
-## 옵션
-
-| 옵션 | 설명 | 예시 |
-|------|------|------|
-| `--lanes <names>` | 콤마로 구분된 레인 이름 목록 (필수) | `--lanes "backend,frontend"` |
-
-## 예시
-
-### 기본 사용
-
-```bash
-# 백엔드와 프론트엔드 2개 레인 생성
-cursorflow new ShopFeature --lanes "backend,frontend"
-```
-
-### 3개 레인 생성
-
-```bash
-# API, Web, Mobile 3개 레인 생성
-cursorflow new SearchFeature --lanes "api,web,mobile"
-```
-
-## 생성 결과
-
-```
-_cursorflow/flows/001_ShopFeature/
-├── flow.meta.json       # Flow 메타데이터
-├── 01-backend.json      # Lane 1 (빈 상태)
-└── 02-frontend.json     # Lane 2 (빈 상태)
-```
-
-### flow.meta.json 스키마
-
-```json
-{
-  "id": "001",
-  "name": "ShopFeature",
-  "createdAt": "2024-12-25T10:30:00Z",
-  "createdBy": "user",
-  "baseBranch": "main",
-  "status": "pending",
-  "lanes": ["backend", "frontend"]
-}
-```
-
-### Lane 파일 스키마 (빈 상태)
-
-```json
-{
-  "laneName": "backend",
-  "tasks": []
-}
-```
-
-## 다음 단계
-
-Flow 생성 후, 각 Lane에 Task를 추가합니다:
-
-```bash
-cursorflow add ShopFeature backend \
-  --task "name=implement|prompt=API 구현"
-
-cursorflow add ShopFeature frontend \
-  --task "name=ui|prompt=UI 구현" \
-  --after "backend:implement"
-```
-
-## 관련 명령어
-
-- [cursorflow add](cursorflow-add.md) - Lane에 Task 추가
-- [cursorflow run](cursorflow-run.md) - Flow 실행
-