@tekyzinc/gsd-t 2.11.4 → 2.11.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,17 @@
2
2
 
3
3
  All notable changes to GSD-T are documented here. Updated with each release.
4
4
 
5
+ ## [2.11.6] - 2026-02-12
6
+
7
+ ### Changed
8
+ - Update notice now shown at both beginning and end of Claude's first response
9
+
10
+ ## [2.11.5] - 2026-02-12
11
+
12
+ ### Added
13
+ - SessionStart hook script (`~/.claude/scripts/gsd-t-update-check.js`) for automatic update notifications in Claude Code sessions
14
+ - "Update Notices" instruction in global CLAUDE.md template — Claude relays update notices to the user on first response
15
+
5
16
  ## [2.11.4] - 2026-02-12
6
17
 
7
18
  ### Fixed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@tekyzinc/gsd-t",
3
- "version": "2.11.4",
3
+ "version": "2.11.6",
4
4
  "description": "GSD-T: Contract-Driven Development for Claude Code — 35 slash commands with backlog management, impact analysis, test sync, and milestone archival",
5
5
  "author": "Tekyz, Inc.",
6
6
  "license": "MIT",
@@ -149,6 +149,15 @@ Even in development, the user may have:
149
149
 
150
150
  # Autonomous Execution Rules
151
151
 
152
+ ## Update Notices
153
+
154
+ If a `[GSD-T UPDATE]` message appears in session startup context, show it to the user at the **beginning AND end** of your first response. Format it as:
155
+
156
+ ```
157
+ ⬆️ GSD-T update available: {installed} → {latest}
158
+ Run: npm update -g @tekyzinc/gsd-t && gsd-t update-all
159
+ ```
160
+
152
161
  ## Conversation vs. Work
153
162
 
154
163
  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.