gsd-pi 2.14.0 → 2.14.2

package/dist/resources/extensions/gsd/auto.ts

@@ -335,10 +335,12 @@ function startDispatchGapWatchdog(ctx: ExtensionContext, pi: ExtensionAPI): void
 
     // Auto-mode is active but no unit was dispatched — the state machine stalled.
     // Re-derive state and attempt a fresh dispatch.
-    ctx.ui.notify(
-      "Dispatch gap detected — no unit dispatched after previous unit completed. Re-evaluating state.",
-      "warning",
-    );
+    if (verbose) {
+      ctx.ui.notify(
+        "Dispatch gap detected — re-evaluating state.",
+        "info",
+      );
+    }
 
     try {
       await dispatchNextUnit(ctx, pi);
@@ -1507,7 +1509,7 @@ async function dispatchNextUnit(
 ): Promise<void> {
   if (!active || !cmdCtx) {
     if (active && !cmdCtx) {
-      ctx.ui.notify("Auto-mode dispatch failed: no command context. Run /gsd auto to restart.", "error");
+      ctx.ui.notify("Auto-mode session expired. Run /gsd auto to restart.", "info");
     }
     return;
   }
@@ -1518,7 +1520,7 @@ async function dispatchNextUnit(
     return; // Another dispatch is in progress — bail silently
   }
   _dispatching = true;
-
+  try {
   // Recursion depth guard: when many units are skipped in sequence (e.g., after
   // crash recovery with 10+ completed units), recursive dispatchNextUnit calls
   // can freeze the TUI or overflow the stack. Yield generously after MAX_SKIP_DEPTH.
@@ -1861,7 +1863,7 @@ async function dispatchNextUnit(
         saveActivityLog(ctx, basePath, currentUnit.type, currentUnit.id);
       }
       await stopAuto(ctx, pi);
-      ctx.ui.notify(`Unexpected phase: ${state.phase}. Stopping auto-mode.`, "warning");
+      ctx.ui.notify(`Unhandled phase "${state.phase}" — run /gsd doctor to diagnose.`, "info");
       return;
     }
   }
@@ -2181,7 +2183,7 @@ async function dispatchNextUnit(
   const result = await cmdCtx!.newSession();
   if (result.cancelled) {
     await stopAuto(ctx, pi);
-    ctx.ui.notify("New session cancelled — auto-mode stopped.", "warning");
+    ctx.ui.notify("Auto-mode stopped.", "info");
     return;
   }
 
@@ -2287,7 +2289,7 @@ async function dispatchNextUnit(
         }
       }
       if (!model) {
-        ctx.ui.notify(`Model ${modelId} not found in available models, trying fallback.`, "warning");
+        if (verbose) ctx.ui.notify(`Model ${modelId} not found, trying fallback.`, "info");
         continue;
       }
 
@@ -2303,25 +2305,14 @@ async function dispatchNextUnit(
       } else {
         const nextModel = modelsToTry[modelsToTry.indexOf(modelId) + 1];
         if (nextModel) {
-          ctx.ui.notify(
-            `Failed to set model ${modelId}, trying fallback ${nextModel}...`,
-            "warning",
-          );
+          if (verbose) ctx.ui.notify(`Failed to set model ${modelId}, trying ${nextModel}...`, "info");
         } else {
-          ctx.ui.notify(
-            `Failed to set model ${modelId} and all fallbacks exhausted. Using default model.`,
-            "warning",
-          );
+          ctx.ui.notify(`All preferred models unavailable for ${unitType}. Using default.`, "warning");
         }
       }
     }
 
-    if (!modelSet) {
-      ctx.ui.notify(
-        `Could not set any preferred model for ${unitType}. Continuing with default.`,
-        "warning",
-      );
-    }
+    // modelSet=false is already handled by the "all fallbacks exhausted" warning above
   }
 
   // Start progress-aware supervision: a soft warning, an idle watchdog, and
