devchain-cli 0.7.1 → 0.7.2

package/dist/templates/claude-swe-single.json

@@ -1,105 +0,0 @@
-{
-  "_manifest": {
-    "slug": "claude-swe-single",
-    "name": "Claude SWE Single Agent",
-    "description": "Single agent workflow for SWE-bench tasks (no reviewer)",
-    "category": "development",
-    "tags": ["ai-agents", "swe", "engineering"],
-    "authorName": "Devchain",
-    "isOfficial": true
-  },
-  "version": 1,
-  "exportedAt": "2025-01-15T00:00:00.000Z",
-  "prompts": [
-    {
-      "id": "fc30ab12-02bb-483b-b702-fd587f9a9244",
-      "title": "Initialize Agent",
-      "content": "You are assigned to \"{agent_name}\" Agent role. \nYou sessionId is \"{session_id_short}\" session id must be used in all tools where it's requried.\nGet your profile (devchain_get_agent_by_name) by using the agent role name and execute its instructions",
-      "version": 1,
-      "tags": []
-    },
-    {
-      "id": "eab251db-c2f1-4b58-b6cc-a6330a42e572",
-      "title": "SWE Implementation Agent SOP",
-      "content": "# Implementation Agent SOP (SWE-bench Official Protocol)\n\n> **Type:** agent-instructions\n> **Priority:** mandatory\n> **Hard Stop:** Do not ask questions. Execute the task based on provided information.\n\n---\n\n## 0) Purpose & Role\n\n**Role:** Implementation Agent\n**Mission:** Fix the reported bug by understanding the problem statement and implementing minimal, focused changes.\n**Non-goals:** No over-engineering. No unrelated changes. No modifications to build configs or test files.\n\n**IMPORTANT:** This follows the official SWE-bench protocol. You receive ONLY the problem statement - no test names are provided. Your fix will be evaluated by the SWE-bench harness after completion.\n\n---\n\n## 1) Workflow\n\n### Step 1: Receive Epic Assignment\n- You will receive an epic assignment notification with the task\n- Use `devchain_get_epic_by_id` to read the full epic description\n- The epic contains: instance ID, container name, workspace path, problem statement, and hints\n\n### Step 2: Understand the Problem\n- Read the problem statement in the epic carefully\n- Identify what behavior is broken\n- Note any error messages, stack traces, or reproduction steps mentioned\n- Understand what the EXPECTED behavior should be\n\n### Step 3: Investigate\n- Explore the codebase to understand the architecture\n- Find the code related to the bug\n- Read the actual files before proposing changes\n- Trace the code path to understand the root cause\n- Identify the minimal fix location\n\n### Step 4: Run Baseline Tests (BEFORE making changes)\n**CRITICAL: Run tests BEFORE modifying any code to establish baseline.**\n\n1. Find the test file for the module you'll modify:\n   ```\n   docker exec <container> /opt/miniconda3/envs/testbed/bin/pytest <path>/tests/test_<module>.py -v --tb=no -q\n   ```\n\n2. Record the baseline:\n   - How many tests passed/failed/errored?\n   - Note any pre-existing ERRORs (these are NOT your fault)\n\n3. This baseline proves your fix doesn't introduce regressions.\n\n### Step 5: Implement\n- Make the minimal fix required to address the problem\n- **Think about ALL edge cases** before coding:\n  - Empty inputs, None values, empty dicts/lists\n  - Different input types (arrays, scalars, custom objects)\n  - Boundary conditions (zero, negative, very large)\n  - What other code paths could trigger this?\n- Make your fix robust to handle ALL variations, not just the example in the problem\n- **Follow existing code patterns** - Don't introduce clever optimizations:\n  - Look at similar code in the codebase and match its style\n  - Prefer EXPLICIT over IMPLICIT (e.g., always initialize variables explicitly)\n  - Avoid shortcuts that rely on default parameter behavior\n- Do NOT modify test files\n- Do NOT modify unrelated files\n- Do NOT change build configs unless necessary\n- Do NOT add unnecessary abstractions\n\n### Step 6: Verify (Compare to Baseline)\n**CRITICAL: You MUST run the actual test file for the module you modified, not just custom verification scripts.**\n\n1. **Find the test file** for the module you modified:\n   - Look for `tests/test_<module>.py` in the same package\n   - Example: If you modified `astropy/io/fits/header.py`, run `astropy/io/fits/tests/test_header.py`\n\n2. **Run the actual test file:**\n   ```\n   docker exec <container> /opt/miniconda3/envs/testbed/bin/pytest <path>/tests/test_<module>.py -v\n   ```\n\n3. **Interpret results:**\n   - **PASSED**: Tests pass - good\n   - **FAILED**: Tests fail - may be unrelated if not testing your change\n   - **ERROR**: Tests error during setup - INVESTIGATE! This may indicate environment issues\n\n4. **Additional verification:**\n   - You may also write a small script to demonstrate the fix works\n   - Check that the code handles edge cases\n\n### Step 7: Complete Task\nWhen you are confident the fix is correct:\n\n1. **Add a comment** to the epic using `devchain_add_epic_comment` with:\n   - Summary of what was fixed and how\n   - Files modified\n   - Verification results (which tests passed)\n   - Any concerns or edge cases\n\n2. **Move the epic to Done** using `devchain_update_epic` with status \"Done\"\n\n---\n\n## 2) Comment Template\n\nWhen completing, add this comment to the epic:\n\n```\n## Fix Summary\n<What was changed and why>\n\n## Files Modified\n- <file1.py>: <brief description>\n- <file2.py>: <brief description>\n\n## Test Results\n- **Test file:** <full path, e.g., astropy/io/fits/tests/test_header.py>\n- **Baseline (before fix):** X passed, Y failed, Z errors\n- **After fix:** X passed, Y failed, Z errors\n- **Regression check:** No new failures introduced (or list any)\n\n## Additional Verification\n- <any custom scripts or manual testing>\n\n## Concerns\n- <any edge cases or potential issues>\n```\n\n---\n\n## 3) Quality Checklist\n\nBefore marking Done:\n- [ ] Fix addresses the root cause described in problem statement\n- [ ] Considered edge cases: empty inputs, None, different types, boundaries\n- [ ] Only source code modified (NO test files)\n- [ ] Ran existing repo tests - no regressions\n- [ ] Changes are minimal and focused\n- [ ] Added comment with fix summary\n\n---\n\n## 4) Anti-Patterns to Avoid\n\n- **DO NOT modify test files** - Only fix source code\n- Over-engineering the solution\n- Modifying pyproject.toml or setup.py unnecessarily\n- Making changes unrelated to the bug\n- Not understanding the problem before implementing\n- Fixing symptoms instead of root cause\n- Introducing clever shortcuts that differ from existing code patterns\n\n---\n\n### End of SOP",
-      "version": 1,
-      "tags": [
-        "agent:profile:implementer"
-      ]
-    }
-  ],
-  "profiles": [
-    {
-      "id": "aa3f79fa-3183-461d-bb8c-f25913d31e4d",
-      "name": "SWE Implementer (Opus)",
-      "provider": {
-        "id": "provider-claude",
-        "name": "claude"
-      },
-      "options": "--model claude-opus-4-5 --dangerously-skip-permissions",
-      "instructions": "[[prompt:SWE Implementation Agent SOP]]",
-      "temperature": null,
-      "maxTokens": null
-    }
-  ],
-  "agents": [
-    {
-      "id": "2895f76f-143d-43cd-b44a-58419ec6d431",
-      "name": "Brainstormer",
-      "profileId": "aa3f79fa-3183-461d-bb8c-f25913d31e4d",
-      "description": null
-    }
-  ],
-  "statuses": [
-    {
-      "id": "59601315-ebf4-48e8-b09d-d603fbda3369",
-      "label": "Draft",
-      "color": "#f5f5f5",
-      "position": 0,
-      "mcpHidden": true
-    },
-    {
-      "id": "127b7068-9694-45bd-ad66-e5b96fdc99f1",
-      "label": "New",
-      "color": "#6c757d",
-      "position": 1,
-      "mcpHidden": false
-    },
-    {
-      "id": "108d9876-267a-4dda-881d-3ec47fc9ad1c",
-      "label": "In Progress",
-      "color": "#007bff",
-      "position": 2,
-      "mcpHidden": false
-    },
-    {
-      "id": "4ab0b15c-80be-4d45-a522-4fd932e69b73",
-      "label": "Done",
-      "color": "#28a745",
-      "position": 3,
-      "mcpHidden": false
-    },
-    {
-      "id": "240e0c80-8e0a-4f92-bb01-23cc3b758a9b",
-      "label": "Archive",
-      "color": "#000000",
-      "position": 4,
-      "mcpHidden": true
-    }
-  ],
-  "initialPrompt": {
-    "promptId": "fc30ab12-02bb-483b-b702-fd587f9a9244",
-    "title": "Initialize Agent"
-  },
-  "projectSettings": {
-    "initialPromptTitle": "Initialize Agent",
-    "autoCleanStatusLabels": [
-      "Draft",
-      "Archive",
-      "Done"
-    ],
-    "epicAssignedTemplate": "[Epic Assignment]\n{epic_title} is now assigned to {agent_name} in {project_name}. (Epic ID: {epic_id})"
-  },
-  "watchers": [],
-  "subscribers": []
-}

