@benzotti/jedi 0.1.12 → 0.1.13

package/dist/index.js

@@ -9250,7 +9250,7 @@ async function copyFrameworkFiles(cwd, projectType, force, ci = false) {
   const frameworkDest = join2(cwd, ".jdi", "framework");
   const glob = new Bun.Glob("**/*");
   for await (const file of glob.scan({ cwd: frameworkDir })) {
-    if (file.startsWith("adapters/") || file.startsWith("commands/"))
+    if (file.startsWith("adapters/"))
       continue;
     const src2 = join2(frameworkDir, file);
     const dest = join2(frameworkDest, file);
@@ -9366,6 +9366,8 @@ Recognise natural language JDI intents and invoke the matching skill via the Ski
 
 Extract flags from context: "in a worktree" \u2192 \`--worktree\`, "lightweight" \u2192 \`--worktree-lightweight\`, "single agent" \u2192 \`--single\`, "use teams" \u2192 \`--team\`. If the intent is unclear, ask. Never guess.
 
+Planning and implementation are separate gates \u2014 NEVER auto-proceed to implementation after plan approval.
+
 ## Iterative Refinement
 
 After \`/jdi:create-plan\` or \`/jdi:implement-plan\` completes, the conversation continues naturally \u2014 no new command invocation needed. When the user provides feedback (e.g. "change task 2", "move this to a helper", "add error handling"), apply the changes directly, update state, and present the updated summary. When the user approves (e.g. "approved", "looks good", "lgtm"), finalise the review state. The conversation IS the feedback loop.
@@ -9388,6 +9390,8 @@ Recognise natural language JDI intents and invoke the matching skill via the Ski
 
 Extract flags from context: "in a worktree" \u2192 \`--worktree\`, "lightweight" \u2192 \`--worktree-lightweight\`, "single agent" \u2192 \`--single\`, "use teams" \u2192 \`--team\`. If the intent is unclear, ask. Never guess.
 
+Planning and implementation are separate gates \u2014 NEVER auto-proceed to implementation after plan approval.
+
 ## Iterative Refinement
 
 After \`/jdi:create-plan\` or \`/jdi:implement-plan\` completes, the conversation continues naturally \u2014 no new command invocation needed. When the user provides feedback (e.g. "change task 2", "move this to a helper", "add error handling"), apply the changes directly, update state, and present the updated summary. When the user approves (e.g. "approved", "looks good", "lgtm"), finalise the review state. The conversation IS the feedback loop.
@@ -11514,7 +11518,7 @@ var setupActionCommand = defineCommand({
 // package.json
 var package_default = {
   name: "@benzotti/jedi",
-  version: "0.1.12",
+  version: "0.1.13",
   description: "JDI - Context-efficient AI development framework for Claude Code",
   type: "module",
   bin: {

package/framework/commands/create-plan.md

@@ -27,6 +27,6 @@ Create an implementation plan using a single planner agent (includes research).
 9. **Present summary** (name, objective, task table, files) then ask: _"Provide feedback to refine, or say **approved** to finalise."_
 10. **Review loop**: approval → update state to `"approved"`, confirm. Feedback → revise plan in-place, increment revision, re-present summary. Repeat until approved. This is natural conversation — no separate command needed.
 
-Agent base (read FIRST for cache): ./components/meta/AgentBase.md | Agent spec: ./agents/jdi-planner.md
+Agent base (read FIRST for cache): .jdi/framework/components/meta/AgentBase.md | Agent spec: .jdi/framework/agents/jdi-planner.md
 
 Feature to plan: $ARGUMENTS

package/framework/commands/implement-plan.md

@@ -26,8 +26,8 @@ Execute a PLAN.md with complexity-based routing.
 11. **Present summary** (tasks completed, files changed, verification results, deviations) then ask: _"Provide feedback to adjust, or say **approved** to finalise."_
 12. **Review loop**: approval → update state to `"complete"`, suggest commit/PR. Feedback → apply code changes, run tests, increment revision, re-present. Repeat until approved. Natural conversation — no separate command needed.
 
-Agent base (read FIRST for cache): ./components/meta/AgentBase.md | Agent specs: ./agents/jdi-backend.md, ./agents/jdi-frontend.md
-Orchestration: ./components/meta/AgentTeamsOrchestration.md | Routing: ./components/meta/ComplexityRouter.md
+Agent base (read FIRST for cache): .jdi/framework/components/meta/AgentBase.md | Agent specs: .jdi/framework/agents/jdi-backend.md, .jdi/framework/agents/jdi-frontend.md
+Orchestration: .jdi/framework/components/meta/AgentTeamsOrchestration.md | Routing: .jdi/framework/components/meta/ComplexityRouter.md
 
 When spawning agents, detect project type and include a `## Project Context` block (type, tech stack, quality gates, working directory) in the spawn prompt. This saves agents 2-3 discovery tool calls.
 

package/framework/commands/worktree-remove.md

@@ -27,6 +27,6 @@ Remove a git worktree and clean up all associated resources.
 7. **Update state**: set `worktree.active: false`, clear `worktree.path`, `worktree.branch` in `.jdi/config/state.yaml`
 8. **Report**: what was removed
 
-Reference: ./hooks/jdi-worktree-cleanup.md
+Reference: .jdi/framework/hooks/jdi-worktree-cleanup.md
 
 Worktree to remove: $ARGUMENTS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@benzotti/jedi",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "JDI - Context-efficient AI development framework for Claude Code",
   "type": "module",
   "bin": {