@tekyzinc/gsd-t 5.8.10 → 5.10.10

package/templates/CLAUDE-project.md

@@ -1,127 +1,70 @@
-# GSD-T Framework (@tekyzinc/gsd-t)
+# {PROJECT_NAME}
 
-Prime Directives, core guards, and workflow rules live in `~/.claude/CLAUDE.md`. This file covers what's specific to this repo.
+{ONE_LINE_WHAT_THIS_IS}
 
-## Overview
+> Everything general lives in `~/.claude/CLAUDE.md` and applies here. This file
+> holds only what is true of this project and nothing else.
 
-Contract-driven development methodology for Claude Code. npm package providing slash commands, a CLI installer, templates, and stack rules for reliable parallelizable AI-assisted development.
+## Rules that can never be broken
 
-## Autonomy Level
+<!--
+  Ticked by David from what the project already says. Nothing invented, nothing
+  copied from the global file. If a rule is enforced by a hook or a gate, say so
+  — the reader should know a machine is watching.
 
-> Overrides global: pins the default from `~/.claude/CLAUDE.md` § Autonomy Levels.
+  Leave this section out entirely if none were found, and say why.
+-->
+{RULES}
 
-**Level 3 — Full Auto**. Only pause for blockers, destructive actions, or project completion.
+## Where the repo misleads you
 
-## Tech Stack
+<!--
+  Only where reading the code gives a confident WRONG answer — two version
+  fields disagreeing, a legacy path that still looks live, a config that is not
+  the one in use. Leave out if none.
+-->
+{MISLEADS}
 
-- **Language**: JavaScript (Node.js >= 16), zero external runtime deps for the installer
-- **Distribution**: npm package `@tekyzinc/gsd-t`
-- **CLI**: `bin/gsd-t.js` (install, update, init, status, uninstall, doctor, graph, headless, …)
-- **Testing**: `npm test` (Node built-in test runner) + manual CLI testing
+## Files that are riskier than they look
 
-## Project Structure
+<!--
+  Determined by reading, never asked. A file fixed the same way five times is a
+  rule nobody wrote down. Say what breaks, not just which file. Leave out if none.
+-->
+{DANGER_MAP}
 
-```
-bin/                     — CLI entry (gsd-t.js) + orchestrators (orchestrator.js, design-orchestrator.js)
-                           + support modules (gsd-t-context-brief.cjs, cli-preflight.cjs, gsd-t-verify-gate.cjs, gsd-t-model-tier-policy.cjs, …)
-commands/                — slash commands for Claude Code (GSD-T workflow + utility)
-templates/               — document + prompt + stack templates
-  CLAUDE-{global,project}.md, requirements.md, architecture.md, workflows.md,
-  infrastructure.md, progress.md, backlog.md, backlog-settings.md, design-contract.md
-  prompts/               — validation subagent protocols (qa, red-team, design-verify)
-  stacks/                — Stack Rules Engine templates (injected at spawn time)
-scripts/                 — runtime scripts (design review, context meter hook, event writer)
-examples/                — example project structure + settings
-docs/methodology.md      — GSD → GSD-T evolution and concepts
-package.json, README.md, GSD-T-README.md, CHANGELOG.md
-```
+## Where this differs from the global rules
 
-Exact command list: `ls commands/`. Exact stack rule set: `ls templates/stacks/`. Don't hand-maintain counts in docs.
+<!-- ONLY genuine differences. An empty table means there are none — leave it out. -->
 
-## Meta-Project Notes
+| Global default | Here | Why |
+|---|---|---|
+{OVERRIDES}
 
-- The "source" is the `.md` files in `commands/` + `templates/` and the JS in `bin/` + `scripts/`. There is no `src/`.
-- Changes to command files change the methodology itself — treat them as code; verify by running the workflow.
-- The `.gsd-t/` state dir coexists with the commands that *define* `.gsd-t/` — intentional.
-- `bin/gsd-t.js` is the primary testable surface; command files are validated by use.
+## Stack and commands
 
-## Conventions
+{STACK}
 
-**CLI** — ANSI colors via escape codes, zero external deps, sync file APIs, version tracked in `package.json` and `~/.claude/.gsd-t-version`.
+| | |
+|---|---|
+| Build | `{BUILD_CMD}` |
+| Test | `{TEST_CMD}` |
+| Branch | `{BRANCH}` |
 
-**Command files** — pure markdown, no frontmatter, accept `$ARGUMENTS`, step-numbered, thin Workflow invokers (`Workflow({scriptPath, args})`). Include a Document Ripple section listing files the underlying Workflow expects domain workers to update. Validation protocol bodies stay in `templates/prompts/*-subagent.md`; Workflow scripts load them via `_lib.loadProtocol(name)`. Don't inline the protocol.
+## Where things are written down
 
-**Templates** — `{Project Name}`, `{Date}`, `{description}` replacement tokens; tables for structured data.
+| | |
+|---|---|
+| State and decisions | `.gsd-t/progress.md` |
+| Interfaces between parts | `.gsd-t/contracts/` |
+| How to reach environments | `docs/infrastructure.md` |
 
-**Directory structure** — `.gsd-t/contracts/` (domain interfaces), `.gsd-t/domains/{name}/` (scope/tasks/constraints), `.gsd-t/milestones/` (archives), `.gsd-t/scan/` (analysis outputs).
+<!--
+  Written {GENERATED_DATE} from this project's own history.
 
