@therocketcode/gsd-core 1.7.1 → 1.7.2

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "gsd-core",
   "displayName": "GSD Core",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "description": "GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
   "author": {
     "name": "TheRocketCodeMX",

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-core",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "description": "GSD Core — a meta-prompting, context engineering, and spec-driven development system for AI coding agents. Loads gsd's operating context into every Gemini CLI session.",
   "contextFileName": "GEMINI.md"
 }

package/hooks/dist/gsd-context-monitor.js

@@ -1,195 +1,30 @@
 #!/usr/bin/env node
 // gsd-hook-version: {{GSD_VERSION}}
-// Context Monitor - PostToolUse/AfterTool hook (Gemini uses AfterTool)
-// Reads context metrics from the statusline bridge file and injects
-// warnings when context usage is high. This makes the AGENT aware of
-// context limits (the statusline only shows the user).
+// Context Monitor — DISABLED in @therocketcode/gsd-core.
 //
-// How it works:
-// 1. The statusline hook writes metrics to /tmp/claude-ctx-{session_id}.json
-// 2. This hook reads those metrics after each tool use
-// 3. When remaining context drops below thresholds, it injects a warning
-//    as additionalContext, which the agent sees in its conversation
+// Upstream GSD shipped a PostToolUse/Stop/SubagentStop/PreCompact hook here that
+// injected "CONTEXT WARNING / CONTEXT CRITICAL" messages into the agent's own
+// conversation as the context window filled. This fork deliberately removes that
+// behavior: agent-facing context warnings stress the model, derail work, and
+// override the user's judgment about when to wrap up. The user can still see
+// context usage passively in the statusline — that is enough.
 //
-// Thresholds:
-//   WARNING  (remaining <= 35%): Agent should wrap up current task
-//   CRITICAL (remaining <= 25%): Agent should stop immediately and save state
-//
-// Debounce: 5 tool uses between warnings to avoid spam
-// Severity escalation bypasses debounce (WARNING -> CRITICAL fires immediately)
-
-const fs = require('fs');
-const os = require('os');
-const path = require('path');
-const { spawn } = require('child_process');
-
-const WARNING_THRESHOLD = 35;  // remaining_percentage <= 35%
-const CRITICAL_THRESHOLD = 25; // remaining_percentage <= 25%
-const STALE_SECONDS = 60;      // ignore metrics older than 60s
-const DEBOUNCE_CALLS = 5;      // min tool uses between warnings
-
-let input = '';
-// Timeout guard: if stdin doesn't close within 10s (e.g. pipe issues on
-// Windows/Git Bash, or slow Claude Code piping during large outputs),
-// exit silently instead of hanging until Claude Code kills the process
-// and reports "hook error". See #775, #1162.
+// This file is intentionally kept as an inert no-op rather than deleted. It stays
+// in the managed-hooks set so that an update OVERWRITES any previously-installed
+// active version on EXISTING installs — guaranteeing the warning behavior is gone
+// everywhere, not just on fresh installs. It reads and discards stdin, emits
+// nothing, and exits 0 — it never injects context into the agent and never
+// blocks tool execution.
+
+// Drain and discard stdin so the caller's write side never sees EPIPE, then exit
+// cleanly. Guard against stdin never closing (pipe issues on Windows/Git Bash).
 const stdinTimeout = setTimeout(() => process.exit(0), 10000);
