@tekyzinc/gsd-t 2.19.1 → 2.20.1

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.20.1] - 2026-02-16
+
+### Added
+- **API Documentation Guard (Swagger/OpenAPI)**: Every API endpoint must be documented in Swagger/OpenAPI spec — no exceptions. Auto-detects framework and installs appropriate Swagger integration. Swagger URL must be published in CLAUDE.md, README.md, and docs/infrastructure.md
+- Pre-Commit Gate now checks for Swagger spec updates on any API endpoint change
+
+## [2.20.0] - 2026-02-16
+
+### Added
+- **Playwright Setup in Init**: `gsd-t-init` now installs Playwright, creates `playwright.config.ts`, and sets up E2E test directory for every project. Detects package manager (bun, npm, yarn, pnpm, pip) automatically
+- **Playwright Readiness Guard**: Before any testing command (execute, test-sync, verify, quick, wave, milestone, complete-milestone, debug), checks for `playwright.config.*` and auto-installs if missing. Playwright must always be ready — no deferring to "later"
+
 ## [2.19.1] - 2026-02-16
 
 ### Changed

package/commands/gsd-t-init.md

@@ -174,13 +174,35 @@ After initialization, verify all created documentation is consistent:
 
 ### Skip what's not affected — init creates docs, so most ripple is about consistency verification.
 
-## Step 7.6: Test Verification
+## Step 7.6: Playwright Setup (MANDATORY)
+
+Every GSD-T project must have Playwright ready for E2E testing. If `playwright.config.*` does not exist:
+
+1. **Detect package manager**: Check for `bun.lockb` (bun), `yarn.lock` (yarn), `pnpm-lock.yaml` (pnpm), `package-lock.json` or `package.json` (npm), `requirements.txt`/`pyproject.toml` (Python)
+2. **Install Playwright**:
+   - bun: `bun add -d @playwright/test && bunx playwright install chromium`
+   - npm: `npm install -D @playwright/test && npx playwright install chromium`
+   - yarn: `yarn add -D @playwright/test && yarn playwright install chromium`
+   - pnpm: `pnpm add -D @playwright/test && pnpm exec playwright install chromium`
+   - Python: `pip install playwright && playwright install chromium`
+   - No package manager detected: `npm init -y && npm install -D @playwright/test && npx playwright install chromium`
+3. **Create `playwright.config.ts`** (or `.js` if not using TypeScript) with sensible defaults:
+   - `testDir: './e2e'` (or `./tests/e2e`)
+   - `use: { baseURL: 'http://localhost:3000' }` (adjust based on project)
+   - Chromium only (keep it fast; user can add more browsers later)
+   - Screenshot on failure enabled
+4. **Create the E2E test directory** (`e2e/` or `tests/e2e/`) with a placeholder spec
+5. **Add test script** to `package.json` if it exists: `"test:e2e": "playwright test"`
+
+Skip silently if `playwright.config.*` already exists.
+
+## Step 7.7: Test Verification
 
 After initialization:
 
 1. **If existing code with tests**: Run the full test suite to establish a baseline. Document results in `.gsd-t/progress.md`
-2. **If existing code without tests**: Note the absence — recommend test setup as part of the first milestone
-3. **If greenfield**: No tests to run, but note that test infrastructure should be in Milestone 1
+2. **If existing code without tests**: Playwright is now set up (Step 7.6) — note unit test framework should be added as part of the first milestone
+3. **If greenfield**: Playwright is ready. Note that unit test infrastructure should be added in Milestone 1
 4. **Verify init outputs**: Confirm all created files exist and are non-empty
 
 ## Step 8: Report

package/package.json

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

@@ -191,6 +191,35 @@ If any are missing:
 
 **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`.
 
+## Playwright Readiness Guard
+
+Before any command that involves testing (`gsd-t-execute`, `gsd-t-test-sync`, `gsd-t-verify`, `gsd-t-quick`, `gsd-t-wave`, `gsd-t-milestone`, `gsd-t-complete-milestone`, `gsd-t-debug`), check if `playwright.config.*` exists in the project. If it does not:
+1. Detect the package manager and install Playwright (`@playwright/test` + chromium)
+2. Create a basic `playwright.config.ts` with sensible defaults
+3. Create the E2E test directory with a placeholder spec
+4. Then continue with the original command
+
+Playwright must always be ready before any testing occurs. Do not skip this check. Do not defer setup to "later."
+
+## API Documentation Guard (Swagger/OpenAPI)
+
+**Every API endpoint MUST be documented in a Swagger/OpenAPI spec. No exceptions.**
+
+When any GSD-T command creates or modifies an API endpoint:
+1. **If no Swagger/OpenAPI spec exists**: Set one up immediately
+   - Detect the framework (Express, Fastify, Hono, Django, FastAPI, etc.)
+   - Install the appropriate Swagger integration (e.g., `swagger-jsdoc` + `swagger-ui-express`, `@fastify/swagger`, FastAPI's built-in OpenAPI)
+   - Create the OpenAPI spec file or configure auto-generation from code
+   - Add a `/docs` or `/api-docs` route serving the Swagger UI
+2. **Update the spec**: Every new or changed endpoint must be reflected in the Swagger/OpenAPI spec — routes, request/response schemas, auth requirements, error responses
+3. **Publish the Swagger URL**: The Swagger/API docs URL MUST appear in:
+   - `CLAUDE.md` — under Documentation or Infrastructure section
+   - `README.md` — under API section or Getting Started
+   - `docs/infrastructure.md` — under API documentation
+4. **Verify**: After any API change, confirm the Swagger UI loads and reflects the current endpoints
+
+This applies during: `gsd-t-execute`, `gsd-t-quick`, `gsd-t-integrate`, `gsd-t-wave`, and any command that touches API code.
+
 ## Prime Rule
 KEEP GOING. Only stop for:
 1. Unrecoverable errors after 2 fix attempts
@@ -209,8 +238,10 @@ BEFORE EVERY COMMIT:
   │     Compare against "Expected branch" in project CLAUDE.md
   │     WRONG BRANCH → STOP. Do NOT commit. Switch to the correct branch first.
   │     No guard set → Proceed (but warn user to set one)
-  ├── Did I change an API endpoint or response shape?
+  ├── Did I create or change an API endpoint or response shape?
   │     YES → Update .gsd-t/contracts/api-contract.md
+  │     YES → Update Swagger/OpenAPI spec (see API Documentation Guard below)
+  │     YES → Verify Swagger URL is in CLAUDE.md and README.md
   ├── Did I change the database schema?
   │     YES → Update .gsd-t/contracts/schema-contract.md AND docs/schema.md
   ├── Did I add/change a UI component interface?