@tekyzinc/gsd-t 5.16.11 → 5.16.12

package/CHANGELOG.md

@@ -2,6 +2,41 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [5.16.12] - 2026-08-29
+
+### Fixed — a retired hook fired on every tool call, on every machine, since M61
+
+An audit of installed hooks against what the installer registers found all 16
+expected hooks present and correct — plus one that should not have been there.
+
+M61 deleted `scripts/gsd-t-context-meter.js` (native `/context` replaced it) and
+unwired the subsystem from `init()` and `doctor()`. `install()` was missed, so it
+kept calling `configureContextMeterHooks()` and re-adding a `PostToolUse` hook
+matching `*` on every install and every update.
+
+**It never errored, which is why it survived eight months.** The command is
+guarded `[ -f … ] && node … || true`, so on every single tool call it spawned a
+bash + `npm root -g` subprocess, found nothing, and exited 0 silently — a real
+cost with no signal.
+
+The fix is two parts, because dropping the registration alone fixes nobody: a
+machine that installed the hook once keeps running it out of its own
+`settings.json`, and the installer is the only thing that reaches those machines.
+
+- `bin/gsd-t.js`: removed the `configureContextMeterHooks()` call from `install()`
+- `bin/gsd-t.js`: added the marker to `removeRetiredHooks()`, so existing machines
+  get it stripped on their next install — the same mechanism that retired the
+  M105 worktree guard
+- `bin/gsd-t.js`: exported `removeRetiredHooks` — it was not testable from
+  outside at all, which is part of why this went unnoticed
+- `test/m61-context-meter-hook-retired.test.js`: 6 regression tests, mutation-tested
+  by reverting each half of the fix
+- `.gsd-t/contracts/graph-metrics-contract.md`: stale line citation for `doMetrics`
+  (:5486 → :5488), shifted by the edit above and caught by the M99 contract-line test
+
+`configureContextMeterHooks` and `removeContextMeterHook` stay defined for the
+uninstall path. No migration needed — the next `gsd-t update` removes the hook.
+
 ## [5.16.11] - 2026-08-27
 
 ### Fixed — the voice fix was the wrong fix, and the gate was measuring the wrong thing

package/README.md

@@ -1,6 +1,6 @@
 # GSD-T: Contract-Driven Development for Claude Code
 
-**v5.16.11** - A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
+**v5.16.12** - A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
 
 **Eliminates context rot** — task-level fresh dispatch (one subagent per task, ~10-20% context each) means compaction never triggers.
 **Compaction-proof debug loops** — `gsd-t headless --debug-loop` runs test-fix-retest cycles as separate `claude -p` sessions. A JSONL debug ledger persists all hypothesis/fix/learning history across fresh sessions. Anti-repetition preamble injection prevents retrying failed hypotheses. Escalation tiers (sonnet → opus → human) and a hard iteration ceiling enforced externally.

package/bin/gsd-t.js

@@ -1205,11 +1205,16 @@ function removeInterceptHooks(settingsPath) {
 //   session signal, but subagents write those too, so one session with agents
 //   looked like several colliding sessions and the guard blocked its own user.
 //
+//   gsd-t-context-meter — M61, script deleted; native /context replaced it.
+//   init() stopped provisioning it then, but install() kept re-registering it,
+//   so every machine still runs it on EVERY tool call: a bash + `npm root -g`
+//   subprocess spawned to look for a file that no longer ships.
+//
 // Throws on any failure. A retired hook that silently survives keeps blocking
 // edits forever, so "could not remove it" must stop the install loudly rather
 // than report success.
 function removeRetiredHooks(settingsPath) {
-  const RETIRED_HOOK_MARKERS = ["gsd-t-worktree-guard"];
+  const RETIRED_HOOK_MARKERS = ["gsd-t-worktree-guard", CONTEXT_METER_HOOK_MARKER];
   const targetPath = settingsPath || SETTINGS_JSON;
   if (!fs.existsSync(targetPath)) return { removed: 0 };
 
@@ -2285,13 +2290,10 @@ async function doInstall(opts = {}) {
   heading("Global Bin Tools (~/.claude/bin/)");
   installGlobalBinTools();
 
-  heading("Context Meter (PostToolUse)");
-  const cmHook = configureContextMeterHooks(SETTINGS_JSON);
-  if (cmHook.installed) {
-    if (cmHook.action === "added") success("Context meter PostToolUse hook added");
-    else if (cmHook.action === "updated") success("Context meter hook command refreshed");
-    else info("Context meter hook already configured");
-  }
+  // M61: Context Meter retired (scripts/gsd-t-context-meter.js deleted; native
+  // /context replaces it). The configureContextMeterHooks() call that stood here
+  // re-registered a PostToolUse hook pointing at that deleted script on every
+  // install. removeRetiredHooks() below now strips it instead.
 
   heading("Graph-Intercept (PostToolUse on Grep — M97)");
   const giHook = configureGraphInterceptHook(SETTINGS_JSON);
@@ -2318,7 +2320,7 @@ async function doInstall(opts = {}) {
 
   const retired = removeRetiredHooks(SETTINGS_JSON);
   if (retired.removed > 0) {
-    success(`Removed ${retired.removed} retired hook(s) from settings.json (worktree-collision guard — M105)`);
+    success(`Removed ${retired.removed} retired hook(s) from settings.json (worktree-collision guard — M105; context meter — M61)`);
   }
 
   // M105 worktree-collision guard RETIRED (2026-08-08). It detected sessions from
@@ -5610,6 +5612,7 @@ module.exports = {
   installContextMeter,
   configureContextMeterHooks,
   removeContextMeterHook,
+  removeRetiredHooks,
   // M97/M98: intercept hook installers
   configureGraphInterceptHook,
   configureReadInterceptHook,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "5.16.11",
+  "version": "5.16.12",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 54 slash commands with headless-by-default workflow spawning, unattended supervisor relay with event stream, graph-powered code analysis, real-time agent dashboard, task telemetry, doc-ripple enforcement, backlog management, impact analysis, test sync, milestone archival, and PRD generation",
   "author": "Tekyz, Inc.",
   "license": "MIT",