@tekyzinc/gsd-t 2.18.0 → 2.18.2

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.18.2] - 2026-02-16
+
+### Added
+- Gap Analysis Gate in `gsd-t-complete-milestone` — mandatory requirements verification before archiving
+- Self-correction loop: auto-fixes gaps, re-verifies, re-analyzes (up to 2 cycles), stops if unresolvable
+- Explicit Playwright E2E test execution in milestone test verification step
+
+## [2.18.1] - 2026-02-16
+
+### Added
+- Auto-Init Guard — GSD-T workflow commands automatically run `gsd-t-init` if any init files are missing, then continue with the original command
+- `gsd-t-init` copies `~/.claude/settings.local` → `.claude/settings.local.json` during project initialization
+- Exempt commands that skip auto-init: `gsd-t-init`, `gsd-t-init-scan-setup`, `gsd-t-help`, `gsd-t-version-update`, `gsd-t-version-update-all`, `gsd-t-prompt`, `gsd-t-brainstorm`
+
 ## [2.18.0] - 2026-02-16
 
 ### Added

package/commands/gsd-t-complete-milestone.md

@@ -17,6 +17,22 @@ If status is not VERIFIED:
 
 If `--force` flag provided, proceed with warning in archive.
 
+## Step 1.5: Gap Analysis Gate
+
+After verification passes, run a gap analysis against `docs/requirements.md` scoped to this milestone's deliverables:
+
+1. Identify which requirements this milestone was supposed to satisfy (from domain scopes, tasks, and milestone definition)
+2. Run `gsd-t-gap-analysis` against those requirements, comparing spec to actual code
+3. If **all gaps resolved** (100% Implemented) → proceed to Step 2
+4. If **gaps found** (Partial, Incorrect, or Not Implemented):
+   a. Auto-fix: execute remediation for each gap (prioritize Critical → High → Medium)
+   b. Run affected tests (unit + integration + Playwright E2E if configured)
+   c. Re-run `gsd-t-verify` to confirm fixes don't break anything
+   d. Re-run gap analysis to confirm gaps are resolved
+   e. If gaps remain after **2 fix cycles** → STOP and report unresolved gaps to user
+
+This is a **mandatory gate** — the milestone cannot be archived with known gaps against its requirements.
+
 ## Step 2: Gather Milestone Artifacts
 
 Collect all files related to this milestone:
@@ -163,10 +179,11 @@ Before creating the git tag, verify all documentation is up to date:
 
 Before creating the git tag, verify the milestone is truly complete:
 
-1. **Run the full test suite**: Execute ALL tests — unit, integration, and E2E if available
-2. **Verify all pass**: Every test must pass. If any fail, fix before tagging (up to 2 attempts)
-3. **Compare to baseline**: If a test baseline was recorded at milestone start, verify coverage has improved or at minimum not regressed
-4. **Log test results**: Include test pass/fail counts in the milestone summary (Step 4)
+1. **Run the full test suite**: Execute ALL tests — unit, integration, and E2E
+2. **Run Playwright E2E** (if configured): Detect `playwright.config.*` or Playwright in dependencies. If present, run the full Playwright suite. If specs are missing or stale, invoke `gsd-t-test-sync` first.
+3. **Verify all pass**: Every test must pass. If any fail, fix before tagging (up to 2 attempts)
+4. **Compare to baseline**: If a test baseline was recorded at milestone start, verify coverage has improved or at minimum not regressed
+5. **Log test results**: Include test pass/fail counts in the milestone summary (Step 4)
 
 ## Step 8: Create Git Tag
 

package/commands/gsd-t-init.md

@@ -18,6 +18,14 @@ Report current state and ask if user wants to reset or continue.
 Offer to migrate: "Found legacy GSD structure. Want me to migrate to GSD-T?"
 If yes, read `.gsd/` state and create equivalent `.gsd-t/` structure.
 
+## Step 1.5: Copy Local Settings
+
+If `~/.claude/settings.local` exists and `.claude/settings.local.json` does not exist in the project:
+1. Create the `.claude/` directory in the project root if it doesn't exist
+2. Copy `~/.claude/settings.local` → `.claude/settings.local.json`
+
+Skip silently if the source file doesn't exist or the target already exists.
+
 ## Step 2: Create Directory Structure
 
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tekyzinc/gsd-t",
-  "version": "2.18.0",
+  "version": "2.18.2",
   "description": "GSD-T: Contract-Driven Development for Claude Code — 41 slash commands with backlog management, impact analysis, test sync, and milestone archival",
   "author": "Tekyz, Inc.",
   "license": "MIT",

package/templates/CLAUDE-global.md

@@ -176,6 +176,21 @@ On session start, a version check hook outputs one of two messages. Show the res
 
 Only execute GSD-T workflow behavior when a `/gsd-t-*` command is invoked or when actively mid-phase (resumed via `/gsd-t-resume`). **Plain text messages — especially questions — should be answered conversationally.** Do not launch into workflow execution, file reading, or phase advancement from a question or comment. If the user wants work done, they will invoke a command.
 
+## Auto-Init Guard
+
+Before executing any GSD-T workflow command, check if **any** of these files are missing in the current project:
+- `.gsd-t/progress.md`, `.gsd-t/backlog.md`, `.gsd-t/backlog-settings.md`
+- `.gsd-t/contracts/`, `.gsd-t/domains/`
+- `.claude/settings.local.json` (if `~/.claude/settings.local` exists)
+- `CLAUDE.md`, `README.md`
+- `docs/requirements.md`, `docs/architecture.md`, `docs/workflows.md`, `docs/infrastructure.md`
+
+If any are missing:
+1. Run `gsd-t-init` automatically (it skips files that already exist)
+2. Then continue with the originally requested command
+
+**Exempt commands** (do not trigger auto-init): `gsd-t-init`, `gsd-t-init-scan-setup`, `gsd-t-help`, `gsd-t-version-update`, `gsd-t-version-update-all`, `gsd-t-prompt`, `gsd-t-brainstorm`.
+
 ## Prime Rule
 KEEP GOING. Only stop for:
 1. Unrecoverable errors after 2 fix attempts