harnesslisted

# Harness — compliance gate (canonical in-repo) **Authority:** [repository-harness](https://github.com/hoangnb24/repository-harness) **Pins:** protocol floor `harness-cli-v0.1.14` · trust CLI **`harness-cli-v0.1.17`** · **never** `0.1.16` assets. Install optional copy to `~/.agents/skills/harness` for global discovery; this file is the **CI-tested** source of truth under `flow-skill/skills/harness-skill/`. ## Scope guard - If cwd has **neither** `scripts/bin/harness-cli` / `harness-cli.exe` **nor** a flow project using `/flow harness` → early-exit (not a harness task). - Non-dev questions → early-exit; do not force intake. ## Before any mutation 1. Prefer: `harness-cli query contract --json` (discover protocol / schema / capabilities). 2. Require awareness of protocol_version 1 when using machine orchestration. 3. Read-only requests (explain, review, status) must **not** intake/trace/bootstrap. ## Story status (trust) - **Forbidden:** `story update --status implemented` - **Required:** `story complete` with proof (upstream) **or** flow-native `story complete --id … --proof-source card_markdown_gate|manual|verify_command` - Never forge shell verify pass from markdown alone. ## SQL - If using `query sql`: treat as **read-only**. Mutating SQL is a trust violation on modern CLI. ## Lane (FEATURE_INTAKE spirit) Hard gates (auth, authz, data model, audit, external provider behavior, removing validation) → high_risk. Scout files before classifying; draft → user c