uni-harness 0.1.0 → 0.1.2

package/.claude/skills/harness-init/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: harness-init
-description: Scan the repository of a new project to fill in the PROJECT section of CLAUDE.md and .harness/commands.env, and propose initial RULES/ANTI-PATTERNS. Run once right after installing the harness, or whenever CLAUDE.md is still in placeholder state. Verifies detected commands by actually running them before applying.
+description: Scan the repository to fill in the PROJECT section of CLAUDE.md and .harness/commands.env, and propose initial RULES/ANTI-PATTERNS. Run once right after installing the harness, or whenever CLAUDE.md is still in placeholder state. Verifies detected commands by actually running them before applying. If the repo has no project code yet (greenfield), offers to scaffold a minimal project so the sensors start active from the first line of code.
 ---
 
 # Harness Init — Initialize the Harness by Scanning the Repo
@@ -11,6 +11,16 @@ running them.
 
 ## Step 1: Scan
 
+- **Exclude the harness's own files first.** Everything the installer put
+  here — `.claude/`, `.harness/`, `harness/` — is the kit's machinery, not
+  the project. Never let it drive language detection, and never propose the
+  kit's self-test (`harness/tests/test_hooks.sh`) as the project's TEST_CMD:
+  it verifies the harness, not the user's code, and pointing the stop gate
+  at it would "pass" every turn regardless of what broke.
+- The scan decides which mode you are in: project code exists → continue
+  with Step 2 (and the brownfield section if the project predates the
+  harness). Nothing but harness files → switch to the **New Projects
+  (greenfield)** section below. Do not stop at "nothing to configure".
 - Language/version: from manifests (package.json, pyproject.toml, go.mod,
   Cargo.toml, *.csproj, ...). Prefer versions pinned in lockfiles/config.
 - BUILD / TEST / LINT candidates: collect from manifest scripts, Makefile,
@@ -38,6 +48,32 @@ running them.
   truisms ("write good code") are forbidden — only things observable in
   this repository.
 
+## New Projects (greenfield — the harness was installed before any code)
+
+If the scan finds no project code at all (no manifest, no sources, no CI),
+the user is starting a project *with* the harness — the whole point is
+that sensors guard the very first code written. Ending with "come back
+later" leaves them off during the riskiest phase. Instead, offer to
+bootstrap:
+
+1. **Ask, don't guess:** what is being built, which language/runtime,
+   which framework and test runner (offer the ecosystem defaults, e.g.
+   pytest / vitest / go test).
+2. **Propose a minimal scaffold** and apply it only after approval: the
+   manifest (package.json / pyproject.toml / go.mod ...), a source entry
+   point, a test setup with **one real passing test**, and a
+   linter/formatter config if the ecosystem has a standard one. Announce
+   any dependency installs with the reason before running them.
+3. If it is not a git repository, offer `git init` (the guard hooks and
+   future ANTI-PATTERNS mining assume git history).
+4. Then continue with Step 2 exactly as usual: run the scaffold's
+   BUILD/TEST/LINT commands, confirm they pass, and fill CLAUDE.md and
+   commands.env with the **verified** commands.
+
+The exit criterion for greenfield: sensors ACTIVE against a real (if tiny)
+test suite. If the user declines the scaffold, leave everything blank as
+before and tell them to re-run /harness-init once code exists.
+
 ## Existing Projects (brownfield)
 
 - If CLAUDE.md existed before the harness was installed, never replace it.

package/bin/cli.js

@@ -27,6 +27,10 @@ const { spawnSync } = require('child_process');
 
 const PKG_ROOT = path.resolve(__dirname, '..');
 const MACHINERY_DIRS = ['.claude/hooks', '.claude/skills', '.claude/agents', 'harness'];
+// Files that live in these dirs but belong to the kit repository only.
+// test_installer.sh tests bin/cli.js, which is never installed into target
+// projects — shipping it there guarantees a failing test suite.
+const KIT_ONLY_FILES = new Set(['harness/tests/test_installer.sh']);
 const MANIFEST = '.harness/kit-manifest.json';
 const KIT_VERSION = require(path.join(PKG_ROOT, 'package.json')).version;
 
@@ -53,7 +57,9 @@ function machineryFiles() {
   const files = [];
   for (const d of MACHINERY_DIRS) {
     for (const f of walk(path.join(PKG_ROOT, d))) {
-      files.push(path.relative(PKG_ROOT, f));
+      const rel = path.relative(PKG_ROOT, f).split(path.sep).join('/');
+      if (KIT_ONLY_FILES.has(rel)) continue;
+      files.push(rel);
     }
   }
   return files.sort();

package/harness/tests/test_installer.sh

@@ -40,6 +40,9 @@ check "writes manifest" "yes" "$([ -f "$TGT/.harness/kit-manifest.json" ] && ech
 check "gitignores logs" ".harness/logs/" "$(cat "$TGT/.gitignore")"
 check "init runs hook tests" "Hook tests passed" "$OUT"
 check "prints next step" "/harness-init" "$OUT"
+# regression: test_installer.sh tests bin/cli.js, which only exists in the
+# npm package — shipping it to targets guarantees a failing suite there
+check "does not ship test_installer.sh" "EMPTY" "$([ -f "$TGT/harness/tests/test_installer.sh" ] && echo left)"
 
 # ── brownfield init: existing project files are preserved ────────
 echo "init (brownfield)"
@@ -82,6 +85,22 @@ check "states owned files untouched" "were not touched" "$OUT"
 OUT=$(node "$CLI" update "$TGT" --force 2>&1)
 check "--force overwrites modifications" "EMPTY" "$(grep -F 'local customization' "$TGT/.claude/hooks/guard-pre-bash.sh" || true)"
 
+# simulate a v0.1.0 install that shipped test_installer.sh: an unmodified
+# manifest-tracked copy must be cleaned up by update
+cp "$ROOT/harness/tests/test_installer.sh" "$TGT/harness/tests/test_installer.sh"
+python3 - "$TGT" <<'EOF'
+import json, sys, hashlib, os
+t = sys.argv[1]
+mp = os.path.join(t, '.harness/kit-manifest.json')
+m = json.load(open(mp))
+p = os.path.join(t, 'harness/tests/test_installer.sh')
+m['files']['harness/tests/test_installer.sh'] = hashlib.sha256(open(p, 'rb').read()).hexdigest()
+json.dump(m, open(mp, 'w'), indent=2)
+EOF
+OUT=$(node "$CLI" update "$TGT" 2>&1)
+check "update removes stale kit-only file" "removed from kit" "$OUT"
+check "stale file is gone" "EMPTY" "$([ -f "$TGT/harness/tests/test_installer.sh" ] && echo left)"
+
 # ── doctor ───────────────────────────────────────────────────────
 echo "doctor"
 OUT=$(node "$CLI" doctor "$TGT" 2>&1)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uni-harness",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "Agent harness kit for Claude Code — installs verification sensors, destructive-command guards, checkpoint recovery, observability logs, and ratchet skills into your project",
   "bin": {
     "uni-harness": "bin/cli.js"