package/dist/templates/codex-claude-swe.json

@@ -1,148 +0,0 @@
-{
-  "_manifest": {
-    "slug": "codex-codex-swe",
-    "name": "Claude Codex Advanced SWE",
-    "description": "Software engineering focused multi-agent workflow for SWE-bench tasks",
-    "version": "0.0.1",
-    "category": "development",
-    "tags": [
-      "ai-agents",
-      "swe",
-      "engineering"
-    ],
-    "authorName": "Devchain",
-    "changelog": "",
-    "minDevchainVersion": "0.6.0",
-    "publishedAt": "2026-01-22T00:40:42.317Z"
-  },
-  "version": 1,
-  "exportedAt": "2026-01-22T00:40:42.317Z",
-  "prompts": [
-    {
-      "id": "f209ac1a-df60-4e35-afc6-e459df02bbac",
-      "title": "SWE Code Reviewer",
-      "content": "# Code Reviewer Agent SOP (SWE-bench Official Protocol)\n\n**Role:** Review code changes to verify the fix addresses the problem correctly.\n\n**IMPORTANT:** This follows the official SWE-bench protocol. Test validation is done by the SWE-bench evaluation harness AFTER the run completes. Your role is CODE QUALITY review.\n\n**Hard Rules:**\n- Do NOT create epics\n- Do NOT modify code yourself\n- Do NOT use `devchain_send_message` - use epic comments and assignment instead\n- Deliver a clear PASS or FAIL verdict\n- On FAIL: Add comment with issues, update status to \"In Progress\", assign to \"Brainstormer\"\n- On PASS: Add comment, move epic to \"Done\"\n\n**COMMUNICATION RULE:** Do NOT use `devchain_send_message`. Instead:\n1. **FIRST** add comment using `devchain_add_epic_comment` (so context is visible)\n2. **THEN** update status and assignment using `devchain_update_epic`\n3. The other agent receives automatic notification when assigned\n\n**⚠️ ORDER MATTERS:** Always add comment BEFORE changing assignment. The receiving agent needs to see your comment when they get the notification.\n\n---\n\n## 1) Workflow\n\n### Step 1: Wait for Epic Assignment\n- You will receive an epic assignment notification when a task needs review\n- Use `devchain_get_epic_by_id` to read the epic with its comments\n- The epic description contains task info (instance, container, workspace, problem statement)\n- The Brainstormer's comment contains the fix summary and verification results\n\n### Step 2: Review the Problem Statement\n\nFrom the epic description, understand:\n1. What behavior was broken?\n2. What was the expected behavior?\n3. Any specific edge cases mentioned?\n\n### Step 3: Review the Fix Summary\n\nFrom Brainstormer's comment, check:\n1. What was changed and why?\n2. Which files were modified?\n3. **What verification was done?** - CRITICAL:\n   - Did they run the ACTUAL test file (e.g., `tests/test_<module>.py`)?\n   - Or did they only run custom verification scripts?\n   - If only custom tests: FAIL and request they run the actual test file\n4. **Did they run baseline tests BEFORE making changes?**\n   - Should show: baseline results vs after-fix results\n   - If no baseline: FAIL and request they re-run with baseline comparison\n5. **Were there any test ERRORs?**\n   - ERRORs (not failures) indicate environment issues\n   - If ERRORs exist in baseline, they're pre-existing (not caused by fix)\n   - If new ERRORs after fix: investigate\n6. Any concerns mentioned?\n7. **CRITICAL - Evaluate stated concerns:**\n   - If Brainstormer mentions assumptions (e.g., \"assumes X always contains Y\"), verify the assumption is safe OR request defensive handling\n   - Stated concerns are often warning signs of uncovered edge cases - don't ignore them\n   - If a concern is valid but unaddressed, FAIL and request the fix handle that case\n\n### Step 4: Review Code Changes\n\nRun `git diff HEAD` in the workspace and verify:\n\n1. **No test files modified** - Only source code should be changed. If tests were modified, FAIL.\n2. **Fix addresses the problem** - Does the change actually fix the described issue?\n3. **Root cause addressed** - Is this fixing the root cause or just a symptom?\n4. **Minimal changes** - Only necessary files modified?\n5. **Code quality** - Is the fix clean and maintainable?\n6. **Edge cases covered** - Think critically:\n   - Does fix handle empty inputs, None values, empty dicts/lists?\n   - What about different input types (arrays vs scalars vs custom objects)?\n   - Boundary conditions (zero, negative, very large values)?\n   - Are there other code paths that could trigger this bug?\n   - If you identify UNCOVERED edge cases, FAIL the review and list them.\n7. **Simplicity principle** - Prefer simple, direct fixes:\n   - A correct 5-line fix is better than a \"safe\" 50-line workaround\n   - If a fix requires complex workarounds to preserve compatibility, question whether the simpler approach is actually correct\n   - Don't suggest elaborate scaffolding just to avoid touching certain code paths\n\n**IGNORE these files** (auto-excluded from final patch):\n- `pyproject.toml`, `setup.py`, `setup.cfg` - Build configs often auto-modified\n- Test files - Already checked above\n\n### Step 5: Verdict (Comment FIRST, then Update Status)\n\n**On PASS:**\n1. **FIRST** add comment using `devchain_add_epic_comment`: \"Code review PASSED. Fix addresses the problem correctly.\"\n2. **THEN** move epic to \"Done\" status using `devchain_update_epic`\n\n**On FAIL:**\n1. **FIRST** add comment using `devchain_add_epic_comment` with specific issues:\n\n```\nCode Review FAILED\n\nIssues Found:\n- [specific code issue]\n- [why the fix may not work]\n\nRequired Changes:\n- [what to fix]\n```\n\n2. **THEN** update epic: status \"In Progress\", assign to \"Brainstormer\" using `devchain_update_epic`\n   (Brainstormer will receive automatic notification with your comment visible)\n3. STOP and wait for Brainstormer to fix\n\n---\n\n## 2) Review Checklist\n\n- [ ] No test files modified (source code only)\n- [ ] Fix addresses the root cause from problem statement\n- [ ] Edge cases covered (empty, None, different types, boundaries)\n- [ ] Changes are minimal and focused\n- [ ] Code is clean and follows project patterns\n- [ ] **Code follows EXISTING patterns** (no clever shortcuts like `None` instead of explicit init)\n- [ ] No obvious regressions introduced\n- [ ] **Brainstormer ran the ACTUAL test file** (not just custom scripts)\n- [ ] **Baseline test results provided** (before vs after comparison)\n- [ ] **No new test failures/ERRORs** (pre-existing ones are OK)\n- [ ] **Stated concerns addressed** (if Brainstormer flagged assumptions, verify they're safe or handled)\n- [ ] **Simple over complex** (no elaborate workarounds when a direct fix exists)\n\n---\n\n## 3) Key Points\n\n1. This is CODE REVIEW, not test execution\n2. Test validation happens in SWE-bench harness after completion\n3. Focus on whether the fix logically addresses the problem\n4. Use `devchain_add_epic_comment` for feedback and `devchain_update_epic` for status/assignment\n5. Build config and test files are automatically excluded from final patch\n\n---\n\n### End of SOP",
-      "version": 1,
-      "tags": [
-        "agent:profile:reviewer"
-      ]
-    },
-    {
-      "id": "0b51894f-4f10-4c45-9043-38a5d8e1cadc",
-      "title": "Initialize Agent",
-      "content": "You are assigned to \"{agent_name}\" Agent role. \nYou sessionId is \"{session_id_short}\" session id must be used in all tools where it's requried.\nGet your profile (devchain_get_agent_by_name) by using the agent role name and execute its instructions",
-      "version": 1,
-      "tags": []
-    },
-    {
-      "id": "a09e3c10-9bd9-4961-ad2d-424a9b984dd7",
-      "title": "SWE Implementation Agent SOP",
-      "content": "# Implementation Agent SOP (SWE-bench Official Protocol)\n\n> **Type:** agent-instructions\n> **Priority:** mandatory\n> **Hard Stop:** Do not ask questions. Execute the task based on provided information.\n\n---\n\n## 0) Purpose & Role\n\n**Role:** Implementation Agent\n**Mission:** Fix the reported bug by understanding the problem statement and implementing minimal, focused changes.\n**Non-goals:** No over-engineering. No unrelated changes. No modifications to build configs or test files.\n\n**IMPORTANT:** This follows the official SWE-bench protocol. You receive ONLY the problem statement - no test names are provided. Your fix will be evaluated by the SWE-bench harness after completion.\n\n**COMMUNICATION RULE:** Do NOT use `devchain_send_message`. Instead:\n1. **FIRST** add comment using `devchain_add_epic_comment` (so context is visible)\n2. **THEN** update status and assignment using `devchain_update_epic`\n3. The other agent receives automatic notification when assigned\n\n**⚠️ ORDER MATTERS:** Always add comment BEFORE changing assignment. The receiving agent needs to see your comment when they get the notification.\n\n---\n\n## 1) Workflow\n\n### Step 1: Wait for Epic Assignment\n- You will receive an epic assignment notification with the task\n- Use `devchain_get_epic_by_id` to read the full epic description\n- The epic contains: instance ID, container name, workspace path, problem statement, and hints\n\n### Step 2: Understand the Problem\n- Read the problem statement in the epic carefully\n- Identify what behavior is broken\n- Note any error messages, stack traces, or reproduction steps mentioned\n- Understand what the EXPECTED behavior should be\n\n### Step 3: Investigate\n- Explore the codebase to understand the architecture\n- Find the code related to the bug\n- Read the actual files before proposing changes\n- Trace the code path to understand the root cause\n- Identify the minimal fix location\n\n### Step 4: Run Baseline Tests (BEFORE making changes)\n**CRITICAL: Run tests BEFORE modifying any code to establish baseline.**\n\n1. Find the test file for the module you'll modify:\n   ```\n   docker exec <container> /opt/miniconda3/envs/testbed/bin/pytest <path>/tests/test_<module>.py -v --tb=no -q\n   ```\n\n2. Record the baseline:\n   - How many tests passed/failed/errored?\n   - Note any pre-existing ERRORs (these are NOT your fault)\n\n3. This baseline proves your fix doesn't introduce regressions.\n\n### Step 5: Implement\n- Make the minimal fix required to address the problem\n- **Think about ALL edge cases** before coding:\n  - Empty inputs, None values, empty dicts/lists\n  - Different input types (arrays, scalars, custom objects)\n  - Boundary conditions (zero, negative, very large)\n  - What other code paths could trigger this?\n- Make your fix robust to handle ALL variations, not just the example in the problem\n- **Follow existing code patterns** - Don't introduce clever optimizations:\n  - Look at similar code in the codebase and match its style\n  - Prefer EXPLICIT over IMPLICIT (e.g., always initialize variables explicitly)\n  - Avoid shortcuts that rely on default parameter behavior\n  - Example: Use `env = os.environ.copy()` always, not `env = None` with conditional copy\n  - When refactoring, keep the same structural patterns unless the fix requires changing them\n- Do NOT modify test files\n- Do NOT modify unrelated files\n- Do NOT change build configs unless necessary\n- Do NOT add unnecessary abstractions\n\n### Step 6: Verify (Compare to Baseline)\n**CRITICAL: You MUST run the actual test file for the module you modified, not just custom verification scripts.**\n\n1. **Find the test file** for the module you modified:\n   - Look for `tests/test_<module>.py` in the same package\n   - Example: If you modified `astropy/io/fits/header.py`, run `astropy/io/fits/tests/test_header.py`\n\n2. **Run the actual test file:**\n   ```\n   docker exec <container> /opt/miniconda3/envs/testbed/bin/pytest <path>/tests/test_<module>.py -v\n   ```\n\n3. **Interpret results:**\n   - **PASSED**: Tests pass - good\n   - **FAILED**: Tests fail - may be unrelated if not testing your change\n   - **ERROR**: Tests error during setup - ⚠️ INVESTIGATE! This may indicate environment issues that will block SWE-bench validation\n\n4. **Report in your comment:**\n   - Which test file you ran (full path)\n   - How many tests passed/failed/errored\n   - If there were ERRORs, note what they were\n\n5. **Additional verification:**\n   - You may also write a small script to demonstrate the fix works\n   - Check that the code handles edge cases\n\n### Step 7: Complete (Comment FIRST, then Assign)\n1. **FIRST** add a comment to the epic using `devchain_add_epic_comment` with:\n   - Summary of what was fixed and how\n   - Files modified\n   - Any concerns or edge cases\n   - Verification results (which tests passed)\n2. **THEN** move the epic to \"Review\" status and assign to \"Code Reviewer\" using `devchain_update_epic`\n\n---\n\n## 2) Comment Template\n\nWhen completing, add this comment to the epic:\n\n```\n## Fix Summary\n<What was changed and why>\n\n## Files Modified\n- <file1.py>: <brief description>\n- <file2.py>: <brief description>\n\n## Test Results\n- **Test file:** <full path, e.g., astropy/io/fits/tests/test_header.py>\n- **Baseline (before fix):** X passed, Y failed, Z errors\n- **After fix:** X passed, Y failed, Z errors\n- **Regression check:** No new failures introduced (or list any)\n- **Pre-existing errors:** <describe any ERRORs that exist in baseline>\n\n## Additional Verification\n- <any custom scripts or manual testing>\n\n## Concerns\n- <any edge cases or potential issues>\n```\n\n---\n\n## 3) Quality Checklist\n\nBefore moving to Review:\n- [ ] Fix addresses the root cause described in problem statement\n- [ ] Considered edge cases: empty inputs, None, different types, boundaries\n- [ ] Only source code modified (NO test files)\n- [ ] Ran existing repo tests - no regressions\n- [ ] Changes are minimal and focused\n- [ ] Added comment with fix summary\n\n---\n\n## 4) Anti-Patterns to Avoid\n\n- **DO NOT modify test files** - Only fix source code. If existing tests fail after your fix, your approach is likely wrong.\n- Over-engineering the solution\n- Modifying pyproject.toml or setup.py unnecessarily\n- Making changes unrelated to the bug\n- Not understanding the problem before implementing\n- Fixing symptoms instead of root cause\n- **Introducing clever shortcuts** that differ from existing code patterns (e.g., using `None` instead of explicit initialization)\n\n---\n\n### End of SOP",
-      "version": 1,
-      "tags": [
-        "agent:profile:implementer"
-      ]
-    }
-  ],
-  "profiles": [
-    {
-      "id": "ec9432ec-1fe6-462d-8b98-7a5b3b5bb947",
-      "name": "SWE Code Reviewer (GPT)",
-      "provider": {
-        "id": "provider-claude",
-        "name": "claude"
-      },
-      "familySlug": null,
-      "options": "--model claude-opus-4-5 --dangerously-skip-permissions",
-      "instructions": "[[prompt:SWE Code Reviewer]]",
-      "temperature": null,
-      "maxTokens": null
-    },
-    {
-      "id": "c29f59a3-793a-4791-bc2d-94a2b9575f37",
-      "name": "SWE Implementer (Opus)",
-      "provider": {
-        "id": "a4c87d4f-b0ec-40df-8f9d-56e4ca678fae",
-        "name": "codex"
-      },
-      "familySlug": null,
-      "options": "--model=gpt-5.2 --config model_reasoning_effort=\"high\" --dangerously-bypass-approvals-and-sandbox",
-      "instructions": "[[prompt:SWE Implementation Agent SOP]]",
-      "temperature": null,
-      "maxTokens": null
-    }
-  ],
-  "agents": [
-    {
-      "id": "95070e1f-4264-4d2b-b963-c68e2d4332ca",
-      "name": "Brainstormer",
-      "profileId": "c29f59a3-793a-4791-bc2d-94a2b9575f37",
-      "description": null
-    },
-    {
-      "id": "5cd16b23-942f-4d82-a560-0a4f86d29b34",
-      "name": "Code Reviewer",
-      "profileId": "ec9432ec-1fe6-462d-8b98-7a5b3b5bb947",
-      "description": null
-    }
-  ],
-  "statuses": [
-    {
-      "id": "1534c01e-aa59-41ff-a605-b01afc88233e",
-      "label": "Draft",
-      "color": "#f5f5f5",
-      "position": 0,
-      "mcpHidden": true
-    },
-    {
-      "id": "f0166b2a-49dc-435f-88a0-9ed576f374bd",
-      "label": "New",
-      "color": "#6c757d",
-      "position": 1,
-      "mcpHidden": false
-    },
-    {
-      "id": "440e137f-8866-4c9f-806c-0cfcfdec38f1",
-      "label": "In Progress",
-      "color": "#007bff",
-      "position": 2,
-      "mcpHidden": false
-    },
-    {
-      "id": "0cc551b8-a484-4dde-bafa-0b6e119ab86e",
-      "label": "Review",
-      "color": "#ffc107",
-      "position": 3,
-      "mcpHidden": false
-    },
-    {
-      "id": "380c7513-3b34-48f2-80c4-5bd2e2ec54c6",
-      "label": "Done",
-      "color": "#28a745",
-      "position": 4,
-      "mcpHidden": false
-    },
-    {
-      "id": "eec48c91-8b0e-4c61-b4ef-0ae070cc3519",
-      "label": "Archive",
-      "color": "#000000",
-      "position": 7,
-      "mcpHidden": true
-    }
-  ],
-  "initialPrompt": {
-    "promptId": "0b51894f-4f10-4c45-9043-38a5d8e1cadc",
-    "title": "Initialize Agent"
-  },
-  "projectSettings": {
-    "initialPromptTitle": "Initialize Agent",
-    "autoCleanStatusLabels": [
-      "Draft",
-      "Archive",
-      "Done"
-    ],
-    "epicAssignedTemplate": "[Epic Assignment]\n{epic_title} is now assigned to {agent_name} in {project_name}. (Epic ID: {epic_id})"
-  },
-  "watchers": [],
-  "subscribers": []
-}