@pieerry/harness-kit 3.1.1 → 3.1.2

package/.claude/scripts/pipeline.py

@@ -162,6 +162,16 @@ def render_line():
     next_cmd = STAGE_TO_COMMAND.get(current, "?")
 
     shape = "+".join(pipeline)
+
+    # No work started yet: show full menu instead of locking to next stage
+    no_work_started = (
+        not fid
+        and not prev
+        and all(stages.get(s) == "pending" for s in pipeline)
+    )
+    if no_work_started:
+        return f"{name} [{shape}] · /product-manager:run · /sse:run · /pipeline:continue · /pipeline:reset"
+
     if prev:
         return f"{name} [{shape}] · {prev} approved · {current} {cur_state} · next {next_cmd}"
     return f"{name} [{shape}] · {current} {cur_state} · next {next_cmd}"

package/.claude/settings.local.json

@@ -71,7 +71,8 @@
       "Bash(git -C /Users/pierryborges/Development/harness-kit diff --stat)",
       "Bash(rm -rf /tmp/hk-fresh /tmp/hk-existing)",
       "Bash(npm whoami *)",
-      "Bash(npm publish *)"
+      "Bash(npm publish *)",
+      "Bash(git tag *)"
     ]
   }
 }

package/README.md

@@ -5,7 +5,7 @@
 Claude Code harness for product + engineering delivery.
 From idea to merged PR, one pipeline.
 
