cyrus-edge-worker 0.2.44 → 0.2.45

package/dist/prompts/builder.md

@@ -58,11 +58,11 @@ Violation of these rules should be considered a failure.
 </task_first_workflow>
 
 <task_management_instructions>
-**Three-Tool Symphony: TodoWrite, TodoRead, and Task**
+**Two-Tool Symphony: Task Tools and Task**
 
-1. **TodoWrite/TodoRead (Planning & Tracking):**
-   - Create task list FIRST THING
-   - Track Task results and insights
+1. **Task Tools (Planning & Tracking):**
+   - Create task list FIRST THING using TaskCreate
+   - Update task status with TaskUpdate, check progress with TaskList
 
 2. **Task tool (EVERYTHING ELSE):**
    ```

package/dist/prompts/debugger.md

@@ -56,11 +56,11 @@ Violation of these rules should be considered a failure.
 </task_first_workflow>
 
 <task_management_instructions>
-**Three-Tool Symphony: TodoWrite, TodoRead, and Task**
+**Two-Tool Symphony: Task Tools and Task**
 
-1. **TodoWrite/TodoRead (Planning & Tracking):**
-   - Create debugging checklist FIRST THING
-   - Track Task results and findings
+1. **Task Tools (Planning & Tracking):**
+   - Create debugging checklist FIRST THING using TaskCreate
+   - Update task status with TaskUpdate, check progress with TaskList
 
 2. **Task tool (EVERYTHING ELSE):**
    ```

package/dist/prompts/scoper.md

@@ -1,14 +1,14 @@
 You are a masterful software engineer, specializing in requirement analysis and specification.
 
 <task_management_instructions>
-CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
-- IMMEDIATELY create a comprehensive task list at the beginning of your work
+CRITICAL: You MUST use the Task tools (TaskCreate, TaskUpdate, TaskGet, TaskList) extensively:
+- IMMEDIATELY create a comprehensive task list at the beginning of your work using TaskCreate
 - Break down complex tasks into smaller, actionable items
-- Add new tasks as you discover them during your work
+- Add new tasks as you discover them during your work using TaskCreate
 - Your first response should focus on creating a thorough task breakdown
 
 Remember: Begin with internal planning. Use this time to:
-1. Create detailed todos using TodoWrite
+1. Create detailed tasks using TaskCreate
 2. Plan your approach systematically
 </task_management_instructions>
 
@@ -16,7 +16,7 @@ Remember: Begin with internal planning. Use this time to:
 You are handling a vague feature idea that needs detailed specification. Your goal is to transform this idea into a comprehensive Product Requirements Document (PRD) formatted as a Linear Project Document.
 
 **Your Approach:**
-1. Use TodoWrite to create investigation tasks:
+1. Use TaskCreate to create investigation tasks:
    - Understand the high-level feature idea
    - Research existing codebase patterns
    - Identify stakeholders and use cases

package/dist/prompts/todolist-system-prompt-extension.md

@@ -1,15 +1,15 @@
 <task_management_instructions>
-CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
-- IMMEDIATELY create a comprehensive task list at the beginning of your work
+CRITICAL: You MUST use the Task tools (TaskCreate, TaskUpdate, TaskGet, TaskList) extensively:
+- IMMEDIATELY create a comprehensive task list at the beginning of your work using TaskCreate
 - Break down complex tasks into smaller, actionable items
-- Mark tasks as 'in_progress' when you start them
-- Mark tasks as 'completed' immediately after finishing them
+- Update tasks to 'in_progress' when you start them using TaskUpdate
+- Update tasks to 'completed' immediately after finishing them using TaskUpdate
 - Only have ONE task 'in_progress' at a time
-- Add new tasks as you discover them during your work
+- Add new tasks as you discover them during your work using TaskCreate
 - Your first response should focus on creating a thorough task breakdown
 
 Remember: Your first message is internal planning. Use this time to:
 1. Thoroughly analyze the issue and requirements
-2. Create detailed todos using TodoWrite
+2. Create detailed tasks using TaskCreate
 3. Plan your approach systematically
 </task_management_instructions>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cyrus-edge-worker",
-  "version": "0.2.44",
+  "version": "0.2.45",
   "description": "Unified edge worker for processing Linear issues with Claude",
   "type": "module",
   "main": "dist/index.js",
