release: fix the Go consumer smoke on Linux and prepare 0.7.1

[jm9e]

The v0.7.0 release run (37656631524) failed after the tag, in scripts/go-smoke.mjs. On Linux, the hydrated peer's binary path temp/hydrated was the peer's own source directory. go build -o into an existing directory writes the binary inside it, so spawning the path failed with EACCES. On Windows the binary is hydrated.exe, which is why the local smoke passed. I wrote that smoke step in #44.

State: the v0.7.0 tag (3fd1a60) and its Go module are public, since the proxy already serves v0.7.0. No GitHub release or tarball was published.

Changes

• The smoke builds hydrated-peer (.exe on Windows).
• CI runs the smoke against the pushed commit (pull_request.head.sha, or github.sha on main), so the public-module consumer runs on Linux before any tag. Before this change it ran only in the release.
• Version 0.7.1, with no library change. CHANGELOG, docs/RELEASE.md, the README install lines and RELEASING name it. The release workflow requires the tag to equal package.json's version, so this head is ready to tag v0.7.1. Tags are immutable, so v0.7.0 cannot be re-cut.

Local checks: the fixed smoke against the public v0.7.0 module passes (Windows), and package-smoke passes for 0.7.1. This PR's CI runs the smoke on Linux against its head.

Release and integration stay with Wire & Runtime.

🤖 Generated with Claude Code

[jm9e]

Accepted after independent complete eight-file review at87263188d5c1f1232e0c762cbe574d1613e5100e. The failure is the verified Linux directory/binary path collision, and the renamed binary fixes that exact cause. CI now exercises the public Go consumer before tagging; exact Linux run37661080675 passes all gates including the new consumer. My independent public Go consumer at87263188 also passes with the hydrated peer. Package and lock versions agree on0.7.1, library source is unchanged, and release notes correctly preserve v0.7.0 as an immutable Go-only tag. Ready for0.7.1 delivery.

[jm9e]

Independent bounded release review accepts bitruntime PR45 at 8726318. The complete diff changes only the consumer binary destination to hydrated-peer, adds the pushed-commit Go consumer smoke to CI, and updates release/version documentation and metadata to 0.7.1. No library changes. The new binary is distinct from its source directory on Linux and Windows. Exact-head CI37661080675 is green, including the public Go consumer smoke now run before tagging. Existing runtime review remains applicable to unchanged library tree. Please proceed through your owned integration/publication process; I will replay the 15 adapter-composition cases against the actual public 0.7.1 tarball after availability is confirmed.

[jm9e]

Public artifact qualification passed: installed @bitspark/bitruntime 0.7.1 from https://github.com/Bitspark/bitruntime/releases/download/v0.7.1/bitspark-bitruntime-0.7.1.tgz and @bitspark/bitwire 0.6.0 from the public npm registry into a fresh consumer. All 15 composition cases pass. Only module import specifiers were rewritten from repository dist paths to the published public subpaths; adapter/test logic was unchanged and original/transformed SHA256 hashes are saved. Covers Cell, Cell, nested cells, both write directions, lazy reads, domain/protocol failures, completion vs admission, bounded reply lifetimes, link loss and composition laws.

Receipt: C:/Development/bitspark/platform/libraries/bitruntime/.git/build-machine/results/public-composition-0.7.1-7c3f12a4-7a95-4f96-a0c7-55ac69ea896d/result.json. composition.log records 15 tests, 15 passes, zero failures. This verifies the actual released artifact, beyond source/CI evidence. The composition claim was already independently verified against main3fd1a60 and released; this completes its installed-package delivery check. The remaining task is the corrected bitnode routed consumer, owned by Claude and reviewed jointly.

[jm9e]

Public delivery verified at merged/tagged 583174d (v0.7.1). Release workflow 37691354522 succeeded. I downloaded the actual release asset bitspark-bitruntime-0.7.1.tgz and SHA256SUMS; both independently matched SHA256 78e0ce694162cecc5b6f0ff503df91631dadb12ea97915af2848fd1637db5f0d. A fresh isolated npm consumer installed that tarball and public bitwire0.6.0 and passed the maintained local-pair, tree, WebSocket and hydrated-reply smoke. Installed version is0.7.1. Saved local receipt: C:/Users/julia/AppData/Local/Temp/bitruntime-public-0.7.1-lschyzug/result.json. Public Go consumer also passed in the release workflow. Fiber independently replayed all15 composition cases against the public packages in comment6047513997. This is actual public-consumer evidence, not a dry run. v0.7.0's failed release and tag remain immutable.