-[![Version](https://img.shields.io/badge/version-3.1.1-blue.svg)](VERSION)
+[![Version](https://img.shields.io/badge/version-3.1.2-blue.svg)](VERSION)
 [![Claude Code](https://img.shields.io/badge/Claude%20Code-plugin-8b5cf6.svg)](https://claude.ai/code)
 [![Plugins](https://img.shields.io/badge/plugins-2-success.svg)](#layout)
 [![Pipeline](https://img.shields.io/badge/stages-6-informational.svg)](#usage)
@@ -15,7 +15,7 @@ From idea to merged PR, one pipeline.
 
 ![harness-kit demo](demo/preview.gif)
 
-<sub>100s walkthrough · install → 6 commands → PR → resume. Each command scene shows the active **guide · ref · sensor · eval**. Dedicated scenes for the dynamic status bar and `/pipeline:continue` resume flow.</sub>
+<sub>110s walkthrough · install → 6 commands → final summary → resume. Each command scene shows the active **guide · ref · sensor · eval**. Dedicated scenes for the dynamic status bar, the named-everything final summary, and `/pipeline:continue` resume flow.</sub>
 
 </div>
 
@@ -46,7 +46,9 @@ npm i -g @pieerry/harness-kit
 hk install
 ```
 
-`hk install` writes plugins into `.claude/plugins/`, drops the status-line hook in `.claude/hooks/`, generates `.claude/settings.json`, and scaffolds `.claude/conventions/` for your project overrides. Run it from the target repo (or pass an explicit `[target]`). Restart Claude Code after.
+`hk install` writes plugins into `.claude/plugins/`, drops the status-line + pipeline-tracking hooks in `.claude/hooks/`, copies the pipeline state manager to `.claude/scripts/`, registers slash commands under `.claude/commands/`, generates `.claude/settings.json`, and scaffolds `.claude/conventions/` for your project overrides. Run it from the target repo (or pass an explicit `[target]`). Restart Claude Code after.
+
+Reinstalling on top of an existing setup backs up the previous `settings.json` to `.claude/settings.json.bak.{timestamp}` before overwriting, so manual customizations are recoverable.
 
 CLI subcommands:
 
@@ -67,11 +69,20 @@ bash ~/.harness-kit/setup/install.sh
 
 ### Update
 
+For npm installs:
+
 ```bash
+npm i -g @pieerry/harness-kit@latest
 hk update
 ```
 
-Pulls latest source and reinstalls. Idempotent. Version is read from the package `VERSION` and recorded in your target at `.claude/.hk-version`.
+For git-clone installs:
+
+```bash
+hk update
+```
+
+`hk update` pulls latest source (git installs only) and reinstalls. Idempotent. Version is read from the package `VERSION` and recorded in your target at `.claude/.hk-version`. npm users must bump the package first — `hk update` alone won't reach the registry.
 
 ### Usage
 
@@ -107,8 +118,19 @@ $ /product-manager:run
 > squad? billing
 > problem? invoice generation fails for multi-currency customers
 > ...
-PRD saved at outputs/prd/2026-05-12-billing-multi-currency.md. Score: 8.6/10.
-PRP saved at outputs/prp/2026-05-12-billing-multi-currency.md. Score: 8.4/10.
+PRD saved at outputs/prd/2026-05-12-billing-multi-currency.md.
+  sensors: prd-structure ok, prd-acceptance-criteria ok
+  eval:    prd-quality 8.6/10, prd-readiness 8.9/10
+  guides:  prd-guidelines.md, writing-style.md, templates/prd.md
+  refs:    business-info.md, squads/billing/context.md
+  next:    /product-manager:prp
+
+PRP saved at outputs/prp/2026-05-12-billing-multi-currency.md.
+  sensors: prp-structure ok, prp-context-quality ok, prp-links ok
+  eval:    prp-quality 8.4/10, prp-context-readiness 9.0/10
+  guides:  prp-guidelines.md, templates/prp.md
+  refs:    prd/2026-05-12-billing-multi-currency.md
+  next:    /sse:plan (ready for handoff)
 ```
 
 Engineering session in the target service repo:
@@ -117,12 +139,34 @@ Engineering session in the target service repo:
 $ /sse:run
 > source PRP? outputs/prp/2026-05-12-billing-multi-currency.md
 > area? backend
-Plan saved at outputs/plan/2026-05-12-billing-multi-currency.md. Score: 8.3/10.
-Dev complete. 5 files changed, 3 commits.
-Tests: 24 passed, 0 failed.
+Plan saved at outputs/plan/2026-05-12-billing-multi-currency.md.
+  sensors: plan-structure ok (problem, files, gates, scope)
+  eval:    plan-quality 8.3/10
+  guides:  pipeline.md, coding-style.md, skills/backend/SKILL.md
+  refs:    prp/2026-05-12-billing-multi-currency.md, conventions/backend.md
+  next:    /sse:dev
+
+Dev complete. branch feat/PROJ-123-multi-currency.
+  files changed: 5
+  commits: 3 (a1b2c3d, d4e5f6g, h7i8j9k)
+  sensors: code-conventions ok, test-coverage ok
+  guides:  coding-style.md, commit-style.md, skills/backend/SKILL.md
+  next:    /sse:test
+
+Tests passed.
+  command:  ./mvnw test
+  passed:   24, failed: 0
+  duration: 12.4s
+  next:     /sse:pr
+
 PR opened: https://github.com/your-org/billing-service/pull/567
+  title:  feat(PROJ-123): timezone-aware deadline check
+  draft:  yes
+  guides: pr-template.md, commit-style.md
 ```
 
+Every reply names the actual sensors that ran, evals with scores, and guides loaded — no generic "ok" lines. The `/sse:run` and `/product-manager:run` summaries aggregate the same shape across phases.
+
 Token usage is logged per phase to a shared JSON across both plugins. See the [product-manager README](.claude/plugins/product-manager/README.md#token-accounting) for the schema and query examples.
 
 ### Samples
@@ -197,7 +241,7 @@ Every stage in the pipeline runs the same loop. Same four ingredients, every tim
 
 Sensors are pass/fail (deterministic, fast). Evals are scored (LLM-judged, retried until ≥ threshold or max attempts). Approval markers (`<!-- approved: -->`) gate the next stage.
 
-The 85s demo above shows every command running with these artifacts loading live on the right panel.
+The 110s demo above shows every command running with these artifacts loading live on the right panel — plus the final summary scene that names every sensor, eval, and guide per phase.
 
 ---
 

package/VERSION

@@ -1 +1 @@
-3.1.1
+3.1.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pieerry/harness-kit",
-  "version": "3.1.1",
+  "version": "3.1.2",
   "description": "Claude Code harness for product + engineering delivery. From idea to merged PR, one pipeline.",
   "author": "Space Metrics AI",
   "license": "MIT",