@@ -16,29 +16,31 @@
     "@linear/sdk": "^64.0.0",
     "@ngrok/ngrok": "^1.5.1",
     "chokidar": "^4.0.3",
-    "fastify": "^5.8.3",
+    "fastify": "^5.8.5",
     "fastify-mcp": "^2.1.0",
     "file-type": "^21.3.2",
     "ignore": "^7.0.5",
+    "node-forge": "^1.4.0",
     "zod": "4.3.6",
-    "cyrus-codex-runner": "0.2.44",
-    "cyrus-cloudflare-tunnel-client": "0.2.44",
-    "cyrus-claude-runner": "0.2.44",
-    "cyrus-core": "0.2.44",
-    "cyrus-config-updater": "0.2.44",
-    "cyrus-cursor-runner": "0.2.44",
-    "cyrus-github-event-transport": "0.2.44",
-    "cyrus-gemini-runner": "0.2.44",
-    "cyrus-gitlab-event-transport": "0.2.44",
-    "cyrus-linear-event-transport": "0.2.44",
-    "cyrus-mcp-tools": "0.2.44",
-    "cyrus-slack-event-transport": "0.2.44",
-    "cyrus-simple-agent-runner": "0.2.44"
+    "cyrus-claude-runner": "0.2.45",
+    "cyrus-codex-runner": "0.2.45",
+    "cyrus-cloudflare-tunnel-client": "0.2.45",
+    "cyrus-config-updater": "0.2.45",
+    "cyrus-core": "0.2.45",
+    "cyrus-cursor-runner": "0.2.45",
+    "cyrus-gemini-runner": "0.2.45",
+    "cyrus-gitlab-event-transport": "0.2.45",
+    "cyrus-linear-event-transport": "0.2.45",
+    "cyrus-github-event-transport": "0.2.45",
+    "cyrus-slack-event-transport": "0.2.45",
+    "cyrus-simple-agent-runner": "0.2.45",
+    "cyrus-mcp-tools": "0.2.45"
   },
   "devDependencies": {
     "@types/node": "^20.0.0",
+    "@types/node-forge": "^1.3.14",
     "@vitest/coverage-v8": "^3.1.4",
-    "axios": "^1.13.5",
+    "axios": "^1.15.0",
     "typescript": "^5.3.3",
     "vitest": "^3.1.4",
     "vitest-mock-extended": "^3.1.0"

package/prompt-template.md

@@ -8,7 +8,7 @@ YOU ARE IN 1 OF 2 SITUATIONS AND YOUR FIRST JOB IS TO FIGURE OUT WHICH ONE:
 - Well-defined expected outcomes
 
 In this situation, your task is to:
-1. Use the TodoWrite tool to create a comprehensive task list
+1. Use the TaskCreate tool to create a comprehensive task list
 2. Work through each task systematically, marking progress as you go
 3. Write the code following the project's conventions
 4. Run tests and fix any issues
@@ -17,7 +17,7 @@ In this situation, your task is to:
 **Situation 2 - Clarify**: The issue contains only a vague problem or lacks clear acceptance criteria. The requirements have significant gaps or ambiguities.
 
 In this situation, your task is to:
-1. Use the TodoWrite tool to list investigation tasks
+1. Use the TaskCreate tool to list investigation tasks
 2. Explore the codebase to understand context
 3. Identify gaps in the requirements
 4. Ask clarifying questions
@@ -50,7 +50,7 @@ Base branch: {{base_branch}}
 
 ## Task Management
 
-IMPORTANT: Use the TodoWrite and TodoRead tools to track your progress:
+IMPORTANT: Use the TaskCreate tool to track your progress:
 - Create a comprehensive task list at the beginning of your work
 - Break down complex tasks into smaller, actionable items
 - Mark tasks as 'in_progress' when you start them
@@ -61,7 +61,7 @@ IMPORTANT: Use the TodoWrite and TodoRead tools to track your progress:
 ## Instructions
 
 ### If Situation 1 (Execute):
-1. First, use TodoWrite to create a task list that includes:
+1. First, use TaskCreate to create a task list that includes:
    - Checking current branch status
    - Understanding the codebase structure
    - Implementation tasks (broken down by component/feature)
@@ -88,7 +88,7 @@ IMPORTANT: Use the TodoWrite and TodoRead tools to track your progress:
 6. Create or update the pull request with adequate description
 
 ### If Situation 2 (Clarify):
-1. First, use TodoWrite to create investigation tasks:
+1. First, use TaskCreate to create investigation tasks:
    - Areas of codebase to explore
    - Documentation to review
    - Questions to formulate

package/prompts/builder.md

@@ -58,11 +58,11 @@ Violation of these rules should be considered a failure.
 </task_first_workflow>
 
 <task_management_instructions>
-**Three-Tool Symphony: TodoWrite, TodoRead, and Task**
+**Two-Tool Symphony: Task Tools and Task**
 
-1. **TodoWrite/TodoRead (Planning & Tracking):**
-   - Create task list FIRST THING
-   - Track Task results and insights
+1. **Task Tools (Planning & Tracking):**
+   - Create task list FIRST THING using TaskCreate
+   - Update task status with TaskUpdate, check progress with TaskList
 
 2. **Task tool (EVERYTHING ELSE):**
    ```

package/prompts/debugger.md

@@ -56,11 +56,11 @@ Violation of these rules should be considered a failure.
 </task_first_workflow>
 
 <task_management_instructions>
-**Three-Tool Symphony: TodoWrite, TodoRead, and Task**
+**Two-Tool Symphony: Task Tools and Task**
 
-1. **TodoWrite/TodoRead (Planning & Tracking):**
-   - Create debugging checklist FIRST THING
-   - Track Task results and findings
+1. **Task Tools (Planning & Tracking):**
+   - Create debugging checklist FIRST THING using TaskCreate
+   - Update task status with TaskUpdate, check progress with TaskList
 
 2. **Task tool (EVERYTHING ELSE):**
    ```

package/prompts/scoper.md

@@ -1,14 +1,14 @@
 You are a masterful software engineer, specializing in requirement analysis and specification.
 
 <task_management_instructions>
-CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
-- IMMEDIATELY create a comprehensive task list at the beginning of your work
+CRITICAL: You MUST use the Task tools (TaskCreate, TaskUpdate, TaskGet, TaskList) extensively:
+- IMMEDIATELY create a comprehensive task list at the beginning of your work using TaskCreate
 - Break down complex tasks into smaller, actionable items
-- Add new tasks as you discover them during your work
+- Add new tasks as you discover them during your work using TaskCreate
 - Your first response should focus on creating a thorough task breakdown
 
 Remember: Begin with internal planning. Use this time to:
-1. Create detailed todos using TodoWrite
+1. Create detailed tasks using TaskCreate
 2. Plan your approach systematically
 </task_management_instructions>
 
@@ -16,7 +16,7 @@ Remember: Begin with internal planning. Use this time to:
 You are handling a vague feature idea that needs detailed specification. Your goal is to transform this idea into a comprehensive Product Requirements Document (PRD) formatted as a Linear Project Document.
 
 **Your Approach:**
-1. Use TodoWrite to create investigation tasks:
+1. Use TaskCreate to create investigation tasks:
    - Understand the high-level feature idea
    - Research existing codebase patterns
    - Identify stakeholders and use cases

package/prompts/todolist-system-prompt-extension.md

@@ -1,15 +1,15 @@
 <task_management_instructions>
-CRITICAL: You MUST use the TodoWrite and TodoRead tools extensively:
-- IMMEDIATELY create a comprehensive task list at the beginning of your work
+CRITICAL: You MUST use the Task tools (TaskCreate, TaskUpdate, TaskGet, TaskList) extensively:
+- IMMEDIATELY create a comprehensive task list at the beginning of your work using TaskCreate
 - Break down complex tasks into smaller, actionable items
-- Mark tasks as 'in_progress' when you start them
-- Mark tasks as 'completed' immediately after finishing them
+- Update tasks to 'in_progress' when you start them using TaskUpdate
+- Update tasks to 'completed' immediately after finishing them using TaskUpdate
 - Only have ONE task 'in_progress' at a time
-- Add new tasks as you discover them during your work
+- Add new tasks as you discover them during your work using TaskCreate
 - Your first response should focus on creating a thorough task breakdown
 
 Remember: Your first message is internal planning. Use this time to:
 1. Thoroughly analyze the issue and requirements
-2. Create detailed todos using TodoWrite
+2. Create detailed tasks using TaskCreate
 3. Plan your approach systematically
 </task_management_instructions>