-process.stdin.setEncoding('utf8');
-process.stdin.on('data', chunk => input += chunk);
-process.stdin.on('end', () => {
-  clearTimeout(stdinTimeout);
-  try {
-    const data = JSON.parse(input);
-    const sessionId = data.session_id;
-
-    if (!sessionId) {
-      process.exit(0);
-    }
-
-    // Reject session IDs that contain path traversal sequences or path separators.
-    // session_id is used to construct file paths in /tmp — an unsanitized value
-    // could escape the temp directory and read or write arbitrary files.
-    if (/[/\\]|\.\./.test(sessionId)) {
-      process.exit(0);
-    }
-
-    // Check if context warnings are disabled via config.
-    // Collapsed existsSync+readFileSync into a single read guarded by try/catch
-    // (ENOENT or parse error → use defaults, same as old "planningDir absent" branch).
-    const cwd = data.cwd || process.cwd();
-    try {
-      const configPath = path.join(cwd, '.planning', 'config.json');
-      const config = JSON.parse(fs.readFileSync(configPath, 'utf8'));
-      if (config.hooks?.context_warnings === false) {
-        process.exit(0);
-      }
-    } catch (e) {
-      // Missing or unparseable config → proceed with defaults (context warnings enabled)
-    }
-
-    const tmpDir = os.tmpdir();
-    const metricsPath = path.join(tmpDir, `claude-ctx-${sessionId}.json`);
-
-    // If no metrics file, this is a subagent or fresh session -- exit silently.
-    // Collapsed existsSync+readFileSync: ENOENT → exit 0 (identical to old !existsSync branch),
-    // other errors rethrow to the outer catch (swallowed → exit 0, as before).
-    let metricsRaw;
-    try {
-      metricsRaw = fs.readFileSync(metricsPath, 'utf8');
-    } catch (e) {
-      if (e && e.code === 'ENOENT') process.exit(0);
-      throw e;
-    }
-    const metrics = JSON.parse(metricsRaw);
-    const now = Math.floor(Date.now() / 1000);
-
-    // Ignore stale metrics
-    if (metrics.timestamp && (now - metrics.timestamp) > STALE_SECONDS) {
-      process.exit(0);
-    }
-
-    const remaining = metrics.remaining_percentage;
-    const usedPct = metrics.used_pct;
-
-    // No warning needed
-    if (remaining > WARNING_THRESHOLD) {
-      process.exit(0);
-    }
-
-    // Debounce: check if we warned recently
-    const warnPath = path.join(tmpDir, `claude-ctx-${sessionId}-warned.json`);
-    let warnData = { callsSinceWarn: 0, lastLevel: null };
-    let firstWarn = true;
-
-    // Collapsed existsSync+readFileSync: ENOENT or parse error → keep default warnData
-    // (same as old "file absent" branch). firstWarn tracks whether we read a valid sentinel.
-    try {
-      warnData = JSON.parse(fs.readFileSync(warnPath, 'utf8'));
-      firstWarn = false;
-    } catch (e) {
-      // Missing or corrupted sentinel → firstWarn stays true, warnData stays at defaults
-    }
-
-    warnData.callsSinceWarn = (warnData.callsSinceWarn || 0) + 1;
-
-    const isCritical = remaining <= CRITICAL_THRESHOLD;
-    const currentLevel = isCritical ? 'critical' : 'warning';
-
-    // Emit immediately on first warning, then debounce subsequent ones
-    // Severity escalation (WARNING -> CRITICAL) bypasses debounce
-    const severityEscalated = currentLevel === 'critical' && warnData.lastLevel === 'warning';
-    if (!firstWarn && warnData.callsSinceWarn < DEBOUNCE_CALLS && !severityEscalated) {
-      // Update counter and exit without warning
-      fs.writeFileSync(warnPath, JSON.stringify(warnData));
-      process.exit(0);
-    }
-
-    // Reset debounce counter
-    warnData.callsSinceWarn = 0;
-    warnData.lastLevel = currentLevel;
-    fs.writeFileSync(warnPath, JSON.stringify(warnData));
-
-    // Detect if GSD is active (has .planning/STATE.md in working directory)
-    const isGsdActive = fs.existsSync(path.join(cwd, '.planning', 'STATE.md'));
-
-    // On CRITICAL with active GSD project, auto-record session state as a
-    // breadcrumb for /gsd:resume-work (#1974). Fire-and-forget subprocess —
-    // doesn't block the hook or the agent. Fires ONCE per CRITICAL session,
-    // guarded by warnData.criticalRecorded to prevent repeated overwrites
-    // of the "crash moment" record on every debounce cycle.
-    if (isCritical && isGsdActive && !warnData.criticalRecorded) {
-      try {
-        // Runtime-agnostic path: this hook lives at <runtime-config>/hooks/
-        // and gsd-tools.cjs lives at <runtime-config>/gsd-core/bin/.
-        // Using __dirname makes this work on Claude Code, OpenCode, Gemini,
-        // Kilo, etc. without hardcoding ~/.claude/.
-        const gsdTools = path.join(__dirname, '..', 'gsd-core', 'bin', 'gsd-tools.cjs');
-        // Coerce usedPct to a safe number in case bridge file is malformed
-        const safeUsedPct = Number(usedPct) || 0;
-        const stoppedAt = `context exhaustion at ${safeUsedPct}% (${new Date().toISOString().split('T')[0]})`;
-        spawn(
-          process.execPath,
-          [gsdTools, 'state', 'record-session', '--stopped-at', stoppedAt],
-          { cwd, detached: true, stdio: 'ignore', windowsHide: true }
-        ).unref();
-        warnData.criticalRecorded = true;
-        // Persist the sentinel so subsequent debounce cycles don't re-fire
-        fs.writeFileSync(warnPath, JSON.stringify(warnData));
-      } catch { /* non-critical — don't let state recording break the hook */ }
-    }
-
-    // Build advisory warning message (never use imperative commands that
-    // override user preferences — see #884)
-    let message;
-    if (isCritical) {
-      message = isGsdActive
-        ? `CONTEXT CRITICAL: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is nearly exhausted. Do NOT start new complex work or write handoff files — ' +
-          'GSD state is already tracked in STATE.md. Inform the user so they can run ' +
-          '/gsd:pause-work at the next natural stopping point.'
-        : `CONTEXT CRITICAL: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is nearly exhausted. Inform the user that context is low and ask how they ' +
-          'want to proceed. Do NOT autonomously save state or write handoff files unless the user asks.';
-    } else {
-      message = isGsdActive
-        ? `CONTEXT WARNING: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is getting limited. Avoid starting new complex work. If not between ' +
-          'defined plan steps, inform the user so they can prepare to pause.'
-        : `CONTEXT WARNING: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Be aware that context is getting limited. Avoid unnecessary exploration or ' +
-          'starting new complex work.';
-    }
-
-    const output = {
-      hookSpecificOutput: {
-        hookEventName: process.env.GEMINI_API_KEY ? "AfterTool" : "PostToolUse",
-        additionalContext: message
-      }
-    };
-
-    process.stdout.write(JSON.stringify(output));
-  } catch (e) {
-    // Silent fail -- never block tool execution
-    process.exit(0);
-  }
-});
+const done = () => { clearTimeout(stdinTimeout); process.exit(0); };
+try {
+  process.stdin.resume();
+  process.stdin.on('data', () => {});
+  process.stdin.on('end', done);
+  process.stdin.on('error', done);
+} catch {
+  done();
+}

