Audit GoReleaser configuration against the release workflow version

[apstndb]

Deferred from local repository review cleanup.

Problem

.goreleaser.yaml still looks close to the generated example template and should be audited against the GoReleaser version used by the release workflow.

Known review notes:

• The top comments still describe the file as an example.
• The release workflow uses goreleaser/goreleaser-action@v6.
• The config uses version: 2.
• Archive configuration should be checked against the current GoReleaser v2 schema before changing fields such as archive formats.

Proposed work

• Install or run the same GoReleaser version used by the action.
• Run a config check against .goreleaser.yaml.
• Remove boilerplate comments that no longer add project value.
• Update any deprecated fields only after validating the exact supported schema.
• Consider pinning the GoReleaser action version input if reproducible release behavior is more important than automatically consuming the latest action default.

Acceptance criteria

• goreleaser check or the current equivalent passes locally.
• .goreleaser.yaml contains only project-relevant release configuration.
• Any schema migration is covered by a release workflow note or PR validation output.

[apstndb]

Resolved by #75. That PR removed the stock GoReleaser boilerplate and unused generate hook, migrated deprecated archive fields to the v2 schema, documented the release workflow behavior, and recorded a passing goreleaser check.

A separate GoReleaser binary version input was considered but not added. The workflow major-pins goreleaser-action@v6 while intentionally allowing its GoReleaser v2 resolution to float; there is no stricter reproducibility requirement today. Revisit if release reproducibility requirements change.