verify-harness

<!-- rig-generated --> # verify-harness — Post-Install Verification Run this skill after `rig init` to confirm everything is working. ## Procedure Run each check and report PASS/FAIL with evidence. ### Session Start Hook - [ ] **S1**: Session started without hook errors - [ ] **S2**: Run `which rtk` — report if available - [ ] **S3**: Run `which jcodemunch-mcp` (or `which uvx`) — report if available - [ ] **S4**: Check if CWD is indexed: run `jcodemunch-mcp list-repos` if available - [ ] **S5**: Check `.harness.yaml` exists and parses - [ ] **S6**: Session-start reports `superpowers: installed` (else install via `/plugin install superpowers@claude-plugins-official`) - [ ] **S7**: If headroom is configured, run `headroom doctor --json` — report pass/warn/fail (proxy liveness, routing, savings flow) ### Tool Router (PreToolUse Hook) - [ ] **TR1**: Run `grep -r test .` in a test call — does the hook intercept it? - [ ] **TR2**: Run `find . -name '*.ts'` — does the hook intercept it? - [ ] **TR3**: Run `sed -i 's/old/new/g' file` — does the hook BLOCK it? - [ ] **TR4**: Run `git status` — does the hook advise rtk (if available)? - [ ] **TR5**: Run `Read` on a specific file — does it pass through? - [ ] **TR6**: Run `Grep` tool — does it advise jcodemunch (if indexed)? - [ ] **TR7**: Run `Glob` tool — does it advise jcodemunch (if indexed)? - [ ] **TR8**: Reference an external directory — does it trigger auto-index? ### Enforcement (PostToolUse Hook) - [ ] **E1**: Edit a...