add a Makefile and build instructions

So the thing can be built and run without reading the harness. Eight targets,
each one go command or verify.sh; make help lists them. README gains the four
lines someone actually needs, and says a site root is a directory the binary is
pointed at rather than something in this repo.

make is recorded in toolchain.md as a convenience: the gate never invokes it, so
a machine without make loses nothing but typing.
This commit is contained in:
Claude Opus 5
2026-07-30 01:38:17 +06:00
committed by bdeshi
parent e14171fa02
commit d0197a41ed
3 changed files with 55 additions and 2 deletions
+5 -2
View File
@@ -32,8 +32,11 @@ These are the ones most likely to move, and the ones whose breakage looks like a
## 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.
`go mod`. The `Makefile` is a convenience wrapper only: every target is one `go` or `verify.sh` command,
and the gate never invokes `make`, so a machine without it loses nothing but typing.
`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.