@tekyzinc/gsd-t 2.31.14 → 2.31.16

package/commands/gsd-t-init.md

@@ -90,13 +90,27 @@ Read the project's `CLAUDE.md` (if it exists) to auto-populate backlog settings:
 
 ## Step 5: Initialize Progress File
 
+### Version Detection
+
+Before creating the progress file, determine the starting version:
+
+1. **Check for an existing version** in the project's manifest file (in this priority order):
+   - `package.json` → `version` field
+   - `pyproject.toml` → `[project] version` or `[tool.poetry] version`
+   - `Cargo.toml` → `[package] version`
+   - `setup.py` → `version=` argument
+   - `build.gradle` / `build.gradle.kts` → `version = `
+   - `.version` file → contents as-is
+2. **If a version is found**: Use it as the starting GSD-T version (the project already has its own versioning history).
+3. **If no version is found**: Use `0.1.00` — the standard GSD-T starting point for a brand-new project with no prior releases. The first `gsd-t-complete-milestone` will reset the patch to `0.1.10` (or bump minor/major per milestone scope).
+
 Create `.gsd-t/progress.md`:
 
 ```markdown
 # GSD-T Progress
 
 ## Project: {name from CLAUDE.md or $ARGUMENTS}
-## Version: 0.1.0
+## Version: {detected version, or 0.1.00}
 ## Status: INITIALIZED
 ## Date: {today}
 

package/package.json

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

package/templates/CLAUDE-global.md

@@ -118,7 +118,9 @@ GSD-T tracks project version in `.gsd-t/progress.md` using semantic versioning:
 
 **Patch convention**: Patch numbers are always 2 digits (≥10). When resetting after a minor or major bump, start at **10** (not 0). This keeps patches always 2 characters without leading zeros, so semver stays valid.
 
-- Version is set during `gsd-t-init` (starts at `0.1.10`)
+- Version is set during `gsd-t-init`:
+  - **New project** (no existing manifest version): starts at `0.1.00` — first `complete-milestone` resets patch to `0.1.10`
+  - **Existing repo** (has `package.json`, `pyproject.toml`, `Cargo.toml`, etc. with a version): use that version as the starting point
 - Version is bumped during `gsd-t-complete-milestone` based on milestone scope
 - Version is reflected in: `progress.md`, `README.md`, package manifest (if any), and git tags (`v{version}`)
 
@@ -456,6 +458,33 @@ constants:  UPPER_SNAKE_CASE  (MAX_RETRIES)
 private:    _underscore       (_internal_method)
 ```
 
+## Markdown Tables
+
+Emoji display as 2 characters wide in terminal/monospace but count as 1 in string length. This causes misaligned columns. **Always add one extra space after emoji in table cells** to compensate:
+
+```
+WRONG — misaligned in terminal:
+| Channel  | Support |
+|----------|---------|
+| Discord  | ✅ |
+| LINE     | ❌ |
+
+RIGHT — one extra space after emoji:
+| Channel  | Support |
+|----------|---------|
+| Discord  | ✅  |
+| LINE     | ❌  |
+```
+
+This extra space is invisible in rendered HTML (GitHub, VS Code preview) but restores alignment in terminal views. Apply to all GSD-T-generated docs that use emoji in tables.
+
+Also pad all cell values in a column to the width of the widest value:
+```
+| iMessage (BlueBubbles) | ✅  |
+| Discord                | ✅  |
+| QQ                     | ❌  |
+```
+
 
 # Recovery After Interruption