@tekyzinc/gsd-t 5.12.10 → 5.12.11

package/CHANGELOG.md

@@ -2,6 +2,34 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [5.12.11] - 2026-08-22
+
+### Fixed — the architect could finish its work and leave nothing, silently
+
+Five consecutive architect runs looked like an idle session. The event log
+showed the opposite of a crash: the architect subagents spawned, worked for
+minutes, and logged `subagent_complete` every time — yet no artifact was
+written, and the session then sat silent.
+
+Nothing in the command ever asked whether the subagent had answered. Step 4
+spawned it and Step 6 assumed output existed, so a subagent that returned only
+chat text — or nothing at all — produced a silent session with no error. That
+is the shape the No-Fallback-Ever doctrine exists to forbid: a failure that
+continues instead of stopping loudly.
+
+- `commands/gsd-t-architect.md`: new step 4a halts on an empty or partial
+  return, naming what is missing, and explicitly bars substituting a
+  self-authored summary (that is not the fresh-context assessment the user
+  asked for). Step 6 now requires the artifact write to be PROVEN on disk
+  before presenting, halting with the missing path if it is not there.
+- `.gsd-t/pseudocode/PseudoCode-SharedLocalConfig.md`: behaviour map for one
+  shared local settings file per project, linked into every worktree; gloss
+  placement fixed to satisfy the style gate.
+
+The root cause of the empty return is not yet known — it lives in the session
+transcript. These halts make the next occurrence report itself instead of
+going quiet.
+
 ## [5.12.10] - 2026-08-19
 
 ### Added — naming an existing worktree walks you into it

package/README.md

@@ -1,6 +1,6 @@
 # GSD-T: Contract-Driven Development for Claude Code
 
-**v5.12.10** - A methodology for reliable, parallelizable development using Claude Code with optional Agent Teams support.
+**v5.12.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/commands/gsd-t-architect.md

@@ -261,6 +261,26 @@ Graph note: if a code graph exists (`.gsd-t/graphDB/graph.db` — resolve via
 reuse/caller queries (Stage 3 + Stage 5 duplication check). If absent, it greps/reads and says so
 LOUDLY (reuse-detection is reduced — never a silent "nothing found").
 
+### 4a — The subagent came back: CHECK IT, never assume
+
+**A run that produces nothing must SAY SO. Ending the turn silently is the failure this step
+exists to stop** — five consecutive architect runs once returned nothing, each looking like an
+idle session, because no step ever asked whether the subagent had answered.
+
+The moment the subagent returns, before any other work:
+
+1. **Did it return anything at all?** An empty return, a return that is only a status line, or no
+   return (the subagent died on an API error) → **HALT**. Say plainly: the architect subagent
+   produced no assessment, name the target, and stop. Do NOT retry silently, do NOT write a
+   summary from your own reading of the code — a summary you wrote yourself is not the
+   fresh-context assessment the user asked for, and presenting it as one is worse than the
+   silence.
+2. **Does it contain the required parts?** The Six-Stage answers and a `Simply Stated` lead. A
+   return that skips stages is a partial result → say which stages are missing, then HALT.
+
+**Never end the turn without either an assessment or a stated reason there is none.** Silence is
+indistinguishable from a hang, and the user cannot tell whether to wait or re-run.
+
 ---
 
 ## Step 5: The subagent runs the Six-Stage Pass (with EVIDENCE, never conviction)
@@ -366,6 +386,12 @@ the artifact to `.gsd-t/pseudocode/PseudoCode-<Target>.md`, then **self-check it
 `gsd-t pseudocode-style --doc <the file>` — a non-zero exit means the style is wrong; fix it
 before presenting. (The same gate is FAIL-blocking in verify.)
 
+**Writing it is not optional, and the write must be PROVEN, not assumed.** Unless `--chat-only`,
+confirm the file is on disk (`ls -la` it) before presenting anything. **A file that is not there
+is a HALT** — say the assessment was produced but the artifact never landed, and name the path
+that is missing. An assessment that exists only as chat text is lost the moment the session is
+cleared, which is exactly how a run that did all its work still leaves nothing behind.
+
 **B — Session summary** (always printed, even under `--build`):
 - **Simply Stated** (REQUIRED FIRST LINE — the clarity gate) — the verdict + the single most
   important finding in ONE clean, jargon-free, straight-line statement a smart non-specialist

package/package.json

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