chore(main): release 0.2.0

[github-actions]

🤖 I have created a release beep boop

0.2.0 (2026-09-30)

⚠ BREAKING CHANGES

• module: importers must switch from github.com/godaddy/ans to github.com/agentnameservice/ans; the old import path no longer resolves against this repository.

Features

• ans-verify: verify attested metadata hashes against the served descriptor (#112) (3504947), closes #99
• finder: make the publisher host free-text searchable (#94) (d8ed4bb)
• ra: AI Catalog generation, FQDN exclusivity, and seal-before-success activation (#47) (daf5ba1)
• ra: default discovery profiles to ANS_DNSAID; real-DNS demo tooling (#89) (79fb0b9)
• ra: Implement ARD-compliant discovery service and event feed (#46) (9dbc5c1)

Bug Fixes

• dns: compare SVCB TargetName as effective target, not presentation string (#108) (f6a3fee)
• dns: match the HTTPS record by SvcParam subset, with alpn as a list (#116) (92b5760)
• dns: split alpn on the escape form that actually reaches the verifier (#118) (83875d0)
• module: move module path to github.com/agentnameservice/ans (#93) (93e5bf9)
• ra: attest only the DNS records verification actually found (#106) (2c4a1de)
• ra: emit v-prefixed ANSName version segment in TXT version= values (#71) (facb1ba), closes #69
• ra: seal the gate-verified ACME method into domainValidation (#75) (99152ec), closes #61
• release: let GoReleaser infer the GitHub owner/name (#67) (e51993f)
• tl: generate logId as UUIDv7 as documented (#72) (996586d)
• tl: read V1 cert-attestation arrays in status-token builder (#54) (974ca94)

Documentation

• adopt DCO and AI-disclosure contribution policy (#84) (f1daf35)
• fix stale comments (#87) (9383881)
• spec: state what receipts and checkpoints prove and how their tree sizes relate (#139) (425b44d)

---

This PR was generated with Release Please. See documentation.

[csnitker-godaddy]

One release-note correction: the ans-verify entry says #112 “closes #99,” but #112 implemented only the attested metadata-hash check.

It did not implement non-ANS verification, reachable/ANS-verified outputs, or the FQDN entry point. The scope decision is recorded in #99, and FQDN support is tracked separately in #120.

Please replace “closes #99” with “related to #99” in both the PR description and CHANGELOG.md, so the release notes accurately describe what shipped.