init

2026-07-30 00:34:18 +06:00
commit 54c14a20be
33 changed files with 2730 additions and 0 deletions
@@ -0,0 +1,45 @@
+# Toolchain and external contracts
+
+What this harness was built against, and which of those are contracts it depends on rather than
+incidentals. Recorded because a failure long after the fact is otherwise indistinguishable from a bug in
+the harness itself. Update the version line when you deliberately move; leave the rest alone.
+
+**Verified working:** 2026-07-28
+
+| Thing | Version then | Harness depends on |
+|---|---|---|
+| Go | 1.26.1 (darwin/arm64) | `go list -f`, `go vet`, `go build`, `go test -race`, `gofmt -l`. All stable since 1.11 |
+| git | 2.53.0 | `status --porcelain -uall`, `rev-list <sha>..HEAD -- '*.go'`, `rev-parse --verify`, `core.hooksPath` (2.9+) |
+| Claude Code | 2.1.119 | the four formats below |
+| bash | macOS default (3.2-era) + BSD userland | `verify.sh` avoids bashisms and GNU-only flags; `grep -L`, `wc -l`, `xargs`, `awk` are POSIX use |
+
+## The four agent-tooling contracts
+
+These are the ones most likely to move, and the ones whose breakage looks like a harness bug:
+
+1. **`CLAUDE.md` is loaded automatically** from the repo root on every request. If that stops being true,
+   nothing enforces the constitution and the agent will behave like a stock assistant.
+2. **`.claude/skills/<name>/SKILL.md`** — a Markdown file in a directory named for the skill, which fires
+   on request content matching its description. The feature loop depends on firing *without* being
+   invoked; if skills come to need explicit invocation, the loop silently stops applying.
+3. **`.claude/commands/<name>.md`** — Markdown with a YAML frontmatter `description:`, invoked as
+   `/<name>`, `$ARGUMENTS` substituted. Used by `/verify`, `/audit`, `/leaf`, `/refresh-docs`, `/adr`,
+   `/invariants`.
+4. **`.claude/settings.json`** — a `permissions` object with `allow` / `ask` / `deny` arrays of
+   `Tool(pattern)` strings. Only a convenience: if the schema changes, the harness still works, you just
+   get more prompts.
+
+## Not depended on
+
+No CI service, no container registry, no language server, no linter binary, no package manager beyond
+`go mod`. `verify.sh` runs offline with nothing but Go and git on `PATH`, which is deliberate — the gate
+must work on a machine you have not configured for two years.
+
+`VERIFY_DOCKER=1` adds a container build step and needs `docker`; it is opt-in and off by default.
+
+## If something breaks after a long absence
+
+Check in this order, cheapest first: `go version` and `git --version` against the table above; then
+whether `verify.sh` fails in the `documentation` block (a harness-internal problem) or the `go` block (a
+toolchain or code problem); then whether the agent is still reading `CLAUDE.md` at all — ask it to quote
+a hard rule, and if it cannot, the problem is contract 1 and nothing downstream will behave.