dev-harness-cli 1.1.0 → 2.1.0

package/cli/lib/help.mjs

@@ -2,7 +2,7 @@
  * Help text builder — centralized to keep all formatting in one place.
  */
 
-const USAGE = `Usage: harness-dev <command> [options]
+const USAGE = `Usage: dev-harness <command> [options]
 
 Pipeline commands:
   init                  Scaffold full harness in current directory
@@ -53,14 +53,14 @@ Exit codes:
   2  Usage error (bad arguments)
   3  Internal error`;
 
-const VERSION = '1.1.0';
+const VERSION = '1.2.0';
 
 // Help text for JSON output
 function buildJsonHelp() {
   return {
     help: true,
     version: VERSION,
-    usage: 'harness-dev <command> [options]',
+    usage: 'dev-harness <command> [options]',
     commands: {
       init: 'Scaffold full harness in current directory',
       status: 'Show current phase + gate state + detected stack',
@@ -111,12 +111,12 @@ export function versionText(json = false) {
   if (json) {
     return JSON.stringify({ version: VERSION });
   }
-  return `harness-dev v${VERSION}`;
+  return `dev-harness v${VERSION}`;
 }
 
-// Per-command help text (for `harness-dev <command> --help`).
+// Per-command help text (for `dev-harness <command> --help`).
 const COMMAND_HELP = {
-  init: `Usage: harness-dev init [--stack <name>] [--target <dir>] [--force] [--no-git] [--json]
+  init: `Usage: dev-harness init [--stack <name>] [--target <dir>] [--force] [--no-git] [--json]
 
 Scaffold a full harness in the target directory:
   - Detects stack (or use --stack)
@@ -131,7 +131,7 @@ Flags:
   --no-git          Skip git init
   --json            JSON output`,
 
-  status: `Usage: harness-dev status [--target <dir>] [--json]
+  status: `Usage: dev-harness status [--target <dir>] [--json]
 
 Show current phase, gate state, detected stack, recent lessons, and next action.
 
@@ -139,7 +139,7 @@ Flags:
   --target <dir>    Project directory (default: cwd)
   --json            JSON output`,
 
-  phase: `Usage: harness-dev phase <name> [--target <dir>] [--git-ops] [--json]
+  phase: `Usage: dev-harness phase <name> [--target <dir>] [--git-ops] [--json]
 
 Invoke a phase. Valid phases: define, plan, build, verify, simplify, review, ship.
 
@@ -148,7 +148,7 @@ Flags:
   --git-ops         Execute git reset --hard + clean on retry (fresh context)
   --json            JSON output`,
 
-  validate: `Usage: harness-dev validate [--phase <name>] [--feature <id> --task <id>] [--target <dir>] [--json]
+  validate: `Usage: dev-harness validate [--phase <name>] [--feature <id> --task <id>] [--target <dir>] [--json]
 
 Run gate checks for the current (or specified) phase.
 
@@ -159,39 +159,39 @@ Flags:
   --target <dir>    Project directory (default: cwd)
   --json            JSON output`,
 
-  'set-mode': `Usage: harness-dev set-mode <copilot|autopilot> [--target <dir>] [--json]
+  'set-mode': `Usage: dev-harness set-mode <copilot|autopilot> [--target <dir>] [--json]
 
 Switch execution mode. Autopilot requires DEFINE phase or later.`,
 
-  config: `Usage: harness-dev config list [--target <dir>] [--json]
-       harness-dev config get [key] [--target <dir>] [--json]
-       harness-dev config set <key> <value> [--target <dir>] [--json]
+  config: `Usage: dev-harness config list [--target <dir>] [--json]
+       dev-harness config get [key] [--target <dir>] [--json]
+       dev-harness config set <key> <value> [--target <dir>] [--json]
 
 List all parameters with descriptions, or get/set values via dot-notation.
 Use 'config list' to see all configurable parameters, their current values,
 types, allowed options, and descriptions.
 
 Examples:
-  harness-dev config list
-  harness-dev config list --json
-  harness-dev config get gates.enabled
-  harness-dev config set gates.enabled true
-  harness-dev config set mode autopilot
-  harness-dev config set maxRetries 5`,
+  dev-harness config list
+  dev-harness config list --json
+  dev-harness config get gates.enabled
+  dev-harness config set gates.enabled true
+  dev-harness config set mode autopilot
+  dev-harness config set maxRetries 5`,
 
-  pause: `Usage: harness-dev pause [--target <dir>] [--json]
+  pause: `Usage: dev-harness pause [--target <dir>] [--json]
 
 Pause autopilot execution. Autopilot stops after the current phase gate.`,
 
-  resume: `Usage: harness-dev resume [--target <dir>] [--json]
+  resume: `Usage: dev-harness resume [--target <dir>] [--json]
 
 Resume autopilot execution.`,
 
