@tekyzinc/gsd-t 5.11.10 → 5.11.11

package/CHANGELOG.md

@@ -2,6 +2,40 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [5.11.11] - 2026-08-09
+
+### Fixed — the reply shortener was shortening itself
+
+The child Claude was started with the personal settings, which carry the very
+Stop hook that spawned it. It answered in about 4 seconds, its own hook then saw
+an answer over the 60-word threshold and spawned a THIRD Claude, and the outer
+call waited ~46s for work it had caused — past its own 45s limit, so it was
+killed and returned nothing. Every turn, since the day it shipped.
+
+`--setting-sources project` starts the child without the personal layer.
+Measured twice each: **54.2s/54.5s before, 7.9s/6.2s after**; through the real
+hook, 8.6s / 10.1s / 10.8s, all producing a rewrite.
+
+The trigger was always the child's own REPLY crossing 60 words, never the input
+text — a 63-character prompt that produces a long answer is just as slow.
+
+Two flags rejected by measurement and recorded so they are not retried: `--bare`
+skips the keychain and the child answers "Not logged in"; `--settings '{}'`
+cannot remove an inherited hook, because settings layers merge.
+
+The `--disallowed-tools` flag from 5.11.10 is removed — its root cause was
+disproved (52.6s with, 52.5s without), and leaving it would enshrine a wrong
+explanation.
+
+Separately: the hook captured the rewriter's stderr into a pipe it never read,
+so the loud timeout warning added in 5.11.10 reached nobody. It is inherited
+now — the let-it-through paths are approved passes *because* the reader can see
+them happen.
+
+- `bin/gsd-t-concise-rewrite.cjs`: the child no longer inherits the hook that spawned it
+- `scripts/gsd-t-concise-hook.js`: the child's stderr reaches the screen
+- `test/m107-concise-rewrite.test.js`: 3 tests pin the recursion, the two rejected flags, the stderr
+
 ## [5.11.10] - 2026-08-09
 
 ### Fixed — four safety gates were passing without checking anything

package/README.md

@@ -1,6 +1,6 @@
 # GSD-T: Contract-Driven Development for Claude Code
 
-**v5.11.10** - A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
+**v5.11.11** - 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-concise-rewrite.cjs

@@ -136,23 +136,29 @@ function checkInvariants(original, rewritten) {
   return lost;
 }
 
-// Shortening prose needs no tools. Left able to use them, the rewriter read the
-// file paths and commands INSIDE the reply as work to do and went off running
-// them — 41 seconds, killed on timeout, empty output and empty stderr, on every
-// turn for two days. Forbidding tools returns the same rewrite in about 7
-// seconds. The list is explicit rather than a mode flag so a newly added tool
-// cannot quietly re-open the same hole.
-const NO_TOOLS = [
-  "Bash", "Read", "Write", "Edit", "NotebookEdit", "Glob", "Grep",
-  "Task", "Agent", "WebFetch", "WebSearch", "TodoWrite",
-].join(",");
-
 /** Ask a fresh Claude to do the rewrite. */
 function rewrite(text, cfg) {
   const prompt = `${RULES}\n\n--- REPLY TO REWRITE ---\n${text}`;
+  // `--setting-sources project` is what stops the shortener shortening itself.
+  //
+  // A child started with the personal settings inherits the very Stop hook that
+  // spawned it: it answers in about 4 seconds, its own hook then sees an answer
+  // over the 60-word threshold and spawns a THIRD Claude, and the outer call
+  // waits ~46s for work it caused — past the 45s limit, so it was killed and
+  // returned nothing, every turn since it shipped. Measured: 54.2s/54.5s with
+  // the personal settings, 7.9s/6.2s with only the project's.
+  //
+  // The trigger was always the CHILD'S OWN REPLY crossing 60 words, never the
+  // input: a 63-character prompt that produces a long answer is just as slow
+  // (57.2s on, 11.7s off).
+  //
+  // Not `--bare`, the documented skip-hooks flag: it also skips the keychain, so
+  // the child returns "Not logged in" in 0.7s. Not `--settings '{}'` either —
+  // settings layers merge, so a lower layer cannot remove a higher layer's hook
+  // (54.5s/56.1s, unchanged).
   const run = spawnSync("claude",
     ["-p", prompt, "--model", cfg.model, "--dangerously-skip-permissions",
-     "--disallowed-tools", NO_TOOLS],
+     "--setting-sources", "project"],
     { encoding: "utf8", timeout: cfg.timeoutMs, maxBuffer: 8 * 1024 * 1024 });
 
   if (run.error) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "5.11.10",
+  "version": "5.11.11",
   "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",

package/scripts/gsd-t-concise-hook.js

@@ -214,9 +214,15 @@ function main() {
     const rewriter = findRewriter(cwd);
     if (!rewriter) return allow();
 
+    // The rewriter's own warnings go to stderr. Captured into a pipe and never
+    // read, they reach nobody — which is why the timeouts stayed invisible even
+    // after a loud message was added for them. Letting the child write straight
+    // to this process's stderr is what makes a give-up path visible; these paths
+    // are approved passes precisely BECAUSE the reader can see them happen.
     const run = spawnSync(process.execPath,
       [rewriter, "--text", last.text, "--project", cwd, "--json"],
-      { encoding: "utf8", timeout: 60000, maxBuffer: 8 * 1024 * 1024 });
+      { encoding: "utf8", timeout: 60000, maxBuffer: 8 * 1024 * 1024,
+        stdio: ["ignore", "pipe", "inherit"] });
 
     if (run.error || !run.stdout) return allow();