cawdex 1.35.75 → 1.35.76

package/dist/autonomous-loops.js

@@ -9,32 +9,32 @@ import chalk from 'chalk';
  * Instructs the agent to review the PR, address comments, and re-review until approved.
  */
 export function buildPRLoopPrompt(cwd) {
-    return `You are a thorough code reviewer in an autonomous PR review loop.
-
-Working directory: ${cwd}
-
-Your task is to:
-1. Review the current PR changes
-2. Identify issues, improvements, or feedback
-3. Suggest fixes or clarifications
-4. After fixes are applied, re-review until you approve
-
-Loop Instructions:
-- On each iteration, provide clear, actionable feedback
-- Mark feedback as CRITICAL, MAJOR, or MINOR
-- Track which issues have been resolved
-- When all issues are resolved, respond with: "PR_APPROVED"
-- If no changes are made after feedback, respond with: "NO_CHANGES_DETECTED"
-- Maximum 5 iterations allowed
-
-Format your response as:
-\`\`\`
-## Review Iteration [N]
-### Issues Found:
-- [issue]: [description]
-
-### Approved: [yes/no]
-### Next Steps: [what needs fixing]
+    return `You are a thorough code reviewer in an autonomous PR review loop.
+
+Working directory: ${cwd}
+
+Your task is to:
+1. Review the current PR changes
+2. Identify issues, improvements, or feedback
+3. Suggest fixes or clarifications
+4. After fixes are applied, re-review until you approve
+
+Loop Instructions:
+- On each iteration, provide clear, actionable feedback
+- Mark feedback as CRITICAL, MAJOR, or MINOR
+- Track which issues have been resolved
+- When all issues are resolved, respond with: "PR_APPROVED"
+- If no changes are made after feedback, respond with: "NO_CHANGES_DETECTED"
+- Maximum 5 iterations allowed
+
+Format your response as:
+\`\`\`
+## Review Iteration [N]
+### Issues Found:
+- [issue]: [description]
+
+### Approved: [yes/no]
+### Next Steps: [what needs fixing]
 \`\`\``;
 }
 /**
@@ -45,31 +45,31 @@ export function buildSequentialPipelinePrompt(tasks) {
     const taskList = tasks
         .map((task, i) => `${i + 1}. ${task}`)
         .join('\n');
-    return `Execute the following tasks sequentially. Each task can reference the output of prior tasks.
-
-## Tasks:
-${taskList}
-
-## Execution Rules:
-- Run tasks in the specified order
-- Each task sees all prior outputs
-- After completing each task, summarize the result
-- If a task fails, explain the error and attempt recovery
-- Continue to the next task even if recovery is partial (unless critical)
-
-For each task, format your response:
-\`\`\`
-## Task [N]: [name]
-### Input from prior tasks: [summary or "none"]
-### Execution:
-[your work here]
-
-### Result:
-[clear summary of what was accomplished]
-
-### Status: [success/partial/failed]
-\`\`\`
-
+    return `Execute the following tasks sequentially. Each task can reference the output of prior tasks.
+
+## Tasks:
+${taskList}
+
+## Execution Rules:
+- Run tasks in the specified order
+- Each task sees all prior outputs
+- After completing each task, summarize the result
+- If a task fails, explain the error and attempt recovery
+- Continue to the next task even if recovery is partial (unless critical)
+
+For each task, format your response:
+\`\`\`
+## Task [N]: [name]
+### Input from prior tasks: [summary or "none"]
+### Execution:
+[your work here]
+
+### Result:
+[clear summary of what was accomplished]
+
+### Status: [success/partial/failed]
+\`\`\`
+
 After all tasks, provide a final summary of the entire pipeline.`;
 }
 /**
@@ -85,34 +85,34 @@ export function buildDAGPrompt(dag) {
         : dag.strategy === 'sequential'
             ? 'Run steps one at a time in dependency order.'
             : 'Run steps in topological layers for optimal parallelism.';
-    return `Execute the following task graph (DAG). Each step may depend on prior steps.
-
-## Task Graph:
-${stepList}
-
-## Strategy: ${dag.strategy}
-${strategyDescription}
-
-## Execution Rules:
-- Respect all dependency relationships
-- Skip a step if its dependency failed (mark as skipped)
-- For parallel execution, run independent steps concurrently
-- Capture the result of each step for dependent steps to use
-- On error, log clearly and continue (unless critical)
-
-For each step, format your response:
-\`\`\`
-## Step: [id] - [name]
-### Dependencies: [list of completed prior steps or "none"]
-### Execution:
-[your work here]
-
-### Result:
-[clear output]
-
-### Status: [success/skipped/failed]
-\`\`\`
-
+    return `Execute the following task graph (DAG). Each step may depend on prior steps.
+
+## Task Graph:
+${stepList}
+
+## Strategy: ${dag.strategy}
+${strategyDescription}
+
+## Execution Rules:
+- Respect all dependency relationships
+- Skip a step if its dependency failed (mark as skipped)
+- For parallel execution, run independent steps concurrently
+- Capture the result of each step for dependent steps to use
+- On error, log clearly and continue (unless critical)
+
+For each step, format your response:
+\`\`\`
+## Step: [id] - [name]
+### Dependencies: [list of completed prior steps or "none"]
+### Execution:
+[your work here]
+
+### Result:
+[clear output]
+
+### Status: [success/skipped/failed]
+\`\`\`
+
 After all steps, provide a final summary of the DAG execution.`;
 }
 /**
@@ -202,29 +202,29 @@ export function printDAGStatus(dag) {
  * Instructs the agent to break down a task into subtasks for parallel/sequential execution.
  */
 export function buildMultiPlanPrompt(task) {
-    return `Decompose the following task into 2-5 independent subtasks that can be executed in parallel or sequence:
-
-Task: ${task}
-
-For each subtask, provide:
-1. Subtask ID (e.g., "backend-setup")
-2. Subtask name
-3. Clear description of what to do
-4. Any dependencies on other subtasks (or "none")
-5. Estimated complexity: low/medium/high
-
-Format as JSON array:
-[
-  {
-    "id": "subtask-id",
-    "name": "Subtask Name",
-    "description": "What this subtask does",
-    "dependsOn": ["other-id"] or [],
-    "complexity": "low|medium|high"
-  },
-  ...
-]
-
+    return `Decompose the following task into 2-5 independent subtasks that can be executed in parallel or sequence:
+
+Task: ${task}
+
+For each subtask, provide:
+1. Subtask ID (e.g., "backend-setup")
+2. Subtask name
+3. Clear description of what to do
+4. Any dependencies on other subtasks (or "none")
+5. Estimated complexity: low/medium/high
+
+Format as JSON array:
+[
+  {
+    "id": "subtask-id",
+    "name": "Subtask Name",
+    "description": "What this subtask does",
+    "dependsOn": ["other-id"] or [],
+    "complexity": "low|medium|high"
+  },
+  ...
+]
+
 Only output the JSON, no explanation.`;
 }
 /**
@@ -232,29 +232,29 @@ Only output the JSON, no explanation.`;
  * Takes a JSON plan and generates execution instructions.
  */
 export function buildMultiExecutePrompt(plan) {
-    return `Execute the following task plan. Each subtask may have dependencies.
-
-## Plan:
-${plan}
-
-## Execution Instructions:
-1. Parse the plan to understand subtask dependencies
-2. Execute subtasks in order (respecting dependencies)
-3. For independent subtasks, you may mention running them in parallel
-4. After completing each subtask, summarize its result
-5. If a subtask fails, attempt recovery or skip dependent tasks
-6. Provide a final summary of all subtask results
-
-Format each subtask execution as:
-\`\`\`
-## Subtask: [id] - [name]
-### Execution:
-[your work]
-
-### Result:
-[output]
-
-### Status: [success/failed/skipped]
+    return `Execute the following task plan. Each subtask may have dependencies.
+
+## Plan:
+${plan}
+
+## Execution Instructions:
+1. Parse the plan to understand subtask dependencies
+2. Execute subtasks in order (respecting dependencies)
+3. For independent subtasks, you may mention running them in parallel
+4. After completing each subtask, summarize its result
+5. If a subtask fails, attempt recovery or skip dependent tasks
+6. Provide a final summary of all subtask results
+
+Format each subtask execution as:
+\`\`\`
+## Subtask: [id] - [name]
+### Execution:
+[your work]
+
+### Result:
+[output]
+
+### Status: [success/failed/skipped]
 \`\`\``;
 }
 /**
@@ -263,45 +263,45 @@ Format each subtask execution as:
  */
 export function buildMultiBackendPrompt(services) {
     const serviceList = services.map((s, i) => `${i + 1}. ${s}`).join('\n');
-    return `You are orchestrating changes across multiple backend services.
-
-## Services to coordinate:
-${serviceList}
-
-## Coordination Rules:
-1. Identify dependencies between services (if service A depends on service B, B must be updated first)
-2. Group changes by update type (API changes, database migrations, configuration)
-3. Create a safe update sequence that minimizes downtime
-4. For each service, specify:
-   - What changes are needed
-   - Any pre-requisites or migrations
-   - Testing strategy
-   - Rollback plan
-
-5. Consider:
-   - API compatibility (version gates if needed)
-   - Database schema compatibility
-   - Gradual rollout vs. big bang
-   - Health checks and monitoring
-
-Format your response:
-\`\`\`
-## Update Plan
-
-### Phase 1: Preparation
-- Service changes to make
-- Migrations to run
-- Infrastructure checks
-
-### Phase 2: Gradual Rollout
-- Service update order
-- Health checks between updates
-- Rollback triggers
-
-### Phase 3: Validation
-- Integration tests to run
-- Metrics to monitor
-- Success criteria
+    return `You are orchestrating changes across multiple backend services.
+
+## Services to coordinate:
+${serviceList}
+
+## Coordination Rules:
+1. Identify dependencies between services (if service A depends on service B, B must be updated first)
+2. Group changes by update type (API changes, database migrations, configuration)
+3. Create a safe update sequence that minimizes downtime
+4. For each service, specify:
+   - What changes are needed
+   - Any pre-requisites or migrations
+   - Testing strategy
+   - Rollback plan
+
+5. Consider:
+   - API compatibility (version gates if needed)
+   - Database schema compatibility
+   - Gradual rollout vs. big bang
+   - Health checks and monitoring
+
+Format your response:
+\`\`\`
+## Update Plan
+
+### Phase 1: Preparation
+- Service changes to make
+- Migrations to run
+- Infrastructure checks
+
+### Phase 2: Gradual Rollout
+- Service update order
+- Health checks between updates
+- Rollback triggers
+
+### Phase 3: Validation
+- Integration tests to run
+- Metrics to monitor
+- Success criteria
 \`\`\``;
 }
 /**
@@ -310,49 +310,49 @@ Format your response:
  */
 export function buildMultiFrontendPrompt(components) {
     const componentList = components.map((c, i) => `${i + 1}. ${c}`).join('\n');
-    return `You are orchestrating changes across multiple frontend components.
-
-## Components to coordinate:
-${componentList}
-
-## Coordination Rules:
-1. Map component dependencies (if ComponentA uses ComponentB, B must be updated first)
-2. Identify shared state or context that multiple components use
-3. Plan the update sequence to maintain app stability
-4. For each component, specify:
-   - Props/API changes needed
-   - State management updates
-   - CSS/styling updates
-   - Test coverage needed
-
-5. Consider:
-   - Backward compatibility (graceful degradation)
-   - Build system impact
-   - Bundle size implications
-   - Visual regression testing
-
-Format your response:
-\`\`\`
-## Component Update Plan
-
-### Dependency Graph
-[List component dependencies]
-
-### Update Sequence
-[Order of component updates]
-
-### Per-Component Changes
-For each component:
-- Props/API changes
-- State updates
-- Styling updates
-- Tests to add/update
-
-### Integration Testing
-[How to verify components work together]
-
-### Rollback Plan
-[If something breaks]
+    return `You are orchestrating changes across multiple frontend components.
+
+## Components to coordinate:
+${componentList}
+
+## Coordination Rules:
+1. Map component dependencies (if ComponentA uses ComponentB, B must be updated first)
+2. Identify shared state or context that multiple components use
+3. Plan the update sequence to maintain app stability
+4. For each component, specify:
+   - Props/API changes needed
+   - State management updates
+   - CSS/styling updates
+   - Test coverage needed
+
+5. Consider:
+   - Backward compatibility (graceful degradation)
+   - Build system impact
+   - Bundle size implications
+   - Visual regression testing
+
+Format your response:
+\`\`\`
+## Component Update Plan
+
+### Dependency Graph
+[List component dependencies]
+
+### Update Sequence
+[Order of component updates]
+
+### Per-Component Changes
+For each component:
+- Props/API changes
+- State updates
+- Styling updates
+- Tests to add/update
+
+### Integration Testing
+[How to verify components work together]
+
+### Rollback Plan
+[If something breaks]
 \`\`\``;
 }
 /**
@@ -361,33 +361,33 @@ For each component:
  */
 export function buildLoopOperatorPrompt(task, loopType) {
     const loopInstructions = getLoopTypeInstructions(loopType);
-    return `You are running an autonomous loop of type: ${loopType}
-
-Task: ${task}
-
-## Loop Operating System:
-${loopInstructions}
-
-## General Loop Rules:
-1. Each iteration, perform the loop action and evaluate the stopping condition
-2. If the stopping condition is met, output "LOOP_COMPLETE" and summarize
-3. If the stopping condition is not met, iterate again
-4. Maximum 10 iterations allowed (unless specified otherwise)
-5. After each iteration, provide a status update
-
-Format each iteration as:
-\`\`\`
-## Iteration [N]
-### Action:
-[what you did]
-
-### Evaluation:
-[did the stopping condition pass?]
-
-### Status:
-[continue/complete]
-\`\`\`
-
+    return `You are running an autonomous loop of type: ${loopType}
+
+Task: ${task}
+
+## Loop Operating System:
+${loopInstructions}
+
+## General Loop Rules:
+1. Each iteration, perform the loop action and evaluate the stopping condition
+2. If the stopping condition is met, output "LOOP_COMPLETE" and summarize
+3. If the stopping condition is not met, iterate again
+4. Maximum 10 iterations allowed (unless specified otherwise)
+5. After each iteration, provide a status update
+
+Format each iteration as:
+\`\`\`
+## Iteration [N]
+### Action:
+[what you did]
+
+### Evaluation:
+[did the stopping condition pass?]
+
+### Status:
+[continue/complete]
+\`\`\`
+
 After loop completion, provide a final summary.`;
 }
 /**
@@ -395,65 +395,65 @@ After loop completion, provide a final summary.`;
  */
 function getLoopTypeInstructions(loopType) {
     const instructions = {
-        verification: `
-This is a VERIFICATION LOOP:
-1. Run tests for the target code
-2. If tests pass, stopping condition is met (LOOP_COMPLETE)
-3. If tests fail, identify the issue and propose a fix
-4. Apply the fix and re-run tests
-5. Iterate until tests pass or max iterations reached
+        verification: `
+This is a VERIFICATION LOOP:
+1. Run tests for the target code
+2. If tests pass, stopping condition is met (LOOP_COMPLETE)
+3. If tests fail, identify the issue and propose a fix
+4. Apply the fix and re-run tests
+5. Iterate until tests pass or max iterations reached
     `,
-        review: `
-This is a REVIEW LOOP:
-1. Review the current state/code/design
-2. Identify issues, gaps, or improvements
-3. If no issues found, stopping condition is met (LOOP_COMPLETE)
-4. If issues found, address them one by one
-5. Re-review after fixes and iterate until all issues resolved
+        review: `
+This is a REVIEW LOOP:
+1. Review the current state/code/design
+2. Identify issues, gaps, or improvements
+3. If no issues found, stopping condition is met (LOOP_COMPLETE)
+4. If issues found, address them one by one
+5. Re-review after fixes and iterate until all issues resolved
     `,
-        exploration: `
-This is an EXPLORATION LOOP:
-1. Explore the current state to understand it
-2. Ask clarifying questions or gather information
-3. If sufficient understanding is achieved, stopping condition is met (LOOP_COMPLETE)
-4. If gaps remain, dig deeper or investigate specific areas
-5. Repeat until you have a complete mental model
+        exploration: `
+This is an EXPLORATION LOOP:
+1. Explore the current state to understand it
+2. Ask clarifying questions or gather information
+3. If sufficient understanding is achieved, stopping condition is met (LOOP_COMPLETE)
+4. If gaps remain, dig deeper or investigate specific areas
+5. Repeat until you have a complete mental model
     `,
-        convergence: `
-This is a CONVERGENCE LOOP:
-1. Generate or refine a solution
-2. Evaluate it against criteria
-3. If it meets all criteria, stopping condition is met (LOOP_COMPLETE)
-4. If gaps remain, identify what needs improvement
-5. Refine the solution and re-evaluate
-6. Iterate until solution converges to acceptable quality
+        convergence: `
+This is a CONVERGENCE LOOP:
+1. Generate or refine a solution
+2. Evaluate it against criteria
+3. If it meets all criteria, stopping condition is met (LOOP_COMPLETE)
+4. If gaps remain, identify what needs improvement
+5. Refine the solution and re-evaluate
+6. Iterate until solution converges to acceptable quality
     `,
-        debugging: `
-This is a DEBUGGING LOOP:
-1. Identify the symptom or error
-2. Form a hypothesis about the root cause
-3. Test the hypothesis with evidence
-4. If confirmed, stopping condition is met (LOOP_COMPLETE)
-5. If not confirmed, form a new hypothesis
-6. Iterate until root cause is identified and explained
+        debugging: `
+This is a DEBUGGING LOOP:
+1. Identify the symptom or error
+2. Form a hypothesis about the root cause
+3. Test the hypothesis with evidence
+4. If confirmed, stopping condition is met (LOOP_COMPLETE)
+5. If not confirmed, form a new hypothesis
+6. Iterate until root cause is identified and explained
     `,
-        optimization: `
-This is an OPTIMIZATION LOOP:
-1. Measure the current performance or quality metric
-2. Identify opportunities to improve
-3. Apply an optimization
-4. Re-measure and check for improvement
-5. If metric reaches target, stopping condition is met (LOOP_COMPLETE)
-6. If not, apply another optimization
-7. Iterate until target is reached or diminishing returns found
+        optimization: `
+This is an OPTIMIZATION LOOP:
+1. Measure the current performance or quality metric
+2. Identify opportunities to improve
+3. Apply an optimization
+4. Re-measure and check for improvement
+5. If metric reaches target, stopping condition is met (LOOP_COMPLETE)
+6. If not, apply another optimization
+7. Iterate until target is reached or diminishing returns found
     `,
-        default: `
-This is a GENERIC AUTONOMOUS LOOP:
-1. On each iteration, work toward the task goal
-2. Evaluate progress: Are you closer to completion?
-3. If task is complete, stopping condition is met (LOOP_COMPLETE)
-4. If not, identify next steps and continue
-5. Iterate until task is complete or max iterations reached
+        default: `
+This is a GENERIC AUTONOMOUS LOOP:
+1. On each iteration, work toward the task goal
+2. Evaluate progress: Are you closer to completion?
+3. If task is complete, stopping condition is met (LOOP_COMPLETE)
+4. If not, identify next steps and continue
+5. Iterate until task is complete or max iterations reached
     `,
     };
     return instructions[loopType] || instructions['default'];