@tekyzinc/gsd-t 2.20.2 → 2.20.4

package/CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.20.4] - 2026-02-16
+
+### Changed
+- **Scan always uses team mode**: `gsd-t-scan` and `gsd-t-init-scan-setup` now spawn a team by default. Solo mode only for trivially small codebases (< 5 files) or when teams are explicitly disabled
+
+## [2.20.3] - 2026-02-16
+
+### Added
+- **Playwright Cleanup**: After Playwright tests finish, kill any app/server processes that were started for the tests. Prevents orphaned dev servers from lingering after test runs
+
 ## [2.20.2] - 2026-02-16
 
 ### Added

package/commands/gsd-t-init-scan-setup.md

@@ -58,7 +58,7 @@ Execute the full scan workflow (same as `/user:gsd-t-scan`):
 3. Cross-populate findings into living documents (docs/architecture.md, docs/workflows.md, docs/infrastructure.md, docs/requirements.md)
 4. Update README.md with discovered tech stack and setup info
 
-Use team mode if agent teams are enabled. Otherwise run solo.
+Always use team mode for the scan unless the codebase is trivially small (< 5 files) or teams are explicitly disabled.
 
 **If `.gsd-t/techdebt.md` already exists**: Append new findings, don't overwrite.
 

package/commands/gsd-t-scan.md

@@ -13,10 +13,7 @@ Read:
 
 ## Step 2: Full Codebase Scan
 
-Choose solo or team mode:
-
-### Team Mode (recommended for medium-to-large codebases)
-If agent teams are enabled, spawn a team — each dimension is fully independent:
+**Always use Team Mode** unless the codebase is trivially small (< 5 files) or agent teams are explicitly disabled. Each dimension is fully independent — parallel scanning is faster and produces better results.
 
 ```
 Create an agent team to scan this codebase:
@@ -41,7 +38,7 @@ Each teammate: write your findings to your assigned file.
 Lead: synthesize all findings into .gsd-t/techdebt.md when complete.
 ```
 
-### Solo Mode (small codebases or teams not enabled)
+### Solo Mode (fallback — only if < 5 files or teams disabled)
 Work through each dimension sequentially:
 
 Systematically analyze the entire codebase across these dimensions:

package/package.json

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

@@ -201,6 +201,15 @@ Before any command that involves testing (`gsd-t-execute`, `gsd-t-test-sync`, `g
 
 Playwright must always be ready before any testing occurs. Do not skip this check. Do not defer setup to "later."
 
+### Playwright Cleanup
+
+After Playwright tests finish (pass or fail), **kill any app/server processes that were started for the tests**. Playwright often launches a dev server (via `webServer` config or manually). These processes must not be left running:
+1. Check for any dev server processes spawned during the test run
+2. Kill them (e.g., `npx kill-port`, or terminate the process directly)
+3. Verify the port is free before proceeding
+
+This applies everywhere Playwright tests are executed: execute, test-sync, verify, quick, wave, debug, complete-milestone, and integrate.
+
 ## API Documentation Guard (Swagger/OpenAPI)
 
 **Every API endpoint MUST be documented in a Swagger/OpenAPI spec. No exceptions.**