gsd-pi 2.29.0-dev.2ccf3fb → 2.29.0-dev.6a38b5d

package/dist/resources/extensions/gsd/prompts/guided-discuss-milestone.md

@@ -91,7 +91,7 @@ Before moving to the wrap-up gate, verify you have covered:
 - options: "Yes, you got it (Recommended)", "Not quite — let me clarify"
 - **The question ID must contain `depth_verification`** (e.g. `depth_verification_confirm`) — this enables the write-gate downstream.
 
-**If `{{structuredQuestionsAvailable}}` is `false`:** ask in plain text: "Did I capture that correctly? If not, tell me what I missed." Wait for confirmation before proceeding.
+**If `{{structuredQuestionsAvailable}}` is `false`:** ask in plain text: "Did I capture that correctly? Anything I missed?" Wait for confirmation before proceeding.
 
 If they clarify, absorb the correction and re-verify.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-pi",
-  "version": "2.29.0-dev.2ccf3fb",
+  "version": "2.29.0-dev.6a38b5d",
   "description": "GSD — Get Shit Done coding agent",
   "license": "MIT",
   "repository": {

package/packages/native/dist/native.d.ts

@@ -55,5 +55,3 @@ export declare const native: {
     parseStreamingJson: (text: string) => unknown;
     xxHash32: (input: string, seed: number) => number;
 };
-/** True when the native addon loaded successfully. False on unsupported platforms. */
-export declare const nativeAvailable = false;

package/packages/native/dist/native.js

@@ -22,14 +22,12 @@ const platformPackageMap = {
     "linux-arm64": "linux-arm64-gnu",
     "win32-x64": "win32-x64-msvc",
 };
-let _loadedSuccessfully = false;
 function loadNative() {
     const errors = [];
     // 1. Try the platform-specific npm optional dependency
     const packageSuffix = platformPackageMap[platformTag];
     if (packageSuffix) {
         try {
-            _loadedSuccessfully = true;
             return require(`@gsd-build/engine-${packageSuffix}`);
         }
         catch (err) {
@@ -40,7 +38,6 @@ function loadNative() {
     // 2. Try local release build (native/addon/gsd_engine.{platform}.node)
     const releasePath = path.join(addonDir, `gsd_engine.${platformTag}.node`);
     try {
-        _loadedSuccessfully = true;
         return require(releasePath);
     }
     catch (err) {
@@ -50,7 +47,6 @@ function loadNative() {
     // 3. Try local dev build (native/addon/gsd_engine.dev.node)
     const devPath = path.join(addonDir, "gsd_engine.dev.node");
     try {
-        _loadedSuccessfully = true;
         return require(devPath);
     }
     catch (err) {
@@ -59,20 +55,10 @@ function loadNative() {
     }
     const details = errors.map((e) => `  - ${e}`).join("\n");
     const supportedPlatforms = Object.keys(platformPackageMap);
-    // Graceful fallback: on unsupported platforms (e.g., win32-arm64), return a
-    // proxy that throws on individual function calls rather than crashing the
-    // entire import chain at startup (#1223). Consumers with JS fallbacks
-    // (parseRoadmap, parsePlan, fuzzyFind, etc.) catch these and degrade gracefully.
-    process.stderr.write(`[gsd] Native addon not available for ${platformTag}. Falling back to JS implementations (slower).\n` +
-        `  Supported native platforms: ${supportedPlatforms.join(", ")}\n`);
-    return new Proxy({}, {
-        get(_target, prop) {
-            return (..._args) => {
-                throw new Error(`Native function '${String(prop)}' is not available on ${platformTag}`);
-            };
-        },
-    });
+    throw new Error(`Failed to load gsd_engine native addon for ${platformTag}.\n\n` +
+        `Tried:\n${details}\n\n` +
+        `Supported platforms: ${supportedPlatforms.join(", ")}\n` +
+        `If your platform is listed, try reinstalling: npm i -g gsd-pi\n` +
+        `Otherwise, please open an issue: https://github.com/gsd-build/gsd-2/issues`);
 }
 export const native = loadNative();
-/** True when the native addon loaded successfully. False on unsupported platforms. */
-export const nativeAvailable = _loadedSuccessfully;

package/packages/native/src/native.ts

@@ -27,8 +27,6 @@ const platformPackageMap: Record<string, string> = {
   "win32-x64": "win32-x64-msvc",
 };
 
-let _loadedSuccessfully = false;
-
 function loadNative(): Record<string, unknown> {
   const errors: string[] = [];
 
@@ -36,7 +34,7 @@ function loadNative(): Record<string, unknown> {
   const packageSuffix = platformPackageMap[platformTag];
   if (packageSuffix) {
     try {
-      _loadedSuccessfully = true; return require(`@gsd-build/engine-${packageSuffix}`) as Record<string, unknown>;
+      return require(`@gsd-build/engine-${packageSuffix}`) as Record<string, unknown>;
     } catch (err) {
       const message = err instanceof Error ? err.message : String(err);
       errors.push(`@gsd-build/engine-${packageSuffix}: ${message}`);
@@ -46,7 +44,7 @@ function loadNative(): Record<string, unknown> {
   // 2. Try local release build (native/addon/gsd_engine.{platform}.node)
   const releasePath = path.join(addonDir, `gsd_engine.${platformTag}.node`);
   try {
-    _loadedSuccessfully = true; return require(releasePath) as Record<string, unknown>;
+    return require(releasePath) as Record<string, unknown>;
   } catch (err) {
     const message = err instanceof Error ? err.message : String(err);
     errors.push(`${releasePath}: ${message}`);
@@ -55,7 +53,7 @@ function loadNative(): Record<string, unknown> {
   // 3. Try local dev build (native/addon/gsd_engine.dev.node)
   const devPath = path.join(addonDir, "gsd_engine.dev.node");
   try {
-    _loadedSuccessfully = true; return require(devPath) as Record<string, unknown>;
+    return require(devPath) as Record<string, unknown>;
   } catch (err) {
     const message = err instanceof Error ? err.message : String(err);
     errors.push(`${devPath}: ${message}`);
@@ -63,22 +61,13 @@ function loadNative(): Record<string, unknown> {
 
   const details = errors.map((e) => `  - ${e}`).join("\n");
   const supportedPlatforms = Object.keys(platformPackageMap);
-
-  // Graceful fallback: on unsupported platforms (e.g., win32-arm64), return a
-  // proxy that throws on individual function calls rather than crashing the
-  // entire import chain at startup (#1223). Consumers with JS fallbacks
-  // (parseRoadmap, parsePlan, fuzzyFind, etc.) catch these and degrade gracefully.
-  process.stderr.write(
-    `[gsd] Native addon not available for ${platformTag}. Falling back to JS implementations (slower).\n` +
-      `  Supported native platforms: ${supportedPlatforms.join(", ")}\n`,
+  throw new Error(
+    `Failed to load gsd_engine native addon for ${platformTag}.\n\n` +
+      `Tried:\n${details}\n\n` +
+      `Supported platforms: ${supportedPlatforms.join(", ")}\n` +
+      `If your platform is listed, try reinstalling: npm i -g gsd-pi\n` +
+      `Otherwise, please open an issue: https://github.com/gsd-build/gsd-2/issues`,
   );
-  return new Proxy({} as Record<string, unknown>, {
-    get(_target, prop) {
-      return (..._args: unknown[]) => {
-        throw new Error(`Native function '${String(prop)}' is not available on ${platformTag}`);
-      };
-    },
-  });
 }
 
 export const native = loadNative() as {
@@ -151,6 +140,3 @@ export const native = loadNative() as {
   parseStreamingJson: (text: string) => unknown;
   xxHash32: (input: string, seed: number) => number;
 };
-
-/** True when the native addon loaded successfully. False on unsupported platforms. */
-export const nativeAvailable = _loadedSuccessfully;

package/src/resources/extensions/gsd/prompts/guided-discuss-milestone.md

@@ -91,7 +91,7 @@ Before moving to the wrap-up gate, verify you have covered:
 - options: "Yes, you got it (Recommended)", "Not quite — let me clarify"
 - **The question ID must contain `depth_verification`** (e.g. `depth_verification_confirm`) — this enables the write-gate downstream.
 
-**If `{{structuredQuestionsAvailable}}` is `false`:** ask in plain text: "Did I capture that correctly? If not, tell me what I missed." Wait for confirmation before proceeding.
+**If `{{structuredQuestionsAvailable}}` is `false`:** ask in plain text: "Did I capture that correctly? Anything I missed?" Wait for confirmation before proceeding.
 
 If they clarify, absorb the correction and re-verify.
 

package/dist/resources/skills/create-gsd-extension/SKILL.md

@@ -1,87 +0,0 @@
----
-name: create-gsd-extension
-description: Create, debug, and iterate on GSD extensions (TypeScript modules that add tools, commands, event hooks, custom UI, and providers to GSD). Use when asked to build an extension, add a tool the LLM can call, register a slash command, hook into GSD events, create custom TUI components, or modify GSD behavior. Triggers on "create extension", "build extension", "add a tool", "register command", "hook into gsd", "custom tool", "gsd plugin", "gsd extension".
----
-
-<essential_principles>
-
-**Extensions are TypeScript modules** that hook into GSD's runtime (built on pi). They export a default function receiving `ExtensionAPI` and use it to subscribe to events, register tools/commands/shortcuts, and interact with the session.
-
-**GSD extension paths:**
-- Global extensions: `~/.gsd/agent/extensions/*.ts` or `~/.gsd/agent/extensions/*/index.ts`
-- Project-local extensions: `.gsd/extensions/*.ts` or `.gsd/extensions/*/index.ts`
-
-**The three primitives:**
-1. **Events** — Listen and react (`pi.on("event", handler)`). Can block tool calls, modify messages, inject context.
-2. **Tools** — Give the LLM new abilities (`pi.registerTool()`). LLM calls them autonomously.
-3. **Commands** — Give users slash commands (`pi.registerCommand()`). Users type `/mycommand`.
-
-**Non-negotiable rules:**
-- Use `StringEnum` from `@mariozechner/pi-ai` for string enum params (NOT `Type.Union`/`Type.Literal` — breaks Google's API)
-- Truncate tool output to 50KB / 2000 lines max (use `truncateHead`/`truncateTail` from `@mariozechner/pi-coding-agent`)
-- Store stateful tool state in `details` for branching support
-- Check `signal?.aborted` in long-running tool executions
-- Use `pi.exec()` not `child_process` for shell commands
-- Check `ctx.hasUI` before dialog methods (non-interactive modes exist)
-- Session control methods (`waitForIdle`, `newSession`, `fork`, `navigateTree`, `reload`) are ONLY available in command handlers — they deadlock in event handlers
-- Lines from `render()` must not exceed `width` — use `truncateToWidth()`
-- Use theme from callback params, never import directly
-- Strip leading `@` from path params in custom tools (some models add it)
-
-**Available imports:**
-
-| Package | Purpose |
-|---------|---------|
-| `@mariozechner/pi-coding-agent` | `ExtensionAPI`, `ExtensionContext`, `Theme`, event types, tool utilities, `DynamicBorder`, `BorderedLoader`, `CustomEditor`, `highlightCode` |
-| `@sinclair/typebox` | `Type.Object`, `Type.String`, `Type.Number`, `Type.Optional`, `Type.Boolean`, `Type.Array` |
-| `@mariozechner/pi-ai` | `StringEnum` (required for string enums), `Type` re-export |
-| `@mariozechner/pi-tui` | `Text`, `Box`, `Container`, `Spacer`, `Markdown`, `SelectList`, `Input`, `matchesKey`, `Key`, `truncateToWidth`, `visibleWidth` |
-| Node.js built-ins | `node:fs`, `node:path`, `node:child_process`, etc. |
-
-</essential_principles>
-
-<routing>
-Based on user intent, route to the appropriate workflow:
-
-**Building a new extension:**
-- "Create an extension", "build a tool", "I want to add a command" → `workflows/create-extension.md`
-
-**Adding capabilities to an existing extension:**
-- "Add a tool to my extension", "add event hook", "add custom rendering" → `workflows/add-capability.md`
-
-**Debugging an extension:**
-- "My extension doesn't work", "tool not showing up", "event not firing" → `workflows/debug-extension.md`
-
-**If user intent is clear from context, skip the question and go directly to the workflow.**
-</routing>
-
-<reference_index>
-All domain knowledge in `references/`:
-
-**Core architecture:** extension-lifecycle.md, events-reference.md
-**API surface:** extensionapi-reference.md, extensioncontext-reference.md
-**Capabilities:** custom-tools.md, custom-commands.md, custom-ui.md, custom-rendering.md
-**Patterns:** state-management.md, system-prompt-modification.md, compaction-session-control.md
-**Infrastructure:** model-provider-management.md, remote-execution-overrides.md, packaging-distribution.md, mode-behavior.md
-**Gotchas:** key-rules-gotchas.md
-</reference_index>
-
-<workflows_index>
-| Workflow | Purpose |
-|----------|---------|
-| create-extension.md | Build a new extension from scratch |
-| add-capability.md | Add tools, commands, hooks, UI to an existing extension |
-| debug-extension.md | Diagnose and fix extension issues |
-</workflows_index>
-
-<success_criteria>
-Extension is complete when:
-- TypeScript compiles without errors (jiti handles this at runtime)
-- Extension loads on GSD startup or `/reload` without errors
-- Tools appear in the LLM's system prompt and are callable
-- Commands respond to `/command` input
-- Event hooks fire at the expected lifecycle points
-- Custom UI renders correctly within terminal width
-- State persists correctly across session restarts (if stateful)
-- Output is truncated to safe limits (if tools produce variable output)
-</success_criteria>

package/dist/resources/skills/create-gsd-extension/references/compaction-session-control.md

@@ -1,77 +0,0 @@
-<overview>
-Custom compaction hooks, triggering compaction, and session control methods available only in command handlers.
-</overview>
-
-<custom_compaction>
-Override default compaction behavior:
-
-```typescript
-pi.on("session_before_compact", async (event, ctx) => {
-  const { preparation, branchEntries, customInstructions, signal } = event;
-
-  // Option 1: Cancel
-  return { cancel: true };
-
-  // Option 2: Custom summary
-  return {
-    compaction: {
-      summary: "Custom summary of conversation so far...",
-      firstKeptEntryId: preparation.firstKeptEntryId,
-      tokensBefore: preparation.tokensBefore,
-    }
-  };
-});
-```
-</custom_compaction>
-
-<trigger_compaction>
-Trigger compaction programmatically from any handler:
-
-```typescript
-ctx.compact({
-  customInstructions: "Focus on the authentication changes",
-  onComplete: (result) => ctx.ui.notify("Compacted!", "info"),
-  onError: (error) => ctx.ui.notify(`Failed: ${error.message}`, "error"),
-});
-```
-</trigger_compaction>
-
-<session_control>
-**Only available in command handlers** (deadlocks in event handlers):
-
-```typescript
-pi.registerCommand("handoff", {
-  handler: async (args, ctx) => {
-    await ctx.waitForIdle();
-
-    // Create new session with initial context
-    const result = await ctx.newSession({
-      parentSession: ctx.sessionManager.getSessionFile(),
-      setup: async (sm) => {
-        sm.appendMessage({
-          role: "user",
-          content: [{ type: "text", text: `Context: ${args}` }],
-          timestamp: Date.now(),
-        });
-      },
-    });
-
-    if (result.cancelled) { /* extension cancelled via session_before_switch */ }
-  },
-});
-```
-
-| Method | Purpose |
-|--------|---------|
-| `ctx.waitForIdle()` | Wait for agent to finish streaming |
-| `ctx.newSession(options?)` | Create a new session |
-| `ctx.fork(entryId)` | Fork from a specific entry |
-| `ctx.navigateTree(targetId, options?)` | Navigate session tree (with optional summary) |
-| `ctx.reload()` | Hot-reload everything (treat as terminal — code after runs pre-reload version) |
-
-`navigateTree` options:
-- `summarize: boolean` — generate summary of abandoned branch
-- `customInstructions: string` — instructions for summarizer
-- `replaceInstructions: boolean` — replace default prompt entirely
-- `label: string` — label to attach to branch summary
-</session_control>

package/dist/resources/skills/create-gsd-extension/references/custom-commands.md

@@ -1,139 +0,0 @@
-<overview>
-Custom slash commands — registration, argument completions, subcommand patterns, and the extended command context.
-</overview>
-
-<basic_registration>
-```typescript
-pi.registerCommand("deploy", {
-  description: "Deploy to an environment",
-  handler: async (args, ctx) => {
-    // args = everything after "/deploy "
-    // ctx = ExtensionCommandContext (has session control methods)
-    ctx.ui.notify(`Deploying to ${args || "production"}`, "info");
-  },
-});
-```
-</basic_registration>
-
-<argument_completions>
-Add tab-completion for command arguments:
-
-```typescript
-import type { AutocompleteItem } from "@mariozechner/pi-tui";
-
-pi.registerCommand("deploy", {
-  description: "Deploy to an environment",
-  getArgumentCompletions: (prefix: string): AutocompleteItem[] | null => {
-    const envs = ["dev", "staging", "prod"];
-    const items = envs.map(e => ({ value: e, label: e }));
-    const filtered = items.filter(i => i.value.startsWith(prefix));
-    return filtered.length > 0 ? filtered : null;
-  },
-  handler: async (args, ctx) => {
-    ctx.ui.notify(`Deploying to ${args}`, "info");
-  },
-});
-```
-</argument_completions>
-
-<subcommand_pattern>
-Fake nested commands via first-argument parsing. Used by `/wt new|ls|switch|merge|rm`.
-
-```typescript
-pi.registerCommand("foo", {
-  description: "Manage foo items: /foo new|list|delete [name]",
-
-  getArgumentCompletions: (prefix: string) => {
-    const parts = prefix.trim().split(/\s+/);
-
-    // First arg: subcommand
-    if (parts.length <= 1) {
-      return ["new", "list", "delete"]
-        .filter(cmd => cmd.startsWith(parts[0] ?? ""))
-        .map(cmd => ({ value: cmd, label: cmd }));
-    }
-
-    // Second arg: depends on subcommand
-    if (parts[0] === "delete") {
-      const items = getItemsSomehow();
-      return items
-        .filter(name => name.startsWith(parts[1] ?? ""))
-        .map(name => ({ value: `delete ${name}`, label: name }));
-    }
-
-    return [];
-  },
-
-  handler: async (args, ctx) => {
-    const parts = args.trim().split(/\s+/);
-    const sub = parts[0];
-
-    switch (sub) {
-      case "new": /* ... */ return;
-      case "list": /* ... */ return;
-      case "delete": /* handle parts[1] */ return;
-      default:
-        ctx.ui.notify("Usage: /foo <new|list|delete> [name]", "info");
-    }
-  },
-});
-```
-
-**Gotcha:** `"".trim().split(/\s+/)` produces `['']`, not `[]`. That's why `parts.length <= 1` handles both empty and partial first arg.
-</subcommand_pattern>
-
-<command_context>
-Command handlers get `ExtensionCommandContext` which extends `ExtensionContext` with session control methods:
-
-| Method | Purpose |
-|--------|---------|
-| `ctx.waitForIdle()` | Wait for agent to finish streaming |
-| `ctx.newSession(options?)` | Create a new session |
-| `ctx.fork(entryId)` | Fork from an entry |
-| `ctx.navigateTree(targetId, options?)` | Navigate session tree |
-| `ctx.reload()` | Hot-reload everything |
-
-**⚠️ These methods are ONLY available in command handlers.** Calling them from event handlers causes deadlocks.
-
-```typescript
-pi.registerCommand("handoff", {
-  handler: async (args, ctx) => {
-    await ctx.waitForIdle();
-    await ctx.newSession({
-      setup: async (sm) => {
-        sm.appendMessage({
-          role: "user",
-          content: [{ type: "text", text: `Context: ${args}` }],
-          timestamp: Date.now(),
-        });
-      },
-    });
-  },
-});
-```
-</command_context>
-
-<reload_pattern>
-Expose reload as both a command and a tool the LLM can call:
-
-```typescript
-pi.registerCommand("reload-runtime", {
-  description: "Reload extensions, skills, prompts, and themes",
-  handler: async (_args, ctx) => {
-    await ctx.reload();
-    return;  // Treat reload as terminal
-  },
-});
-
-pi.registerTool({
-  name: "reload_runtime",
-  label: "Reload Runtime",
-  description: "Reload extensions, skills, prompts, and themes",
-  parameters: Type.Object({}),
-  async execute() {
-    pi.sendUserMessage("/reload-runtime", { deliverAs: "followUp" });
-    return { content: [{ type: "text", text: "Queued /reload-runtime as follow-up." }] };
-  },
-});
-```
-</reload_pattern>

package/dist/resources/skills/create-gsd-extension/references/custom-rendering.md

@@ -1,108 +0,0 @@
-<overview>
-Custom rendering for tools and messages — control how they appear in the TUI.
-</overview>
-
-<tool_rendering>
-Tools can provide `renderCall` (how the call looks) and `renderResult` (how the result looks):
-
-```typescript
-import { Text } from "@mariozechner/pi-tui";
-import { keyHint } from "@mariozechner/pi-coding-agent";
-
-pi.registerTool({
-  name: "my_tool",
-  // ...
-
-  renderCall(args, theme) {
-    let text = theme.fg("toolTitle", theme.bold("my_tool "));
-    text += theme.fg("muted", args.action);
-    if (args.text) text += " " + theme.fg("dim", `"${args.text}"`);
-    return new Text(text, 0, 0);  // 0,0 padding — Box handles it
-  },
-
-  renderResult(result, { expanded, isPartial }, theme) {
-    // isPartial = true during streaming (onUpdate was called)
-    if (isPartial) {
-      return new Text(theme.fg("warning", "Processing..."), 0, 0);
-    }
-
-    // expanded = user toggled expand (Ctrl+O)
-    if (result.details?.error) {
-      return new Text(theme.fg("error", `Error: ${result.details.error}`), 0, 0);
-    }
-
-    let text = theme.fg("success", "✓ Done");
-    if (!expanded) {
-      text += ` (${keyHint("expandTools", "to expand")})`;
-    }
-    if (expanded && result.details?.items) {
-      for (const item of result.details.items) {
-        text += "\n  " + theme.fg("dim", item);
-      }
-    }
-    return new Text(text, 0, 0);
-  },
-});
-```
-
-If you omit `renderCall`/`renderResult`, the built-in renderer is used. Useful for tool overrides where you just wrap logic without reimplementing UI.
-
-**Fallback:** If render methods throw, `renderCall` shows tool name, `renderResult` shows raw `content` text.
-</tool_rendering>
-
-<key_hints>
-Key hint helpers for showing keybinding info in render output:
-
-```typescript
-import { keyHint, appKeyHint, editorKey, rawKeyHint } from "@mariozechner/pi-coding-agent";
-
-// Editor action hint (respects user keybinding config)
-keyHint("expandTools", "to expand")    // e.g., "Ctrl+O to expand"
-keyHint("selectConfirm", "to select")
-
-// Raw key hint (always shows literal key)
-rawKeyHint("Ctrl+O", "to expand")
-```
-</key_hints>
-
-<message_rendering>
-Register a renderer for custom message types:
-
-```typescript
-import { Text } from "@mariozechner/pi-tui";
-
-pi.registerMessageRenderer("my-extension", (message, options, theme) => {
-  const { expanded } = options;
-  let text = theme.fg("accent", `[${message.customType}] `) + message.content;
-  if (expanded && message.details) {
-    text += "\n" + theme.fg("dim", JSON.stringify(message.details, null, 2));
-  }
-  return new Text(text, 0, 0);
-});
-
-// Send messages that use this renderer:
-pi.sendMessage({
-  customType: "my-extension",  // Matches renderer name
-  content: "Status update",
-  display: true,
-  details: { foo: "bar" },
-});
-```
-</message_rendering>
-
-<syntax_highlighting>
-```typescript
-import { highlightCode, getLanguageFromPath } from "@mariozechner/pi-coding-agent";
-
-const lang = getLanguageFromPath("/path/to/file.rs");  // "rust"
-const highlighted = highlightCode(code, lang, theme);
-```
-</syntax_highlighting>
-
-<best_practices>
-- Return `Text` with padding `(0, 0)` — the wrapping `Box` handles padding
-- Support `expanded` for detail on demand
-- Handle `isPartial` for streaming progress
-- Keep collapsed view compact
-- Use `\n` for multi-line content within a single `Text`
-</best_practices>