zeekayandHanzo Dev acb9f38d95 zap: make the rename shippable, and give the golden fixture its generator ...

The rename to `zapwire` was inert: `cargo publish` refused the manifest
outright with

    all dependencies must have a version requirement specified when
    publishing. dependency `zapc` does not specify a version

so nothing could leave the workspace, and crates.io still resolved
`hanzo-zap` to THIS repo via 0.2.1 — the collision the rename exists to
end. The build-dependency now carries both a path and a version: the
path is what the workspace builds against, the version is what a
published `zapwire` resolves from crates.io. `zapc` gains the
`repository` link it was missing, since a crate whose repository field
points at the wrong source is precisely how the `hanzo-zap` confusion
started (0.2.1 declares `repository = hanzoai/zap` from a zap-proto/spec
checkout).

crosswire.rs told the reader to regenerate its golden hex with
`tests/gen_golden.go` — a file that does not exist, leaving hand-editing
hex as the only option the comment explicitly forbids. `interop/golden`
is that generator, and it emits the finished Rust `const` lines rather
than bare hex so there is no transcription step to get wrong. Its output
reproduces the committed fixture byte-for-byte.

`go vet ./interop` -> `go vet ./...`, so the new package is covered by
the same gate rather than needing its own line.

make test: 27 lib + 10 crosswire + 2 live-Go interop, green, exit 0.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-28 23:18:52 -07:00

..

golden

zap: make the rename shippable, and give the golden fixture its generator

2026-07-28 23:18:52 -07:00

main.go

zap: give Rust a real client, and stop two codebases sharing one crate name

2026-07-28 22:52:13 -07:00