xforce 0.1.2 → 0.1.4

package/dist/cli/index.js

@@ -892,22 +892,31 @@ Fix the code to make the ${kind} pass. Do not commit \u2014 the pipeline handles
 // src/agents/prompts/planner-system.ts
 var PLANNER_SYSTEM_PROMPT = `You are a senior software architect analyzing a codebase to create an implementation plan.
 
-You have access to read-only tools: Read, Glob, and Grep. Use them to:
-1. Explore the repository structure (Glob for file patterns, Read for file contents)
-2. Understand existing patterns, conventions, and architecture
-3. Identify the exact files that need to be modified or created
-4. Analyze dependencies and potential ripple effects
+You have access to read-only tools: Read, Glob, and Grep. Use them to explore the repository before planning.
 
-RULES:
-- Start by quickly checking the project structure (Glob for key file patterns). If the repo is empty or has very few files, skip deep exploration and produce your plan immediately.
-- Be specific about file paths \u2014 use actual paths you found in the codebase, or specify paths to create for greenfield projects.
+## TURN BUDGET \u2014 CRITICAL
+You have a LIMITED number of turns. You MUST produce your JSON plan well before you run out.
+
+- **Small/empty repos** (< 20 files): Spend 1-3 turns exploring, then output your plan.
+- **Medium repos** (20-100 files): Spend 3-8 turns exploring, then output your plan.
+- **Large repos** (100+ files): Spend at most 10-15 turns exploring, then output your plan.
+
+If you are unsure whether you've explored enough, STOP EXPLORING AND OUTPUT YOUR PLAN. An incomplete plan is infinitely better than no plan at all. The coder agent will adapt.
+
+## EXPLORATION STRATEGY
+1. Start with a broad Glob (e.g. \`**/*.{ts,tsx,js,jsx,py}\`) to understand project size and structure.
+2. Read key files: package.json, config files, entry points.
+3. Grep for patterns relevant to the task.
+4. Stop exploring once you understand the project structure and relevant patterns.
+
+## PLAN QUALITY
+- Be specific about file paths \u2014 use actual paths from the codebase, or specify paths to create.
 - Consider test files and their patterns.
 - Identify potential risks (breaking changes, missing test coverage, security).
 - Estimate complexity honestly.
 - Your plan should be actionable and concrete, not vague.
-- Do NOT spend more than a few turns exploring. Produce your JSON plan as quickly as possible.
 
-You MUST respond with valid JSON matching the required schema.`;
+You MUST respond with valid JSON matching the required schema. Do NOT wrap it in markdown fences.`;
 function buildPlannerPrompt(taskSpec) {
   return `## Task: ${taskSpec.title}
 
@@ -1115,39 +1124,6 @@ var ImplementationPlanSchema = z2.object({
   implementationSteps: z2.array(ImplementationStepSchema),
   estimatedTurns: z2.number().int().positive()
 });
-var PLAN_JSON_SCHEMA = {
-  type: "object",
-  properties: {
-    approach: { type: "string" },
-    filesToModify: { type: "array", items: { type: "string" } },
-    filesToCreate: { type: "array", items: { type: "string" } },
-    estimatedComplexity: { type: "string", enum: ["low", "medium", "high"] },
-    risks: { type: "array", items: { type: "string" } },
-    implementationSteps: {
-      type: "array",
-      items: {
-        type: "object",
-        properties: {
-          order: { type: "number" },
-          description: { type: "string" },
-          files: { type: "array", items: { type: "string" } },
-          rationale: { type: "string" }
-        },
-        required: ["order", "description", "files", "rationale"]
-      }
-    },
-    estimatedTurns: { type: "number" }
-  },
-  required: [
-    "approach",
-    "filesToModify",
-    "filesToCreate",
-    "estimatedComplexity",
-    "risks",
-    "implementationSteps",
-    "estimatedTurns"
-  ]
-};
 function extractJSON(text) {
   const jsonMatch = text.match(/\{[\s\S]*\}/);
   if (jsonMatch) return jsonMatch[0];
@@ -1181,10 +1157,6 @@ async function runPlanningAgent(params) {
       permissionMode: "bypassPermissions",
       allowDangerouslySkipPermissions: true,
       systemPrompt: PLANNER_SYSTEM_PROMPT,
-      outputFormat: {
-        type: "json_schema",
-        schema: PLAN_JSON_SCHEMA
-      },
       stderr: (data) => {
         stderrOutput += data;
         log6.debug({ stderr: data.trimEnd() }, "Agent SDK stderr");
@@ -1229,7 +1201,8 @@ ${stderrOutput.slice(0, 2e3)}` : "";
   log6.debug(
     {
       subtype: resultMessage.subtype,
-      hasStructuredOutput: "structured_output" in resultMessage && !!resultMessage.structured_output,
+      numTurns: resultMessage.num_turns,
+      costUsd: resultMessage.total_cost_usd,
       hasResult: "result" in resultMessage && !!resultMessage.result,
       hasLastAssistant: !!lastAssistantText,
       lastAssistantLength: lastAssistantText.length