@@ -2434,6 +2425,9 @@ async function dispatchNextUnit(
     );
     await pauseAuto(ctx, pi);
   }
+  } finally {
+    _dispatching = false;
+  }
 }
 
 // ─── Skill Discovery ──────────────────────────────────────────────────────────

package/dist/resources/extensions/gsd/gitignore.ts

@@ -87,6 +87,28 @@ export function ensureGitignore(basePath: string): boolean {
     existing = readFileSync(gitignorePath, "utf-8");
   }
 
+  // Self-heal: remove blanket ".gsd/" lines from pre-v2.14.0 projects.
+  // The blanket ignore prevented planning artifacts (.gsd/milestones/) from
+  // being tracked in git, causing artifacts to vanish in worktrees and
+  // triggering loop detection failures. Replace with explicit runtime-only
+  // ignores so planning files are tracked naturally.
+  let modified = false;
+  const lines = existing.split("\n");
+  const filteredLines = lines.filter(line => {
+    const trimmed = line.trim();
+    // Remove standalone ".gsd/" lines (blanket ignore) but keep specific
+    // .gsd/ subpath patterns like ".gsd/activity/" or ".gsd/auto.lock"
+    if (trimmed === ".gsd/" || trimmed === ".gsd") {
+      modified = true;
+      return false;
+    }
+    return true;
+  });
+  if (modified) {
+    existing = filteredLines.join("\n");
+    writeFileSync(gitignorePath, existing, "utf-8");
+  }
+
   // Parse existing lines (trimmed, ignoring comments and blanks)
   const existingLines = new Set(
     existing
@@ -98,7 +120,7 @@ export function ensureGitignore(basePath: string): boolean {
   // Find patterns not yet present
   const missing = BASELINE_PATTERNS.filter((p) => !existingLines.has(p));
 
-  if (missing.length === 0) return false;
+  if (missing.length === 0) return modified;
 
   // Build the block to append
   const block = [

package/dist/resources/extensions/gsd/prompts/discuss.md

@@ -91,13 +91,19 @@ Do not count the reflection step as a question round. Rounds start after reflect
 
 ## Depth Verification
 
-Before moving to the wrap-up gate, present a structured depth summary to the user via `ask_user_questions`. This is a checkpoint — show what you captured across the depth checklist dimensions, using the user's own terminology and framing.
+Before moving to the wrap-up gate, present a structured depth summary as a checkpoint.
 
-The question should summarize: what you understood them to be building, what shaped your understanding most (their emphasis, constraints, concerns), and any areas where you're least confident in your understanding. Frame it as: "Before we move to planning, here's what I captured — did I get the depth right?"
+**Print the summary as normal chat text first** — this is where the formatting renders properly. Structure the summary across the depth checklist dimensions using the user's own terminology and framing. Cover: what you understood them to be building, what shaped your understanding most (their emphasis, constraints, concerns), and any areas where you're least confident in your understanding.
 
-**Convention:** The question ID must contain `depth_verification` (e.g., `depth_verification_summary`). This naming convention enables downstream mechanical detection of this step.
+**Then** use `ask_user_questions` with a short confirmation question — NOT the summary itself. The question field is designed for single sentences, not multi-paragraph summaries.
 
-Offer two options: "Yes, you got it (Recommended)" and "Not quite — let me clarify." If they clarify, absorb the correction and re-verify.
+**Convention:** The question ID must contain `depth_verification` (e.g., `depth_verification_confirm`). This naming convention enables downstream mechanical detection of this step.
+
+Example flow:
+1. Print in chat: the full depth summary with markdown formatting (headers, bold, bullets)
+2. Call `ask_user_questions` with: header "Depth Check", question "Did I capture the depth right?", options "Yes, you got it (Recommended)" and "Not quite — let me clarify"
+
+If they clarify, absorb the correction and re-verify.
 
 ## Wrap-up Gate
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-pi",
-  "version": "2.14.0",
+  "version": "2.14.2",
   "description": "GSD — Get Shit Done coding agent",
   "license": "MIT",
   "repository": {

package/src/resources/extensions/gsd/auto.ts

@@ -335,10 +335,12 @@ function startDispatchGapWatchdog(ctx: ExtensionContext, pi: ExtensionAPI): void
 
     // Auto-mode is active but no unit was dispatched — the state machine stalled.
     // Re-derive state and attempt a fresh dispatch.
-    ctx.ui.notify(
-      "Dispatch gap detected — no unit dispatched after previous unit completed. Re-evaluating state.",
-      "warning",
-    );
+    if (verbose) {
+      ctx.ui.notify(
+        "Dispatch gap detected — re-evaluating state.",
+        "info",
+      );
+    }
 
     try {
       await dispatchNextUnit(ctx, pi);
@@ -1507,7 +1509,7 @@ async function dispatchNextUnit(
 ): Promise<void> {
   if (!active || !cmdCtx) {
     if (active && !cmdCtx) {
-      ctx.ui.notify("Auto-mode dispatch failed: no command context. Run /gsd auto to restart.", "error");
+      ctx.ui.notify("Auto-mode session expired. Run /gsd auto to restart.", "info");
     }
     return;
   }
@@ -1518,7 +1520,7 @@ async function dispatchNextUnit(
     return; // Another dispatch is in progress — bail silently
   }
   _dispatching = true;
-
+  try {
   // Recursion depth guard: when many units are skipped in sequence (e.g., after
   // crash recovery with 10+ completed units), recursive dispatchNextUnit calls
   // can freeze the TUI or overflow the stack. Yield generously after MAX_SKIP_DEPTH.
@@ -1861,7 +1863,7 @@ async function dispatchNextUnit(
         saveActivityLog(ctx, basePath, currentUnit.type, currentUnit.id);
       }
       await stopAuto(ctx, pi);
-      ctx.ui.notify(`Unexpected phase: ${state.phase}. Stopping auto-mode.`, "warning");
+      ctx.ui.notify(`Unhandled phase "${state.phase}" — run /gsd doctor to diagnose.`, "info");
       return;
     }
   }
@@ -2181,7 +2183,7 @@ async function dispatchNextUnit(
   const result = await cmdCtx!.newSession();
   if (result.cancelled) {
     await stopAuto(ctx, pi);
-    ctx.ui.notify("New session cancelled — auto-mode stopped.", "warning");
+    ctx.ui.notify("Auto-mode stopped.", "info");
     return;
   }
 
@@ -2287,7 +2289,7 @@ async function dispatchNextUnit(
         }
       }
       if (!model) {
-        ctx.ui.notify(`Model ${modelId} not found in available models, trying fallback.`, "warning");
+        if (verbose) ctx.ui.notify(`Model ${modelId} not found, trying fallback.`, "info");
         continue;
       }
 
@@ -2303,25 +2305,14 @@ async function dispatchNextUnit(
       } else {
         const nextModel = modelsToTry[modelsToTry.indexOf(modelId) + 1];
         if (nextModel) {
-          ctx.ui.notify(
-            `Failed to set model ${modelId}, trying fallback ${nextModel}...`,
-            "warning",
-          );
+          if (verbose) ctx.ui.notify(`Failed to set model ${modelId}, trying ${nextModel}...`, "info");
         } else {
-          ctx.ui.notify(
-            `Failed to set model ${modelId} and all fallbacks exhausted. Using default model.`,
-            "warning",
-          );
+          ctx.ui.notify(`All preferred models unavailable for ${unitType}. Using default.`, "warning");
         }
       }
     }
 
-    if (!modelSet) {
-      ctx.ui.notify(
-        `Could not set any preferred model for ${unitType}. Continuing with default.`,
-        "warning",
-      );
-    }
+    // modelSet=false is already handled by the "all fallbacks exhausted" warning above
   }
 
   // Start progress-aware supervision: a soft warning, an idle watchdog, and
@@ -2434,6 +2425,9 @@ async function dispatchNextUnit(
     );
     await pauseAuto(ctx, pi);
   }
+  } finally {
+    _dispatching = false;
+  }
 }
 
 // ─── Skill Discovery ──────────────────────────────────────────────────────────