-  learn: `Usage: harness-dev learn "<message>" [--target <dir>] [--json]
+  learn: `Usage: dev-harness learn "<message>" [--target <dir>] [--json]
 
 Append a lesson to the Lessons section of progress.md.`,
 
-  contract: `Usage: harness-dev contract <subcommand> [options] [--target <dir>] [--json]
+  contract: `Usage: dev-harness contract <subcommand> [options] [--target <dir>] [--json]
 
 Subcommands:
   propose --scope "..." [--exclusions "..."] [--criteria "..."]   Generator proposes
@@ -199,7 +199,7 @@ Subcommands:
   status                                                            Show contract state
   escalate [--reason "..."]                                         Human adjudication`,
 
-  worktree: `Usage: harness-dev worktree <subcommand> [options] [--target <dir>] [--json]
+  worktree: `Usage: dev-harness worktree <subcommand> [options] [--target <dir>] [--json]
 
 Subcommands:
   create <name>   Create isolated worktree for a feature
@@ -207,25 +207,25 @@ Subcommands:
   prune           Remove orphaned worktrees
   remove <name>   Clean up worktree (optionally merge branch)`,
 
-  rollback: `Usage: harness-dev rollback <subcommand> [checkpoint] [--target <dir>] [--json]
+  rollback: `Usage: dev-harness rollback <subcommand> [checkpoint] [--target <dir>] [--json]
 
 Subcommands:
   list            Show available checkpoints
   to <tag>        Restore state to a checkpoint
   branch <tag>    Branch off a good iteration`,
 
-  checkpoint: `Usage: harness-dev checkpoint create <label> [--force] [--target <dir>] [--json]
+  checkpoint: `Usage: dev-harness checkpoint create <label> [--force] [--target <dir>] [--json]
 
 Create a manual checkpoint tag (manual/<label>). Requires clean working tree
 unless --force is given.`,
 
-  'detect-tool': `Usage: harness-dev detect-tool [--target <dir>] [--json]
+  'detect-tool': `Usage: dev-harness detect-tool [--target <dir>] [--json]
 
 Scan the project for agent-tool files (CLAUDE.md, .cursorrules, AGENTS.md, etc.)
 and report which coding agents are available. Recommends a tool based on config
 and detected files.`,
 
-  help: `Usage: harness-dev help
+  help: `Usage: dev-harness help
 
 Show the global help message. Alias for --help.`,
 };

package/cli/lib/ralph-inner.mjs

@@ -259,7 +259,7 @@ export function runPhase(targetDir, phase, options = {}) {
     // Human output
     process.stdout.write(output);
     process.stdout.write(`\n═══════════════════════════════════════\n`);
-    process.stdout.write(`Run: harness-dev validate --feature ${feature.id} --task ${task.id}\n`);
+    process.stdout.write(`Run: dev-harness validate --feature ${feature.id} --task ${task.id}\n`);
     process.stdout.write(`═══════════════════════════════════════\n`);
 
     return {
@@ -298,7 +298,7 @@ export function runPhase(targetDir, phase, options = {}) {
   // Human output
   process.stdout.write(output);
   process.stdout.write(`\n═══════════════════════════════════════\n`);
-  process.stdout.write(`Run: harness-dev validate\n`);
+  process.stdout.write(`Run: dev-harness validate\n`);
   process.stdout.write(`═══════════════════════════════════════\n`);
 
   return {

package/cli/lib/ralph-outer.mjs

@@ -98,7 +98,7 @@ export function continuePipeline(targetDir, completedPhase, options = {}) {
 
   if (mode === 'copilot') {
     // Copilot: print instructions for next phase
-    const msg = `${completedPhase.toUpperCase()} complete. Next: harness-dev phase ${nextPhase}`;
+    const msg = `${completedPhase.toUpperCase()} complete. Next: dev-harness phase ${nextPhase}`;
     if (json) {
       return {
         ok: true,
@@ -128,7 +128,7 @@ export function continuePipeline(targetDir, completedPhase, options = {}) {
 
   // Re-check pause before auto-advancing (user may have paused during phase execution)
   if (config.paused) {
-    const msg = `Autopilot paused after "${completedPhase}". Run: harness-dev resume`;
+    const msg = `Autopilot paused after "${completedPhase}". Run: dev-harness resume`;
     if (verbose && !json) {
       process.stdout.write(`\n  ⏸ ${msg}\n`);
     }
@@ -205,7 +205,7 @@ export function continuePipeline(targetDir, completedPhase, options = {}) {
  * Run the full autopilot pipeline from current state through SHIP.
  *
  * This is a convenience wrapper — normally autopilot is triggered
- * by calling `harness-dev phase <name>` while in autopilot mode.
+ * by calling `dev-harness phase <name>` while in autopilot mode.
  *
  * @param {string} targetDir
  * @param {object} [options]

package/cli/lib/ralph-output.mjs

@@ -171,7 +171,7 @@ export function buildDeliverableRetryOutput(phase, mode, maxRetries, resetOnRetr
   }
 
   out += `\n`;
-  out += `When done, run: harness-dev validate\n`;
+  out += `When done, run: dev-harness validate\n`;
   if (resetOnRetry) {out += `Git reset on retry: enabled\n`;}
   if (autoCommit) {out += `Auto-commit: enabled\n`;}
   return out;

package/cli/lib/scaffold.mjs

@@ -418,7 +418,7 @@ export function getVersionFileContent(stack) {
  * Return .gitignore content for the given stack.
  */
 export function getGitignoreContent(stack) {
-  return `# Harness runtime state (regenerated by harness-dev)
+  return `# Harness runtime state (regenerated by dev-harness)
 harness/config.json
 harness/features/feature-list.json
 harness/progress.md

package/cli/lib/state.mjs

@@ -124,7 +124,7 @@ export function loadConfig(targetDir) {
       config: defaults,
       path: cfgPath,
       ok: false,
-      error: `Not found: ${cfgPath}. Run: harness-dev init`,
+      error: `Not found: ${cfgPath}. Run: dev-harness init`,
     };
   }
 

package/package.json

@@ -1,10 +1,10 @@
 {
   "name": "dev-harness-cli",
-  "version": "1.1.0",
+  "version": "2.1.0",
   "description": "Agent-agnostic software development harness CLI — scaffold, phase orchestration, gate validation for any coding agent",
   "type": "module",
   "bin": {
-    "harness-dev": "cli/harness-dev.mjs"
+    "dev-harness": "cli/dev-harness.mjs"
   },
   "files": [
     "cli/",
@@ -39,10 +39,19 @@
   "scripts": {
     "lint": "eslint cli/",
     "lint:fix": "eslint cli/ --fix",
-    "check": "node --check cli/harness-dev.mjs && echo 'Syntax OK'",
+    "check": "node --check cli/dev-harness.mjs && echo 'Syntax OK'",
     "test": "node test/run-all.mjs",
     "test:verbose": "node test/run-all.mjs --verbose",
-    "postinstall": "node -e \"try{process.stdout.write('harness-dev installed. Run: npx harness-dev --help\\n')}catch(e){}\""
+    "postinstall": "node -e \"try{process.stdout.write('dev-harness installed. Run: npx dev-harness --help\\n')}catch(e){}\""
+  },
+  "dependencies": {
+    "ajv": "^8.17.1",
+    "ink": "^5.1.0",
+    "p-retry": "^6.2.1",
+    "picocolors": "^1.1.1",
+    "react": "^18.3.1",
+    "simple-git": "^3.27.0",
+    "string-width": "^7.1.0"
   },
   "devDependencies": {
     "@eslint/js": "^10.0.1",

package/templates/AGENTS.md

@@ -3,9 +3,9 @@
 ## Quick Start
 
 ```bash
