@ktpartners/dgs-platform 3.4.1 → 3.4.2

package/CHANGELOG.md

@@ -8,6 +8,11 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [3.4.2] - 2026-06-25
+
+### Fixed
+- **Shipped workflows no longer hardcode the author's home path (quick-260625-0b3)** — `workflows/init-product.md` (8 sites) and `workflows/execute-plan.md` (1 site) invoked `node`/`cat` against the literal `/Users/adrian/.claude/deliver-great-systems/...`, so on any other user's machine those `dgs-tools` calls and the CLAUDE.md template read pointed at a nonexistent directory and failed. Replaced every occurrence with the portable `~/.claude/deliver-great-systems/...` form already used by all other workflows. No code or config files were affected — this was the only path leak in the distribution; `git grep /Users/adrian` over the shipped workflows now returns nothing.
+
 ## [3.4.1] - 2026-06-12
 
 ### Fixed

package/deliver-great-systems/workflows/execute-plan.md

@@ -512,7 +512,7 @@ ls -1 ${phase_dir}/*-SUMMARY.md 2>/dev/null | wc -l
 **Determine milestone status** (MANDATORY — do not guess from context):
 
 ```bash
-ROADMAP_INFO=$(node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs roadmap analyze)
+ROADMAP_INFO=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs roadmap analyze)
 ```
 
 Parse the `phases` array from the JSON result. Find the highest phase number in the current milestone. Compare against the current phase number to determine which route to take.

package/deliver-great-systems/workflows/init-product.md

@@ -27,7 +27,7 @@ What would you like to name this product? (e.g., "my-saas-app", "mobile-platform
 ## 2. Run Init Product
 
 ```bash
-RESULT=$(node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs repos init-product "$PRODUCT_NAME" --raw)
+RESULT=$(node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs repos init-product "$PRODUCT_NAME" --raw)
 ```
 
 Parse JSON response. Route to the appropriate handler based on the response shape.
@@ -94,7 +94,7 @@ Workflow discipline is always enabled by default — it adds a CLAUDE.md file th
 
 Read the CLAUDE.md template:
 ```bash
-CLAUDE_TEMPLATE=$(cat /Users/adrian/.claude/deliver-great-systems/templates/claude-md.md)
+CLAUDE_TEMPLATE=$(cat ~/.claude/deliver-great-systems/templates/claude-md.md)
 ```
 
 Check if `./CLAUDE.md` already exists in the project root (cwd):
@@ -121,7 +121,7 @@ Check if `./CLAUDE.md` already exists in the project root (cwd):
 
 Set config:
 ```bash
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set workflow.discipline true
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set workflow.discipline true
 ```
 
 Display: `Workflow discipline enabled — CLAUDE.md added.`
@@ -133,14 +133,14 @@ CLAUDE.md is always included in the init commit file list (b4 below).
 All other recommended defaults (`model_profile=balanced`, `commit_docs=true`, `workflow.research=true`, `workflow.plan_check=true`, `workflow.verifier=true`, `git.base_branch=main`) are already applied by `repos init-product` in step 2 — they live in `config.cjs`'s hardcoded defaults and are merged with any per-user overrides from `~/.dgs/defaults.json` (saved via `/dgs:settings save-as-defaults`). The three keys below are the only ones the underlying init does not pre-populate, so they are set explicitly here:
 
 ```bash
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set mode yolo
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set granularity standard
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set workflow.codereview true
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set mode yolo
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set granularity standard
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs config-set workflow.codereview true
 ```
 
 Commit the applied defaults:
 ```bash
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs commit "chore: apply recommended defaults" --files ${config_path}
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs commit "chore: apply recommended defaults" --files ${config_path}
 ```
 
 **b4. Commit initialized files:**
@@ -150,7 +150,7 @@ Extract the `scaffolded_files` array from the init response (`RESULT` captured i
 ```bash
 # AGENT-13: consume scaffolded_files from cmdReposInitProduct (per references/workflow-conventions.md)
 SCAFFOLDED=$(printf '%s' "$RESULT" | jq -r '.scaffolded_files[]?' | tr '\n' ' ')
-node /Users/adrian/.claude/deliver-great-systems/bin/dgs-tools.cjs commit "docs: initialize product ${product_name}" --files REPOS.md PROJECTS.md config.json .gitignore CLAUDE.md ${SCAFFOLDED}
+node ~/.claude/deliver-great-systems/bin/dgs-tools.cjs commit "docs: initialize product ${product_name}" --files REPOS.md PROJECTS.md config.json .gitignore CLAUDE.md ${SCAFFOLDED}
 ```
 
 CLAUDE.md is always included (workflow discipline is now always enabled by default — see b2). The `${SCAFFOLDED}` token is unquoted intentionally so word-splitting expands the multiple paths into separate `--files` arguments.

package/package.json

@@ -8,7 +8,7 @@
   "bugs": {
     "url": "https://github.com/KT-Partners-Ltd/dgs-platform-docs/issues"
   },
-  "version": "3.4.1",
+  "version": "3.4.2",
   "description": "Deliver Great Systems Platform — A meta-prompting, context engineering and spec-driven development system for Claude Code and Gemini by KT Partners.",
   "bin": {
     "dgs": "bin/install.js"