dev-harness-cli 1.0.5 → 1.2.0

package/templates/ci/github-actions.yml

@@ -74,5 +74,5 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - run: npm install -g @dev-harness/cli
-      - run: harness-dev validate --json
+      - run: npm install -g dev-harness-cli
+      - run: dev-harness validate --json

package/templates/ci/gitlab-ci.yml

@@ -54,6 +54,6 @@ gate:
   stage: gate
   image: node:lts
   script:
-    - npm install -g @dev-harness/cli
-    - harness-dev validate --json
+    - npm install -g dev-harness-cli
+    - dev-harness validate --json
   needs: [coverage]

package/templates/docs/agents/generator.md

@@ -10,4 +10,4 @@ You implement. You produce artifacts. You self-check.
 - In BUILD: implement ONE task at a time, then validate
 - In VERIFY: run the full test suite
 - In SIMPLIFY: adopt the Simplifier persona (see simplifier.md)
-- When done: call `harness-dev validate`
+- When done: call `dev-harness validate`

package/templates/docs/agents/planner.md

@@ -9,5 +9,5 @@ You design the approach. You write criteria. You set scope.
 - Set exclusions explicitly ("We will NOT build X")
 - Hand off to Generator when criteria are clear
 - In DEFINE: interview the user, write PRD in specs/*.md
-- In PLAN: decompose features into tasks in feature_list.json
+- In PLAN: decompose features into tasks in harness/features/feature-list.json
 - Review gate criteria with Evaluator before proceeding

package/templates/docs/agents/simplifier.md

@@ -10,4 +10,4 @@ You refactor. You clean. You never change behavior.
 - Break long functions (~40 line threshold)
 - Rename unclear variables
 - ⚠ All tests must still pass after your changes
-- Run `harness-dev validate` after each feature to confirm gate
+- Run `dev-harness validate` after each feature to confirm gate

package/templates/docs/phases/build.md

@@ -21,14 +21,14 @@ fresh context. Only when all features pass does the phase gate run.
 1. Read `progress.md`, `AGENTS.md`, `sprint-contract.md`.
 2. Pick next feature where `passes === false`.
 3. Implement the feature's tasks.
-4. Run `harness-dev validate --feature <name> --task <id>` per task.
+4. Run `dev-harness validate --feature <name> --task <id>` per task.
 5. On pass: mark feature `passes: true`, commit, append lesson to `progress.md`.
 6. On fail (≤ `maxRetries`): retry with fresh context (git reset if `--git-ops`).
 7. On fail (> `maxRetries`): escalate to human.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -38,4 +38,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase verify` (Generator → Evaluator).
+On gate pass: `dev-harness phase verify` (Generator → Evaluator).

package/templates/docs/phases/define.md

@@ -12,7 +12,7 @@ feature list.
 
 ## Entry
 
-- `harness-config.json` exists (created by `harness-dev init`)
+- `harness-config.json` exists (created by `dev-harness init`)
 - `AGENTS.md` present in project root
 
 ## Work
@@ -40,7 +40,7 @@ feature list.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -48,4 +48,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase plan` (Planner → continues as Planner for decomposition).
+On gate pass: `dev-harness phase plan` (Planner → continues as Planner for decomposition).

package/templates/docs/phases/plan.md

@@ -20,11 +20,11 @@ verifiable acceptance criteria. The Sprint Contract is negotiated here.
 2. Decompose into features → tasks in `feature_list.json`.
 3. Planner proposes `sprint-contract.md` (scope, criteria, exclusions).
 4. Evaluator reviews; iterate until `**Status:** Agreed`.
-5. Use `harness-dev contract propose` / `contract review --decision <agreed|needs-revision>`.
+5. Use `dev-harness contract propose` / `contract review --decision <agreed|needs-revision>`.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -33,4 +33,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase build` (Planner → Generator).
+On gate pass: `dev-harness phase build` (Planner → Generator).

package/templates/docs/phases/review.md

@@ -27,7 +27,7 @@ overall verdict: Accept / Revise / Block.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -39,4 +39,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase ship` (committee → release).
+On gate pass: `dev-harness phase ship` (committee → release).

package/templates/docs/phases/ship.md

@@ -17,13 +17,13 @@ The release must be reproducible from a clean checkout.
 
 1. Update `CHANGELOG.md` with version, date, summary.
 2. Bump version in `package.json` / equivalent manifest.
-3. Run full `harness-dev validate` — all gates must pass.
+3. Run full `dev-harness validate` — all gates must pass.
 4. Tag the release: `git tag -a v<x.y.z> -m "Release x.y.z"`.
 5. Open or merge the PR per project workflow.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -38,6 +38,6 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: pipeline complete. `harness-dev status` reports
+On gate pass: pipeline complete. `dev-harness status` reports
 `Pipeline complete after "ship"`. Increment `pipelineIteration` and loop back
 to DEFINE for the next sprint, or stop if the project is done.

package/templates/docs/phases/simplify.md

@@ -20,14 +20,14 @@ must not break the feature's acceptance criteria.
 1. Read `progress.md` and `AGENTS.md`.
 2. For each feature: review the implementation, propose deletions/renames.
 3. Apply simplifications.
-4. Re-run `harness-dev validate --feature <name>` — criteria must still pass.
+4. Re-run `dev-harness validate --feature <name>` — criteria must still pass.
 5. On pass: commit, append lesson.
 6. On fail (≤ `maxRetries`): revert and retry.
 7. On fail (> `maxRetries`): escalate.
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -37,4 +37,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase review` (Simplifier → multi-agent committee).
+On gate pass: `dev-harness phase review` (Simplifier → multi-agent committee).

package/templates/docs/phases/verify.md

@@ -26,7 +26,7 @@ feature's acceptance criteria from the sprint contract and scores it against
 
 ## Exit Gate
 
-Run `harness-dev validate` — checks:
+Run `dev-harness validate` — checks:
 
 - `config-exists`
 - `git-repo`
@@ -35,4 +35,4 @@ Run `harness-dev validate` — checks:
 
 ## Handoff
 
-On gate pass: `harness-dev phase simplify` (Evaluator → Simplifier).
+On gate pass: `dev-harness phase simplify` (Evaluator → Simplifier).

package/templates/harness-config.json

@@ -0,0 +1,42 @@
+{
+  "version": "1.0",
+  "stack": "{{stack}}",
+  "stackMeta": null,
+  "agentTool": null,
+  "mode": "copilot",
+  "currentPhase": null,
+  "paused": false,
+  "features": {
+    "remaining": 0,
+    "passing": 0,
+    "total": 0
+  },
+  "gates": {
+    "enabled": false,
+    "checks": ["all"]
+  },
+  "git": {
+    "autoCommit": false,
+    "autoTag": false,
+    "resetOnRetry": false,
+    "branch": null,
+    "clean": true,
+    "hasUpstream": false,
+    "lastCommitMessage": null
+  },
+  "phases": {
+    "enabled": ["define", "plan", "build", "verify", "review", "ship"]
+  },
+  "agents": {
+    "tone": {
+      "planner": "Analytical and precise. Define clear boundaries.",
+      "generator": "Focused and practical. Build what's specified, nothing more.",
+      "evaluator": "Skeptical and thorough. Accept only compelling evidence.",
+      "simplifier": "Relentless about clarity. Delete more than you add."
+    }
+  },
+  "maxRetries": 3,
+  "retryCount": 0,
+  "pipelineIteration": 0,
+  "gateHistory": []
+}

package/templates/init.ps1

@@ -94,4 +94,4 @@ switch ($Stack) {
 Write-Host "  ✓ Setup verified" -ForegroundColor Green
 
 # ── Start ────────────────────────────────────────────────────────────────────
-Write-Host "`nSetup complete. Run: harness-dev phase define" -ForegroundColor Cyan
+Write-Host "`nSetup complete. Run: dev-harness phase define" -ForegroundColor Cyan

package/templates/progress.md

@@ -0,0 +1,18 @@
+# Progress: {{stackLabel}}
+
+## Session State
+
+Current Phase: not started
+Current Feature: —
+Gate Status: pending
+Next Action: —
+Retry Count: 0/{{maxRetries}}
+
+## Lessons
+
+<!-- Use \`dev-harness learn "lesson here"\` to add lessons. -->
+
+## Checkpoints
+
+| Tag | Phase | Date | Notes |
+|-----|-------|------|-------|