-harness-dev status        # Where are we?
-harness-dev phase <name>  # Invoke a phase
-harness-dev validate      # Check gate criteria
+dev-harness status        # Where are we?
+dev-harness phase <name>  # Invoke a phase
+dev-harness validate      # Check gate criteria
 ```
 
 ## Project
@@ -50,8 +50,8 @@ All harness-managed files live under `harness/` (except `AGENTS.md` which stays
 2. Read `harness/progress.md` + this file before each operation
 3. Commit frequently — each iteration is a checkpoint
 4. If unsure → read the role guide in `harness/docs/agents/`
-5. Never skip gates — run `harness-dev validate` after each phase
-6. Fresh context per retry — pass `--git-ops` to `harness-dev phase <name>` to auto-reset the working tree on retry (off by default; agent-agnostic)
+5. Never skip gates — run `dev-harness validate` after each phase
+6. Fresh context per retry — pass `--git-ops` to `dev-harness phase <name>` to auto-reset the working tree on retry (off by default; agent-agnostic)
 7. **No files in project root** unless they are harness-managed files (listed in Key Files above) or standard project files (README.md, LICENSE, CHANGELOG.md, CONTRIBUTING.md, .gitignore, and the stack config file like package.json/pyproject.toml/Cargo.toml). All source code, tests, scripts, and docs go in subdirectories.
 8. **Structure from the start** — create folders for your work on day one and stick to them. Suggested layout: `src/` (source), `tests/` (tests), `docs/` (documentation), `scripts/` (automation). Do not dump files at root "temporarily" — there is no temporary.
 9. **No orphaned files** — every file you create must have a clear purpose and be referenced by imports, configs, docs, or the build system. If you create a file, wire it in immediately. Delete files you stop using.

package/templates/ci/github-actions.yml

@@ -75,4 +75,4 @@ jobs:
     steps:
       - uses: actions/checkout@v4
       - run: npm install -g dev-harness-cli
-      - run: harness-dev validate --json
+      - run: dev-harness validate --json

package/templates/ci/gitlab-ci.yml

@@ -55,5 +55,5 @@ gate:
   image: node:lts
   script:
     - npm install -g dev-harness-cli
-    - harness-dev validate --json
+    - 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/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/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

@@ -10,7 +10,7 @@ Retry Count: 0/{{maxRetries}}
 
 ## Lessons
 
-<!-- Use \`harness-dev learn "lesson here"\` to add lessons. -->
+<!-- Use \`dev-harness learn "lesson here"\` to add lessons. -->
 
 ## Checkpoints