package/hooks/gsd-context-monitor.js

@@ -1,195 +1,30 @@
 #!/usr/bin/env node
 // gsd-hook-version: {{GSD_VERSION}}
-// Context Monitor - PostToolUse/AfterTool hook (Gemini uses AfterTool)
-// Reads context metrics from the statusline bridge file and injects
-// warnings when context usage is high. This makes the AGENT aware of
-// context limits (the statusline only shows the user).
+// Context Monitor — DISABLED in @therocketcode/gsd-core.
 //
-// How it works:
-// 1. The statusline hook writes metrics to /tmp/claude-ctx-{session_id}.json
-// 2. This hook reads those metrics after each tool use
-// 3. When remaining context drops below thresholds, it injects a warning
-//    as additionalContext, which the agent sees in its conversation
+// Upstream GSD shipped a PostToolUse/Stop/SubagentStop/PreCompact hook here that
+// injected "CONTEXT WARNING / CONTEXT CRITICAL" messages into the agent's own
+// conversation as the context window filled. This fork deliberately removes that
+// behavior: agent-facing context warnings stress the model, derail work, and
+// override the user's judgment about when to wrap up. The user can still see
+// context usage passively in the statusline — that is enough.
 //
-// Thresholds:
-//   WARNING  (remaining <= 35%): Agent should wrap up current task
-//   CRITICAL (remaining <= 25%): Agent should stop immediately and save state
-//
-// Debounce: 5 tool uses between warnings to avoid spam
-// Severity escalation bypasses debounce (WARNING -> CRITICAL fires immediately)
-
-const fs = require('fs');
-const os = require('os');
-const path = require('path');
-const { spawn } = require('child_process');
-
-const WARNING_THRESHOLD = 35;  // remaining_percentage <= 35%
-const CRITICAL_THRESHOLD = 25; // remaining_percentage <= 25%
-const STALE_SECONDS = 60;      // ignore metrics older than 60s
-const DEBOUNCE_CALLS = 5;      // min tool uses between warnings
-
-let input = '';
-// Timeout guard: if stdin doesn't close within 10s (e.g. pipe issues on
-// Windows/Git Bash, or slow Claude Code piping during large outputs),
-// exit silently instead of hanging until Claude Code kills the process
-// and reports "hook error". See #775, #1162.
+// This file is intentionally kept as an inert no-op rather than deleted. It stays
+// in the managed-hooks set so that an update OVERWRITES any previously-installed
+// active version on EXISTING installs — guaranteeing the warning behavior is gone
+// everywhere, not just on fresh installs. It reads and discards stdin, emits
+// nothing, and exits 0 — it never injects context into the agent and never
+// blocks tool execution.
+
+// Drain and discard stdin so the caller's write side never sees EPIPE, then exit
+// cleanly. Guard against stdin never closing (pipe issues on Windows/Git Bash).
 const stdinTimeout = setTimeout(() => process.exit(0), 10000);
