[Lutherwaves]

Milestone 2 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-m2.md). It targets feat/go, not main: a git install runs main HEAD, and no release has the binary yet.

Every caller now runs the Go binary through bin/builder, and the Python is gone.

• The session hook and the opencode plugin run bin/builder hook. With no binary, the hook prints the soul, exits 0, writes nothing on stderr, in under 1 s. With a broken PATH, it still gives the full text: the shim needs only Bash builtins.
• The budget, reach and security skills and their eval allow rules name "${CLAUDE_PLUGIN_ROOT}/bin/builder" <command>. The budget skill finds an old watcher job that runs burn-proj.py and offers to replace it.
• skills/harness/setup.sh merges .mcp.json with jq or builder mcp-merge. mcp-merge now keeps key order and exact numbers, byte-identical to the jq path.
• The eval runner uses jq and the binary; the parity config block is a dev-only Go command, cmd/parity-config. Its path check follows os.path.realpath, which closes a hole where $HOME/missing/.. passed the guards.
• The template test is Go (tests/templates_test.go).
• Deleted: every .py outside the eval sample projects, the Python unittests, tests/test_parity.sh, tests/parity/.
• scripts/validate.sh needs Go, builds the binary once, and fails on a tracked .py, a python3 word, an old tool path, or a skill that runs the shim without the quoted plugin root. A failed build is one error.

Proof: bash scripts/validate.sh passes; go test -count=3 ./... passes; tests/test_validate.sh 0 failures; a fake python3 first on PATH is never called; the hook ran end to end with a versioned binary under a temp BUILDER_HOME (45 ms) and with an empty one (soul only).

Evals not run: the paid runs for budget, reach, security and security-audit would prove the new allow patterns match what Claude Code allows. Run them before feat/go merges to main.

Calls made on the way:

• feat/go caught up with main by a merge (chore: bring feat/go up to main), no force push.
• The two milestone 1 fixes (builtins-only shim, ordered mcp-merge) land here, because this milestone makes both paths live.
• The template test is excluded from the old-name guard, since it pins burn-proj.py on purpose.

Milestone 3 must: ship scripts/install.sh (the shim's message names it); fix README.md:55 and docs/install.md:3, which still say Python 3 is needed; check the shim on macOS Bash 3.2.

🤖 Generated with Claude Code