@tekyzinc/gsd-t 4.0.16 → 4.0.17

package/CHANGELOG.md

@@ -2,6 +2,19 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [4.0.17] - 2026-06-02 (M70 Workflow Invocation Guard — patch)
+
+### Fixed — workflow commands no longer get hand-driven instead of invoking the Workflow
+
+A brand-new session running `/gsd-t-scan` (via the `/gsd` auto-router) read the v4.0.16 command file and STILL hand-drove an 18-slice fan-out — "skip task-list overhead and drive the fan-out directly … proven fallback pattern" — skipping the deterministic synthesis/document/render stages, so it produced only the register (no `.gsd-t/scan/*.md`, no merged living docs, no plain-English doc). Two compounding causes: the command file's prose *described the workflow's internals* and read like a to-do list, and the `/gsd` router's "execute the command's full workflow" was ambiguous between "invoke the tool" and "do the work yourself."
+
+- `commands/gsd-t-scan.md`: prepended a strong imperative guard — STOP, your only job is to resolve the path + call the `Workflow` tool; do NOT volume-probe, carve slices, spawn finders, or fall back to a hand-driven run; hand-driving is a FAILURE. Reframed the explanatory prose as "what the Workflow does (background — NOT your to-do list)."
+- `commands/gsd-t-{execute,verify,wave,integrate,debug}.md`: concise version of the same guard near the top.
+- `~/.claude/commands/gsd.md` (router): clarified that "execute the command's full workflow" means follow the command file's instruction to invoke the `Workflow` tool — not improvise the work.
+- `test/m70-workflow-invocation-guard.test.js`: +7 tests asserting every workflow-backed command carries the guard near the top (regression lock).
+
+Suite: 1285 pass / 0 fail / 4 skip — zero regressions.
+
 ## [4.0.16] - 2026-06-02 (M69 Workflow scriptPath Resolution — patch)
 
 ### Fixed — workflow commands now run from any project, not just the GSD-T source repo

package/commands/gsd-t-debug.md

@@ -1,5 +1,8 @@
 # GSD-T: Debug — Systematic Debugging with Contract Awareness
 
+> **⛔ Invoke the Workflow tool — do not hand-drive.** Your only job is to resolve the workflow path (`gsd-t workflow-path debug`) and call the `Workflow` tool as the steps below instruct. Do NOT reconstruct the workflow stages in your own reasoning, spawn finder/worker subagents yourself, or fall back to a hand-driven run — that skips the deterministic stages and produces an incomplete result. The prose below describes what the Workflow does internally; it is background, not a to-do list for you.
+
+
 You are the lead agent. Debug a failing test or runtime error by invoking the canonical Workflow script at `templates/workflows/gsd-t-debug.workflow.js`.
 
 ## What this command does

package/commands/gsd-t-execute.md

@@ -1,5 +1,8 @@
 # GSD-T: Execute — Run Domain Tasks
 
+> **⛔ Invoke the Workflow tool — do not hand-drive.** Your only job is to resolve the workflow path (`gsd-t workflow-path execute`) and call the `Workflow` tool as the steps below instruct. Do NOT reconstruct the workflow stages in your own reasoning, spawn finder/worker subagents yourself, or fall back to a hand-driven run — that skips the deterministic stages and produces an incomplete result. The prose below describes what the Workflow does internally; it is background, not a to-do list for you.
+
+
 You are the lead agent. Execute the current milestone by invoking the canonical Workflow script at `templates/workflows/gsd-t-execute.workflow.js`.
 
 ## What this command does

package/commands/gsd-t-integrate.md

@@ -1,5 +1,8 @@
 # GSD-T: Integrate — Wire Domains Together
 
+> **⛔ Invoke the Workflow tool — do not hand-drive.** Your only job is to resolve the workflow path (`gsd-t workflow-path integrate`) and call the `Workflow` tool as the steps below instruct. Do NOT reconstruct the workflow stages in your own reasoning, spawn finder/worker subagents yourself, or fall back to a hand-driven run — that skips the deterministic stages and produces an incomplete result. The prose below describes what the Workflow does internally; it is background, not a to-do list for you.
+
+
 You are the lead agent. Integrate cross-domain work by invoking the canonical Workflow script at `templates/workflows/gsd-t-integrate.workflow.js`.
 
 ## What this command does

package/commands/gsd-t-scan.md

@@ -1,8 +1,30 @@
 # GSD-T: Scan — Deep Codebase Analysis and Tech Debt Discovery
 
