[Lutherwaves]

Milestone 1 of the Go port (spec: docs/superpowers/specs/2026-10-25-go-port-and-cleanup-design.md, plan: docs/superpowers/plans/2026-10-26-go-port-m1.md).

One builder binary now does what the Python does: hook, ledger, reach, security, budget and mcp-merge, plus go run ./cmd/support-table. The committed shim bin/builder runs the binary pinned to the plugin version, or exits 3 with the install line. The Python stays and still runs everything; milestone 2 switches the callers to the shim and deletes it.

• tests/test_parity.sh runs the Python and the Go on the same inputs, 27 cases: text compared byte for byte, JSON after jq -S, plus ledger and reach files written in one language and read in the other.
• Every Python test case is ported to Go tests.
• scripts/validate.sh gains a → go step: gofmt, go vet, go test, the shim test and parity. CI sets up Go from go.mod.

Calls made on the way (each with its reason in the commits):

• A non-UTF-8 Codex config.toml reads as empty, as in the Python.
• The support table keeps fixtures in file order, so the README does not drift.
• builder budget with a bad number prints the usage and exits 2; the Python crashed with a traceback.
• The reach dedupe digest folds case with a table generated from Python's str.casefold.

Deferred minors (edge cases where the Go differs from the Python; none on a path a skill takes today): mcp-merge loses big-int precision and key order; non-UTF-8 reach.json is accepted; U+0085 in a logged text; a mapping block with no closing marker; +Inf vs inf; cli.Repr corner cases; one OS-reason wording; greedy version read on a one-line manifest; notifier WaitDelay; no kill test.

🤖 Generated with Claude Code