@tekyzinc/gsd-t 2.16.4 → 2.16.5

package/CHANGELOG.md

@@ -2,6 +2,15 @@
 
 All notable changes to GSD-T are documented here. Updated with each release.
 
+## [2.16.5] - 2026-02-16
+
+### Added
+- `gsd-t-populate` now reconstructs Decision Log from git history — parses all commits, generates timestamped entries, merges with existing log
+- Pre-Commit Gate explicitly lists all 30 file-modifying commands that must log to progress.md
+
+### Changed
+- Rebuilt GSD-T project Decision Log with full `YYYY-MM-DD HH:MM` timestamps from 54 git commits
+
 ## [2.16.4] - 2026-02-16
 
 ### Changed

package/commands/gsd-t-populate.md

@@ -35,6 +35,36 @@ Scan this codebase and populate the GSD-T documentation. Analyze the actual code
 - Set status: VERIFIED
 - Log today session: "GSD-T documentation populated from existing codebase"
 
+## Reconstruct Decision Log from Git History
+
+Rebuild the progress.md Decision Log from the project's commit history:
+
+1. **Read existing Decision Log entries** — note what's already recorded to avoid duplicates
+2. **Run `git log --reverse --format="%ai|%s"`** — get all commits with timestamps and messages
+3. **Filter meaningful commits** — skip merge commits, trivial whitespace/formatting-only commits
+4. **Generate entries** in the standard format:
+   ```
+   - YYYY-MM-DD HH:MM: {commit summary} — {brief context from commit message}
+   ```
+5. **Group by date** — if multiple commits on the same day cover the same logical change, combine them into one entry rather than listing each commit separately
+6. **Merge with existing entries** — insert reconstructed entries chronologically, keeping any hand-written entries that already exist (they may have richer context than commit messages)
+7. **Mark the reconstruction** — add a note at the top of the reconstructed section:
+   ```
+   (Entries before {date} reconstructed from git history)
+   ```
+
+### What to include:
+- Feature additions, bug fixes, refactors
+- Config/dependency changes
+- Documentation updates
+- Version bumps and releases
+- Any commit that modified documents, scripts, or code
+
+### What to exclude:
+- Pure merge commits with no additional context
+- Commits that only change whitespace or formatting
+- Duplicate entries already in the Decision Log
+
 ---
 
 ## Document Ripple

package/package.json

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

package/templates/CLAUDE-global.md

@@ -205,11 +205,16 @@ BEFORE EVERY COMMIT:
   │     YES → Update docs/requirements.md (mark complete or revise)
   ├── Did I add/change/remove a component or change data flow?
   │     YES → Update docs/architecture.md
-  ├── Did I complete a task or make a meaningful change?
+  ├── Did I modify any document, script, or code file?
   │     YES → Add timestamped entry to .gsd-t/progress.md Decision Log
   │     Format: `- YYYY-MM-DD HH:MM: {what was done} — {brief context or result}`
+  │     This includes ALL file-modifying activities:
+  │       project, feature, scan, gap-analysis, milestone, partition, discuss,
+  │       plan, impact, execute, test-sync, integrate, verify, complete-milestone,
+  │       wave, quick, debug, promote-debt, populate, setup, init, init-scan-setup,
+  │       backlog-add/edit/move/remove/promote/settings, and any manual code changes
   ├── Did I make an architectural or design decision?
-  │     YES → Add to .gsd-t/progress.md Decision Log (with decision rationale)
+  │     YES → Also include decision rationale in the progress.md entry
   ├── Did I discover or fix tech debt?
   │     YES → Update .gsd-t/techdebt.md
   ├── Did I establish a pattern future work should follow?