package/src/resources/extensions/gsd/gitignore.ts

@@ -87,6 +87,28 @@ export function ensureGitignore(basePath: string): boolean {
     existing = readFileSync(gitignorePath, "utf-8");
   }
 
+  // Self-heal: remove blanket ".gsd/" lines from pre-v2.14.0 projects.
+  // The blanket ignore prevented planning artifacts (.gsd/milestones/) from
+  // being tracked in git, causing artifacts to vanish in worktrees and
+  // triggering loop detection failures. Replace with explicit runtime-only
+  // ignores so planning files are tracked naturally.
+  let modified = false;
+  const lines = existing.split("\n");
+  const filteredLines = lines.filter(line => {
+    const trimmed = line.trim();
+    // Remove standalone ".gsd/" lines (blanket ignore) but keep specific
+    // .gsd/ subpath patterns like ".gsd/activity/" or ".gsd/auto.lock"
+    if (trimmed === ".gsd/" || trimmed === ".gsd") {
+      modified = true;
+      return false;
+    }
+    return true;
+  });
+  if (modified) {
+    existing = filteredLines.join("\n");
+    writeFileSync(gitignorePath, existing, "utf-8");
+  }
+
   // Parse existing lines (trimmed, ignoring comments and blanks)
   const existingLines = new Set(
     existing
@@ -98,7 +120,7 @@ export function ensureGitignore(basePath: string): boolean {
   // Find patterns not yet present
   const missing = BASELINE_PATTERNS.filter((p) => !existingLines.has(p));
 
-  if (missing.length === 0) return false;
+  if (missing.length === 0) return modified;
 
   // Build the block to append
   const block = [

package/src/resources/extensions/gsd/prompts/discuss.md

@@ -91,13 +91,19 @@ Do not count the reflection step as a question round. Rounds start after reflect
 
 ## Depth Verification
 
-Before moving to the wrap-up gate, present a structured depth summary to the user via `ask_user_questions`. This is a checkpoint — show what you captured across the depth checklist dimensions, using the user's own terminology and framing.
+Before moving to the wrap-up gate, present a structured depth summary as a checkpoint.
 
-The question should summarize: what you understood them to be building, what shaped your understanding most (their emphasis, constraints, concerns), and any areas where you're least confident in your understanding. Frame it as: "Before we move to planning, here's what I captured — did I get the depth right?"
+**Print the summary as normal chat text first** — this is where the formatting renders properly. Structure the summary across the depth checklist dimensions using the user's own terminology and framing. Cover: what you understood them to be building, what shaped your understanding most (their emphasis, constraints, concerns), and any areas where you're least confident in your understanding.
 
-**Convention:** The question ID must contain `depth_verification` (e.g., `depth_verification_summary`). This naming convention enables downstream mechanical detection of this step.
+**Then** use `ask_user_questions` with a short confirmation question — NOT the summary itself. The question field is designed for single sentences, not multi-paragraph summaries.
 
-Offer two options: "Yes, you got it (Recommended)" and "Not quite — let me clarify." If they clarify, absorb the correction and re-verify.
+**Convention:** The question ID must contain `depth_verification` (e.g., `depth_verification_confirm`). This naming convention enables downstream mechanical detection of this step.
+
+Example flow:
+1. Print in chat: the full depth summary with markdown formatting (headers, bold, bullets)
+2. Call `ask_user_questions` with: header "Depth Check", question "Did I capture the depth right?", options "Yes, you got it (Recommended)" and "Not quite — let me clarify"
+
+If they clarify, absorb the correction and re-verify.
 
 ## Wrap-up Gate