go 1.0.1: a consumer's go mod tidy works again (closes #454)

[EricAndrechek]

go 1.0.1: a consumer's go mod tidy works again. Closes #454.

The defect (measured against the published go/v1.0.0 from the Go proxy):

• A consumer's go mod tidy fails, because the module "does not contain package github.com/wave-rf/chtypes/go/internal/testhook".
• The consumer's go.sum therefore stays incomplete, and a fresh consumer's go build fails too.

The cause:

• Five retained 0.x files in go/chtypes/ sat behind //go:build chtypes_v0_retired.
• go mod tidy considers every build tag except ignore, so it resolved their imports.

The fix:

• The five constraint lines become //go:build ignore. The files stay in the tree and stay protected; their deletion is still held in Held for the maintainer: delete the five retained v0 Go verification files and prune their protected-path entries #431.
• scripts/release-verify.sh: the Go consumer module now runs go mod tidy with no -e, no output masking and no || true. Every release dry run and every post-publish verify runs a real consumer tidy.
• Go's bindingVersion is now 1.0.1, and go/CHANGELOG.md has the 1.0.1 entry.

Measured locally:

• With the fix on a copy of v1:
  • the module's own go mod tidy (no -e) leaves go.mod/go.sum byte-identical;
  • a consumer (with replace) gets go mod tidy exit 0 and go mod tidy -diff exit 0, and go build succeeds.
• On this branch:
  • go vet ./..., the User-Agent tests and golangci-lint (0 issues);
  • release-verify.sh --selftest and shellcheck;
  • policy-merge-check --check-carve-out and --check-guide;
  • lint-public, lint-spelling and lint-cited-paths;
  • markdownlint and dprint.

After merge:

1. A release-go dry run from the merged head, where the consumer tidy runs with no -e against the local module.
2. Then go/v1.0.1 on that head.
3. Post-publish verify runs against the PROXY copy, consumer tidy included.

🤖 Generated with Claude Code

https://claude.ai/code/session_012NdkF6p8Q3qkdxKCgbdjgb