completelyinitlisted

You are scaffolding the **claude-harness** project thin layer into the current repo. The heavy logic (hooks, evaluator agent) ships with the plugin/global install; this only adds the small per-project pieces. **Never overwrite an existing file without asking** (unless the user passed `--force`). ## Steps 1. **Locate the repo root** (`git rev-parse --show-toplevel`, else cwd) and **detect the stack**: - `pyproject.toml` / `setup.cfg` → Python (commands: `ruff check`, `mypy`, `pytest`) - `package.json` → JS/TS (read its `scripts`; commands likely `eslint .`, `tsc --noEmit`, `vitest run` / `jest`) - `go.mod` → Go; `Cargo.toml` → Rust. Record the real lint/typecheck/test commands. 2. **Create `.claude/` and `.claude/harness/`** if missing. 3. **Write `.claude/DEFINITION_OF_DONE.md`.** Copy the harness template. Locate it under the installed plugin (try `${CLAUDE_PLUGIN_ROOT}/templates/DEFINITION_OF_DONE.md`, then `~/.claude/harness/core/`); if you can't find it, regenerate it from the canonical content you know (default-FAIL checklist). Fill in the detected stack's commands. 4. **Merge the harness rules into the project `CLAUDE.md`.** If `CLAUDE.md` exists, append the `CLAUDE.harness.md` snippet (between its `<!-- claude-harness -->` markers) — do not duplicate if already present. If no `CLAUDE.md`, create a minimal one with the snippet. Fill in the real project commands you detected in step 1. 5. **Project quality command (optional).** If the rep