bdeshi/khosra
0
0
Fork 0
Code Issues Pull Requests Releases Activity

harness: permissions changes owe no HARNESS.md note

Browse Source 
The coupling gate treated every path under .claude/ as mechanism, so editing the
pre-approved command list demanded an explanation of a machine that had not
changed. HARNESS.md already calls settings.json a convenience — if its schema
changed the harness would still work, you would just get more prompts — so the
gate now exempts that one file and nothing else.

Carries the settings.json edit that exposed it.
This commit is contained in:
Claude Opus 5
2026-07-30 01:35:14 +06:00
committed by bdeshi
parent 242bd60d9c
commit 2466ce79c7
3 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HARNESS.md
+2 -1
View File
@@ -140,7 +140,8 @@ The harness is code and drifts like code. Same rule as the engine: **a change sh
that describe it, in the same change.**
- `verify.sh` fails when `CLAUDE.md`, `scripts/` or `.claude/` changes without `HARNESS.md`
changing. This file is the current description of the machine, not a snapshot of its design.
changing — except `.claude/settings.json`, which is permissions rather than mechanism and owes no
explanation. This file is the current description of the machine, not a snapshot of its design.
- `verify.sh` fails when a `.go` file changes without `docs/state.md` changing, and when `cmd/` or
`internal/` code changes without a `_test.go` changing — behaviour ships with a test. A comment-only or
`gofmt`-only diff is exempt: it ships no behaviour, and failing it would only teach you `--no-verify`.