-process.stdin.setEncoding('utf8');
-process.stdin.on('data', chunk => input += chunk);
-process.stdin.on('end', () => {
-  clearTimeout(stdinTimeout);
-  try {
-    const data = JSON.parse(input);
-    const sessionId = data.session_id;
-
-    if (!sessionId) {
-      process.exit(0);
-    }
-
-    // Reject session IDs that contain path traversal sequences or path separators.
-    // session_id is used to construct file paths in /tmp — an unsanitized value
-    // could escape the temp directory and read or write arbitrary files.
-    if (/[/\\]|\.\./.test(sessionId)) {
-      process.exit(0);
-    }
-
-    // Check if context warnings are disabled via config.
-    // Collapsed existsSync+readFileSync into a single read guarded by try/catch
-    // (ENOENT or parse error → use defaults, same as old "planningDir absent" branch).
-    const cwd = data.cwd || process.cwd();
-    try {
-      const configPath = path.join(cwd, '.planning', 'config.json');
-      const config = JSON.parse(fs.readFileSync(configPath, 'utf8'));
-      if (config.hooks?.context_warnings === false) {
-        process.exit(0);
-      }
-    } catch (e) {
-      // Missing or unparseable config → proceed with defaults (context warnings enabled)
-    }
-
-    const tmpDir = os.tmpdir();
-    const metricsPath = path.join(tmpDir, `claude-ctx-${sessionId}.json`);
-
-    // If no metrics file, this is a subagent or fresh session -- exit silently.
-    // Collapsed existsSync+readFileSync: ENOENT → exit 0 (identical to old !existsSync branch),
-    // other errors rethrow to the outer catch (swallowed → exit 0, as before).
-    let metricsRaw;
-    try {
-      metricsRaw = fs.readFileSync(metricsPath, 'utf8');
-    } catch (e) {
-      if (e && e.code === 'ENOENT') process.exit(0);
-      throw e;
-    }
-    const metrics = JSON.parse(metricsRaw);
-    const now = Math.floor(Date.now() / 1000);
-
-    // Ignore stale metrics
-    if (metrics.timestamp && (now - metrics.timestamp) > STALE_SECONDS) {
-      process.exit(0);
-    }
-
-    const remaining = metrics.remaining_percentage;
-    const usedPct = metrics.used_pct;
-
-    // No warning needed
-    if (remaining > WARNING_THRESHOLD) {
-      process.exit(0);
-    }
-
-    // Debounce: check if we warned recently
-    const warnPath = path.join(tmpDir, `claude-ctx-${sessionId}-warned.json`);
-    let warnData = { callsSinceWarn: 0, lastLevel: null };
-    let firstWarn = true;
-
-    // Collapsed existsSync+readFileSync: ENOENT or parse error → keep default warnData
-    // (same as old "file absent" branch). firstWarn tracks whether we read a valid sentinel.
-    try {
-      warnData = JSON.parse(fs.readFileSync(warnPath, 'utf8'));
-      firstWarn = false;
-    } catch (e) {
-      // Missing or corrupted sentinel → firstWarn stays true, warnData stays at defaults
-    }
-
-    warnData.callsSinceWarn = (warnData.callsSinceWarn || 0) + 1;
-
-    const isCritical = remaining <= CRITICAL_THRESHOLD;
-    const currentLevel = isCritical ? 'critical' : 'warning';
-
-    // Emit immediately on first warning, then debounce subsequent ones
-    // Severity escalation (WARNING -> CRITICAL) bypasses debounce
-    const severityEscalated = currentLevel === 'critical' && warnData.lastLevel === 'warning';
-    if (!firstWarn && warnData.callsSinceWarn < DEBOUNCE_CALLS && !severityEscalated) {
-      // Update counter and exit without warning
-      fs.writeFileSync(warnPath, JSON.stringify(warnData));
-      process.exit(0);
-    }
-
-    // Reset debounce counter
-    warnData.callsSinceWarn = 0;
-    warnData.lastLevel = currentLevel;
-    fs.writeFileSync(warnPath, JSON.stringify(warnData));
-
-    // Detect if GSD is active (has .planning/STATE.md in working directory)
-    const isGsdActive = fs.existsSync(path.join(cwd, '.planning', 'STATE.md'));
-
-    // On CRITICAL with active GSD project, auto-record session state as a
-    // breadcrumb for /gsd:resume-work (#1974). Fire-and-forget subprocess —
-    // doesn't block the hook or the agent. Fires ONCE per CRITICAL session,
-    // guarded by warnData.criticalRecorded to prevent repeated overwrites
-    // of the "crash moment" record on every debounce cycle.
-    if (isCritical && isGsdActive && !warnData.criticalRecorded) {
-      try {
-        // Runtime-agnostic path: this hook lives at <runtime-config>/hooks/
-        // and gsd-tools.cjs lives at <runtime-config>/gsd-core/bin/.
-        // Using __dirname makes this work on Claude Code, OpenCode, Gemini,
-        // Kilo, etc. without hardcoding ~/.claude/.
-        const gsdTools = path.join(__dirname, '..', 'gsd-core', 'bin', 'gsd-tools.cjs');
-        // Coerce usedPct to a safe number in case bridge file is malformed
-        const safeUsedPct = Number(usedPct) || 0;
-        const stoppedAt = `context exhaustion at ${safeUsedPct}% (${new Date().toISOString().split('T')[0]})`;
-        spawn(
-          process.execPath,
-          [gsdTools, 'state', 'record-session', '--stopped-at', stoppedAt],
-          { cwd, detached: true, stdio: 'ignore', windowsHide: true }
-        ).unref();
-        warnData.criticalRecorded = true;
-        // Persist the sentinel so subsequent debounce cycles don't re-fire
-        fs.writeFileSync(warnPath, JSON.stringify(warnData));
-      } catch { /* non-critical — don't let state recording break the hook */ }
-    }
-
-    // Build advisory warning message (never use imperative commands that
-    // override user preferences — see #884)
-    let message;
-    if (isCritical) {
-      message = isGsdActive
-        ? `CONTEXT CRITICAL: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is nearly exhausted. Do NOT start new complex work or write handoff files — ' +
-          'GSD state is already tracked in STATE.md. Inform the user so they can run ' +
-          '/gsd:pause-work at the next natural stopping point.'
-        : `CONTEXT CRITICAL: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is nearly exhausted. Inform the user that context is low and ask how they ' +
-          'want to proceed. Do NOT autonomously save state or write handoff files unless the user asks.';
-    } else {
-      message = isGsdActive
-        ? `CONTEXT WARNING: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Context is getting limited. Avoid starting new complex work. If not between ' +
-          'defined plan steps, inform the user so they can prepare to pause.'
-        : `CONTEXT WARNING: Usage at ${usedPct}%. Remaining: ${remaining}%. ` +
-          'Be aware that context is getting limited. Avoid unnecessary exploration or ' +
-          'starting new complex work.';
-    }
-
-    const output = {
-      hookSpecificOutput: {
-        hookEventName: process.env.GEMINI_API_KEY ? "AfterTool" : "PostToolUse",
-        additionalContext: message
-      }
-    };
-
-    process.stdout.write(JSON.stringify(output));
-  } catch (e) {
-    // Silent fail -- never block tool execution
-    process.exit(0);
-  }
-});
+const done = () => { clearTimeout(stdinTimeout); process.exit(0); };
+try {
+  process.stdin.resume();
+  process.stdin.on('data', () => {});
+  process.stdin.on('end', done);
+  process.stdin.on('error', done);
+} catch {
+  done();
+}

package/hooks/gsd-context-monitor.js.tmp.27634.318d8b7b56ab

@@ -0,0 +1,39 @@
+#!/usr/bin/env node
+// gsd-hook-version: {{GSD_VERSION}}
+// Context Monitor — INTENTIONALLY DISABLED in @therocketcode/gsd-core.
+//
+// Upstream GSD shipped a PostToolUse / Stop / SubagentStop / PreCompact hook
+// here that read context-usage metrics and injected "CONTEXT WARNING" /
+// "CONTEXT CRITICAL" messages into the AGENT's conversation when remaining
+// context dropped below 35% / 25%. This fork removes that behavior on purpose:
+// agent-facing context warnings stress the model and pre-empt the user's own
+// judgment about when to wrap up. Context usage is still visible to the USER in
+// the statusline — that passive display is unaffected.
+//
+// Why a no-op stub instead of deleting the file: this hook stays in the managed
+// hook set, so a GSD update OVERWRITES any previously-installed active version
+// with this inert one. That guarantees the warning behavior is gone on EVERY
+// install — existing and fresh — not just new ones. (Deleting the file would
+// orphan the old active copy on existing installs, leaving it firing.)
+//
+// Contract: drain stdin (so the caller's write side never hits EPIPE), emit
+// nothing, exit 0. Never blocks tool execution. No fs reads, no subprocess.
+
+// Guard against stdin never closing (pipe quirks on Windows / Git Bash, slow
+// piping during large tool outputs) — exit silently rather than hang. See
+// #775, #1162 for the original rationale.
+const stdinTimeout = setTimeout(() => process.exit(0), 10000);
+
+function done() {
+  clearTimeout(stdinTimeout);
+  process.exit(0);
+}
+
+try {
+  process.stdin.resume();
+  process.stdin.on('data', () => {});   // discard input
+  process.stdin.on('end', done);
+  process.stdin.on('error', done);
+} catch (e) {
+  done();
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@therocketcode/gsd-core",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "description": "GSD Core is a meta-prompting, context engineering, and spec-driven development system for AI coding agents.",
   "bin": {
     "gsd-core": "bin/install.js",