-**Publishing** — after `npm publish`, ALWAYS run `/gsd-t-version-update-all` to propagate to registered projects.
+  Nothing above should carry a number that changes on its own — no version, no
+  line count, no "currently in progress". Those belong in progress.md, and a
+  file that repeats them is wrong within a week.
 
-## GSD-T Workflows (M61 — v4.0.10+)
-
-Phase orchestration lives in `templates/workflows/`. Each command file (`commands/gsd-t-*.md`) is a thin invoker that calls `Workflow({scriptPath, args})`. Canonical scripts:
-
-- `gsd-t-execute.workflow.js` — preflight → brief → file-disjointness → parallel(domain workers) → integrate → verify-gate
-- `gsd-t-verify.workflow.js` — orthogonal triad with M57 CI-parity + M58 test-data purge as FAIL-blocking gates
-- `gsd-t-wave.workflow.js`, `-integrate`, `-debug`, `-quick`, `-phase` (generic upper-stage runner)
-
-Shared helpers: `templates/workflows/_lib.js`. Each helper prefers project-local `bin/<tool>.cjs` and falls back to global `gsd-t` PATH binary.
-
-The brains stay in `bin/`: `gsd-t-file-disjointness.cjs`, `gsd-t-task-graph.cjs`, `gsd-t-context-brief.cjs`, `cli-preflight.cjs`, `gsd-t-verify-gate.cjs`, `gsd-t-verify-gate-judge.cjs`, `gsd-t-build-coverage.cjs`, `gsd-t-ci-parity.cjs`, `gsd-t-test-data-ledger.cjs`, `journey-coverage.cjs`. Workflows invoke them via `lib.*` helpers.
-
-## Validation Protocols (KEPT — methodology layer)
-
-Three validation protocol bodies stay at `templates/prompts/`:
-- `qa-subagent.md` — test mechanics + shallow-test detection + contract compliance
-- `red-team-subagent.md` — adversarial / security / boundaries; verdict `FAIL` / `GRUDGING-PASS`
-- `design-verify-subagent.md` — visual MATCH/DEVIATION against the design contract
-
-These are invoked as Workflow `agent()` stages with schema-validated output. The methodology body is unchanged; only the invocation context (Workflow stage vs. Task subagent) updated. Per `.gsd-t/contracts/orthogonal-validation-contract.md` v1.0.0 STABLE.
-
-
-# Destructive Action Guard (MANDATORY)
-
-**NEVER perform destructive or structural changes without explicit user approval.** This applies at ALL autonomy levels.
-
-Before any of these actions, STOP and ask the user:
-- DROP TABLE, DROP COLUMN, DROP INDEX, TRUNCATE, DELETE without WHERE
-- Renaming or removing database tables or columns
-- Schema migrations that lose data or break existing queries
-- Replacing an existing architecture pattern (e.g., normalized → denormalized)
-- Removing or replacing existing files/modules that contain working functionality
-- Changing ORM models in ways that conflict with the existing database schema
-- Removing API endpoints or changing response shapes that existing clients depend on
-- Any change that would require other parts of the system to be rewritten
-
-**Rule: "Adapt new code to existing structures, not the other way around."**
-
-## Pre-Commit Gate (project-specific additions)
-
-The global gate applies first (see `~/.claude/CLAUDE.md`). Additionally for this repo:
-
-- **Command file interface/behavior changed** → update `GSD-T-README.md` + `README.md` commands table + `templates/CLAUDE-global.md` + `commands/gsd-t-help.md`.
-- **Command added/removed** → update all 4 files above, bump `package.json`, update any command-counting logic in `bin/gsd-t.js`.
-- **New command invokes a Workflow** → verify `scriptPath` resolves to `templates/workflows/<name>.workflow.js` and `args` shape matches the script's `meta.phases`.
-- **CLI installer changed** → smoke test `install`, `update`, `status`, `doctor`, `init`, `uninstall`.
-- **Template changed** → verify `gsd-t-init` still produces correct output.
-- **Wave flow changed (phases added/removed/reordered)** → update `gsd-t-wave.md`, `GSD-T-README.md` wave diagram, `README.md` workflow section.
-- **Contract or domain boundary changed** → update `.gsd-t/contracts/` and owning `scope.md`.
-
-## Don't
-
-- NEVER add external npm runtime dependencies to the installer — zero-dep invariant.
-- NEVER rename a command without updating all 4 reference files above.
-- NEVER modify wave phase sequence without updating wave, README, GSD-T-README in the same commit.
-- NEVER let installer's command count diverge from `commands/` directory reality.
-- NEVER inline validation-subagent protocol bodies into Workflow scripts — `_lib.loadProtocol("qa"|"red-team"|"design-verify")` reads the methodology body from `templates/prompts/`.
-
-## Recovery After Interruption
-
-1. Read `.gsd-t/progress.md`
-2. Read `README.md` for what the package delivers
-3. Check `commands/` and `package.json` for current state
-4. Continue from current task; don't restart the phase
-
-## Current Status
-
-See `.gsd-t/progress.md`.
+  Regenerate with /gsd-t-setup.
+-->