@tekyzinc/gsd-t 2.24.8 → 2.28.13

package/templates/CLAUDE-global.md

@@ -55,6 +55,8 @@ PROJECT or FEATURE or SCAN
 | `/user:gsd-t-status` | Cross-domain progress view |
 | `/user:gsd-t-debug` | Systematic debugging |
 | `/user:gsd-t-quick` | Fast task, respects contracts |
+| `/user:gsd-t-health` | Validate .gsd-t/ structure, optionally repair |
+| `/user:gsd-t-pause` | Save exact position for reliable resume |
 | `/user:gsd-t-populate` | Auto-populate docs from existing codebase |
 | `/user:gsd-t-log` | Sync progress Decision Log with recent git activity |
 | `/user:gsd-t-resume` | Restore context, continue |
@@ -109,11 +111,13 @@ GSD-T tracks project version in `.gsd-t/progress.md` using semantic versioning:
 
 | Segment | Bumped When | Example |
 |---------|-------------|---------|
-| **Major** | Breaking changes, major rework, v1 launch | 1.0.0 → 2.0.0 |
-| **Minor** | New features, completed feature milestones | 1.1.0 → 1.2.0 |
-| **Patch** | Bug fixes, minor improvements, cleanup | 1.1.1 → 1.1.2 |
+| **Major** | Breaking changes, major rework, v1 launch | 1.0.10 → 2.0.10 |
+| **Minor** | New features, completed feature milestones | 1.10.10 → 1.11.10 |
+| **Patch** | Bug fixes, minor improvements, cleanup | 1.1.10 → 1.1.11 |
 
-- Version is set during `gsd-t-init` (starts at `0.1.0`)
+**Patch convention**: Patch numbers are always 2 digits (≥10). When resetting after a minor or major bump, start at **10** (not 0). This keeps patches always 2 characters without leading zeros, so semver stays valid.
+
+- Version is set during `gsd-t-init` (starts at `0.1.10`)
 - Version is bumped during `gsd-t-complete-milestone` based on milestone scope
 - Version is reflected in: `progress.md`, `README.md`, package manifest (if any), and git tags (`v{version}`)
 
@@ -222,20 +226,24 @@ This applies everywhere Playwright tests are executed: execute, test-sync, verif
 
 ## QA Agent (Mandatory)
 
-Any GSD-T phase that produces or validates code **MUST spawn a QA teammate**. The QA agent's sole job is test generation, execution, and gap reporting. It never writes feature code.
+Any GSD-T phase that produces or validates code **MUST run QA**. The QA agent's sole job is test generation, execution, and gap reporting. It never writes feature code.
 
-**Commands that must spawn QA agent:**
-`partition`, `plan`, `execute`, `verify`, `complete-milestone`, `quick`, `debug`, `integrate`, `test-sync`, `wave`
+**QA method by command:**
+- `execute`, `integrate` → spawn QA via **Task subagent** (lightweight, no TeamCreate)
+- `test-sync`, `verify`, `complete-milestone` → perform contract testing and gap analysis **inline**
+- `quick`, `debug` → run the full test suite **inline** as part of the command's Test & Verify step
+- `wave` → each phase agent handles QA per the rules above
+- `partition`, `plan` → no QA spawn needed (no code produced yet)
 
-**Spawn instruction:**
+**Task subagent spawn instruction (execute/integrate):**
 ```
-Teammate "qa": Read commands/gsd-t-qa.md for your full instructions.
-  Phase context: {current phase}. Read .gsd-t/contracts/ for contract definitions.
-  Your job: generate contract tests, run all tests, report gaps.
-  You do NOT write feature code.
+Task subagent (general-purpose):
+"Run the full test suite and contract compliance tests.
+Read .gsd-t/contracts/ for contract definitions.
+Report: pass/fail counts and any coverage gaps."
 ```
 
-**QA agent failure blocks phase completion.** Lead cannot proceed until QA reports PASS or user explicitly overrides.
+**QA failure blocks phase completion.** Lead cannot proceed until QA reports PASS or user explicitly overrides.
 
 ## API Documentation Guard (Swagger/OpenAPI)
 
@@ -408,7 +416,7 @@ Successor mapping:
 | `populate` | `status` | |
 | `setup` | `status` | |
 
-Commands with no successor (standalone): `quick`, `debug`, `brainstorm`, `status`, `help`, `resume`, `prompt`, `log`, backlog commands.
+Commands with no successor (standalone): `quick`, `debug`, `brainstorm`, `status`, `help`, `resume`, `prompt`, `log`, `health`, `pause`, backlog commands.
 
 Skip the hint if auto-advancing (Level 3 mid-wave) — only show when the user needs to manually invoke the next step.