The %w advisory counted every fmt.Errorf without %w, including calls that create an error rather than wrap one — so it fired permanently on correct code. It now looks for a call that passes an err and drops the %w, which is the actual rule. Recorded the general form in the loop's Verify step and in HARNESS.md: a warning that fires on correct code and keeps firing is a defect in the check or the code, resolved in that change. Two advisories have now been narrowed after firing on code the harness itself mandates, and the count creeping from one to two was the only signal either time. verify.sh is at zero warnings, which is what makes the next one legible.
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.