harnesslisted

# Harness — compliance gate (canonical in-repo) **Live authority:** flow durable Python (`/flow harness` → `skills/flow/harness/flow_harness.py`) + mechanical `flow.sh` + semantic `gate-rules.md`. **Historical:** pre-EOL repository-harness protocol v1 is archive only (last published `harness-cli-v0.1.22`). See `skills/flow/harness/GAP-MATRIX-0.1.17.md` (SUPERSEDED). 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 - Prefer **flow projects**: use `/flow harness …` (Python backend). - If cwd has **neither** a flow project (`.flow/` or `flow/`) **nor** `scripts/bin/harness-cli` / `harness-cli.exe` → early-exit (not a harness task). - Non-dev questions → early-exit; do not force intake. ## Before any mutation 1. On flow projects: `flow.sh harness query matrix` (or `/flow harness query matrix`). 2. Legacy archive binary (if present): optional `harness-cli query contract --json` — **not** required; not a live product pin. 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 **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` on an archive binary: treat as *