ci(release): migrate Gitcrawl to shared pipeline

[steipete]

Summary

• make release-unified.yml the only official Gitcrawl release path through openclaw/release-workflows@v1
• preserve checksums.txt, all six thin platform archive names, the four established archive members, org.openclaw.gitcrawl, SSH-signed tags, event-scoped CI evidence, and the existing Homebrew token/tap
• retire the old draft verifier and tag-snapshot release workflows, remove the obsolete GoReleaser signing hook, and make local packaging aliases refuse with the exact unified command

Asset diff

No published asset disappears or is renamed.

Unchanged:

• checksums.txt
• Darwin/Linux amd64+arm64 .tar.gz archives
• Windows amd64+arm64 .zip archives
• CHANGELOG.md, LICENSE, README.md, and the Gitcrawl executable inside every archive

Additive verifier controls: ASSET-INVENTORY.json, SIGNING-MANIFEST.json, and RELEASE-NOTES.md.

Proof

• make check: tidy, format, vet, govulncheck, deadcode, 85.1% coverage, CLI smoke, release-script tests, and six-target GoReleaser snapshot all green
• actionlint .github/workflows/*.yml
• goreleaser check
• snapshot Windows archives remain .zip; Linux and Windows archive members match the current public contract
• local make release refuses and prints gh workflow run release-unified.yml --repo openclaw/gitcrawl -f version=X.Y.Z
• autoreview's only finding was rejected as stale: remote v1 peels to f2fd4f2040e5e5885b7678b4f1cc43e60cbc18b5, declares every configured input, and Discrawl run 30253337453 exercised the same contract through publication and Homebrew

[clawsweeper]

ClawSweeper status: review started.

I am starting a fresh review of this pull request: ci(release): migrate Gitcrawl to shared pipeline This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.