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

harness: say which settings file the exemption means

Browse Source 
The exemption is Claude Code's permission list, not "settings files". khosra will
have its own configuration and none of it is exempt: the engine's settings live in
the site root and the engine validates them, while scripts/budgets.env and
everything else under scripts/ and .claude/ stays gated. Verified by touching
budgets.env and watching the coupling gate fail.
This commit is contained in:
Claude Opus 5
2026-07-30 01:39:28 +06:00
committed by bdeshi
parent d0197a41ed
commit f37e7b1308
2 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
HARNESS.md
+3 -2
View File
@@ -142,8 +142,9 @@ The harness is code and drifts like code. Same rule as the engine: **a change sh
that describe it, in the same change.** that describe it, in the same change.**
- `verify.sh` fails when `CLAUDE.md`, `scripts/` or `.claude/` changes without `HARNESS.md` - `verify.sh` fails when `CLAUDE.md`, `scripts/` or `.claude/` changes without `HARNESS.md`
changing — except `.claude/settings.json`, which is permissions rather than mechanism and owes no changing — except `.claude/settings.json`, which is Claude Code's permission list rather than anything
explanation. This file is the current description of the machine, not a snapshot of its design. about khosra. That exemption is one path: `scripts/budgets.env` and every other file under `scripts/`
and `.claude/` stays gated, and khosra's own settings are not exempt from anything. 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 - `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 `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`. `gofmt`-only diff is exempt: it ships no behaviour, and failing it would only teach you `--no-verify`.
scripts/verify.sh
+5 -2
View File
@@ -76,8 +76,11 @@ if [ -d .git ] && command -v git >/dev/null 2>&1; then
pass "templates/theme-contract coupling" pass "templates/theme-contract coupling"
fi fi
# settings.json is permissions, not mechanism — HARNESS.md calls it a convenience, so a tweak there # One exemption, and it is about the agent tooling rather than this project: .claude/settings.json is
# owes no explanation. Everything else under .claude/ changes how the machine behaves. # Claude Code's own permission list, which HARNESS.md calls a convenience, so editing it explains
# nothing about khosra. khosra's own configuration is not exempt from anything — the engine's settings
# live in the site root (content-model.md) and the engine validates them itself. Everything else under
# .claude/, and all of scripts/ including budgets.env, changes how the machine behaves and is gated.
harnesschanged=$(echo "$changed" | grep -E '^(CLAUDE\.md$|scripts/|\.claude/)' | grep -v '^\.claude/settings\.json$' || true) harnesschanged=$(echo "$changed" | grep -E '^(CLAUDE\.md$|scripts/|\.claude/)' | grep -v '^\.claude/settings\.json$' || true)
if [ -n "$harnesschanged" ] && ! echo "$changed" | grep -qx 'HARNESS.md'; then if [ -n "$harnesschanged" ] && ! echo "$changed" | grep -qx 'HARNESS.md'; then
bad "the harness changed (CLAUDE.md, scripts/ or .claude/) but HARNESS.md did not — the guide to the machine is part of the machine" bad "the harness changed (CLAUDE.md, scripts/ or .claude/) but HARNESS.md did not — the guide to the machine is part of the machine"