Claude Opus 5andbdeshi
e6c0673374
Earned by a real mistake this session: `web.Handler` gained a parameter, its caller in cmd/ was updated in the working tree, and `git add internal docs` left that caller out. verify.sh was green throughout, because every gate looks at the files on disk rather than at the commit being made. The result was a commit that did not compile — the kind of thing git bisect trips over for as long as the repo exists. I rewrote the two local commits rather than adding a fix-up on top. The check builds a throwaway checkout of the index via `git write-tree`, so it cannot touch the real index or working tree, and it only runs when something is staged. Proved both directions: staging a signature change without its caller fails, a clean tree passes. Eighth gate defect found by running the harness against real work rather than reasoning about it — and the first that was a missing gate rather than a wrong one.
khosra
A flat-file personal publishing engine in Go. Point the binary at a directory of Markdown and it becomes an owned, networked home for fiction, webcomics, art, and essays, in English and Bengali. The site's content lives in its own repository, not this one (ADR-0011).
Build and run
Needs Go 1.26+ and git; nothing else.
make build # or: go build -o khosra ./cmd/khosra
make run SITE=/path/to/site # or: ./khosra -site /path/to/site
make test
make verify # everything the project enforces — green before every commit
make help lists targets. make is a convenience wrapper; go build, go test and
./scripts/verify.sh work on their own and are what the gate uses.
A site root is a directory holding content/, and optionally static/ and templates/. It lives in its
own repository, not this one — the binary is pointed at it.
If you are a human: start at HARNESS.md — what the scaffolding is, how to use it, and what to decide.
If you are an agent: start at CLAUDE.md — the constitution and the read order. It is loaded for you automatically; this file is not a prerequisite and nothing here is a rule.