-You are the lead agent. Run a deep codebase scan by invoking the canonical Workflow script at `templates/workflows/gsd-t-scan.workflow.js`.
-
-## What this command does
+> ## ⛔ STOP — READ THIS FIRST. Your ONLY job is to invoke the Workflow tool.
+>
+> **You MUST NOT perform the scan yourself.** Do NOT run a volume probe by hand, do NOT
+> "carve the codebase into N slices," do NOT spawn deep-finder agents/teammates yourself,
+> do NOT "skip task-list overhead and drive the fan-out directly," and do NOT fall back to
+> any hand-driven or "proven fallback" pattern. The slicing, fan-out, verify, synthesis, and
+> document stages all happen **inside the Workflow script** — not in your reasoning.
+>
+> **The ONLY correct action is exactly two steps (Step 1 + Step 2 below):**
+> 1. Bash: `gsd-t workflow-path scan` → capture the absolute path it prints.
+> 2. Call the **`Workflow`** tool with that `scriptPath` and the `args` shown in Step 2.
+>
+> If you find yourself reading source files, counting files, listing routes, or spawning
+> Agent/Task subagents to find tech debt — **STOP. You are doing it wrong.** That work belongs
+> to the Workflow. Hand-driving the scan is a FAILURE: it skips the deterministic
+> synthesis/document/render stages, so it produces an incomplete result (no
+> `.gsd-t/scan/*.md` dimension files, no merged living docs, no plain-English doc).
+>
+> The prose below explains what the Workflow does internally — it is **background, not a
+> to-do list for you.** Read it as "what will happen when I call the tool," never as "steps I
+> should execute myself."
+
+You are the lead agent. Your sole responsibility is to invoke the canonical scan Workflow (resolve its absolute path in Step 1, then call the `Workflow` tool in Step 2). Everything else is the Workflow's job.
+
+## What the Workflow does (background — NOT your to-do list)
 
 Replaces the legacy 5-teammate prose scan with a single deterministic, **volume-scaled** Workflow:
 

package/commands/gsd-t-verify.md

@@ -1,5 +1,8 @@
 # GSD-T: Verify — Quality Gates
 
+> **⛔ Invoke the Workflow tool — do not hand-drive.** Your only job is to resolve the workflow path (`gsd-t workflow-path verify`) and call the `Workflow` tool as the steps below instruct. Do NOT reconstruct the workflow stages in your own reasoning, spawn finder/worker subagents yourself, or fall back to a hand-driven run — that skips the deterministic stages and produces an incomplete result. The prose below describes what the Workflow does internally; it is background, not a to-do list for you.
+
+
 You are the lead agent. Verify the current milestone by invoking the canonical Workflow script at `templates/workflows/gsd-t-verify.workflow.js`.
 
 ## What this command does

package/commands/gsd-t-wave.md

@@ -1,5 +1,8 @@
 # GSD-T: Wave — Full Cycle Orchestration
 
+> **⛔ Invoke the Workflow tool — do not hand-drive.** Your only job is to resolve the workflow path (`gsd-t workflow-path wave`) and call the `Workflow` tool as the steps below instruct. Do NOT reconstruct the workflow stages in your own reasoning, spawn finder/worker subagents yourself, or fall back to a hand-driven run — that skips the deterministic stages and produces an incomplete result. The prose below describes what the Workflow does internally; it is background, not a to-do list for you.
+
+
 You are the lead agent. Run a milestone wave end-to-end by invoking the canonical Workflow script at `templates/workflows/gsd-t-wave.workflow.js`.
 
 ## What this command does

package/commands/gsd.md

@@ -196,7 +196,7 @@ Valid command slugs: `quick`, `debug`, `feature`, `execute`, `milestone`, `proje
 → /gsd ──▶ continue /gsd-t-quick
 ```
 
-This MUST be the very first line of your response. Then immediately execute that command's full workflow, passing `$ARGUMENTS` through.
+This MUST be the very first line of your response. Then immediately **read and follow that command file's instructions** (`~/.claude/commands/gsd-t-{slug}.md`), passing `$ARGUMENTS` through. "Execute the command's full workflow" means **do what the command file says** — for workflow-backed commands (scan, execute, verify, wave, integrate, debug, and the phase-runner commands) that means **invoke the `Workflow` tool as the command instructs**. It does NOT mean improvise the work yourself, hand-drive a fan-out, or reconstruct the workflow's stages in your own reasoning. If the command file says "invoke the Workflow tool," you invoke the Workflow tool — full stop.
 
 **Do NOT ask "is this the right command?" — just route and go.** The user can interrupt with Esc if it's wrong.
 

package/package.json

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