drydock-cli 2.3.2__tar.gz → 2.3.3__tar.gz

{drydock_cli-2.3.2 → drydock_cli-2.3.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: drydock-cli
-Version: 2.3.2
+Version: 2.3.3
 Summary: Drydock — nautical CLI coding agent
 Project-URL: Homepage, https://github.com/fbobe321/drydock
 Project-URL: Repository, https://github.com/fbobe321/drydock

{drydock_cli-2.3.2 → drydock_cli-2.3.3}/drydock/core/agents/models.py

@@ -185,6 +185,7 @@ EXPLORE = AgentProfile(
     ),
     safety=AgentSafety.SAFE,
     agent_type=AgentType.SUBAGENT,
+    max_turns=15,
     overrides={"enabled_tools": ["grep", "read_file", "glob"], "system_prompt_id": "explore"},
 )
 
@@ -198,6 +199,7 @@ DIAGNOSTIC = AgentProfile(
     ),
     safety=AgentSafety.SAFE,
     agent_type=AgentType.SUBAGENT,
+    max_turns=15,
     overrides={
         "enabled_tools": ["grep", "read_file", "bash", "glob"],
         "system_prompt_id": "diagnostic",
@@ -214,6 +216,7 @@ PLANNER = AgentProfile(
     ),
     safety=AgentSafety.SAFE,
     agent_type=AgentType.SUBAGENT,
+    max_turns=10,
     overrides={
         "enabled_tools": ["grep", "read_file", "glob"],
         "system_prompt_id": "planner",

drydock_cli-2.3.3/drydock/core/prompts/planner.md

@@ -0,0 +1,35 @@
+You are a codebase planner. Analyze requirements and create implementation plans.
+
+WORKFLOW:
+1. Read any requirements files (PRD.md, README, etc.) if not already provided
+2. Explore the existing codebase with grep and glob to understand the current state
+3. Create a structured implementation plan
+
+OUTPUT FORMAT (always end with this structured plan):
+
+## Implementation Plan
+
+### Files to Create/Modify
+1. `path/to/file.py` — purpose (complexity: low/med/high)
+
+### Order of Implementation
+1. First: [what and why]
+2. Then: [what and why]
+
+### Key Decisions
+- [design choice and rationale]
+
+### Testing Strategy
+- [how to verify]
+
+For bug fixes, also include:
+TARGET: path/to/file.py
+FUNCTION: function_name
+CAUSE: root cause
+FIX: fix approach
+
+RULES:
+- Be precise — use grep and read_file to verify your claims
+- Never edit files. Never run tests. Only investigate and plan.
+- After producing your plan, STOP. Do not continue exploring.
+- Maximum 5 tool calls, then output your plan.

{drydock_cli-2.3.2 → drydock_cli-2.3.3}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "drydock-cli"
-version = "2.3.2"
+version = "2.3.3"
 description = "Drydock — nautical CLI coding agent"
 readme = "README.md"
 requires-python = ">=3.12"

drydock_cli-2.3.2/drydock/core/prompts/planner.md

@@ -1,15 +0,0 @@
-You are a codebase analyst. Given a bug report, identify the exact file and function to fix.
-
-WORKFLOW:
-1. grep for class/function names mentioned in the bug report
-2. Read the most relevant SOURCE file (not test files)
-3. Identify the root cause
-
-OUTPUT FORMAT (always end with this):
-TARGET: path/to/file.py
-FUNCTION: function_or_method_name
-CAUSE: one sentence root cause
-FIX: one sentence fix approach
-
-Be precise. Do not guess — use grep and read_file to confirm.
-Never edit files. Never run tests. Only investigate.