docs(release): describe a formula that lands without a bottle

[brettdavies]

Summary

The release documents describe what the tap does with an anc release: it installs and tests the agentnative formula from the archives the release publishes, on four platforms, and lands the bump as one commit with no bottle. They described a bottle build, a bottle upload back to this repository's release, and a bottle attestation check.

• RELEASES.md and RELEASES-RATIONALE.md: what the tap does with a release, and why the GitHub Release stays not-latest until the formula lands. The Homebrew rollback reverts one commit; a release published with a bottle (0.6.0 and earlier) has a second.
• RELEASES-POSTFLIGHT.md: the tap workflow is Publish formula, the Homebrew gate checks an archive install, and the brew verify gate is gone because it reads bottles. The archive attestation gate is unchanged.
• README.md: the Homebrew paragraph says the formula installs the release archive by checksum, and links the tap's "Verifying an archive".
• scripts/SYNCS.md: the tap downloads and verifies the release's archives and uploads nothing back.
• The header comments of release.yml and finalize-release.yml give the pipeline as it runs, and name the build job as the one place a release compiles its binaries.

Changelog

Documentation

• Document that the Homebrew formula installs the release's archive directly, with no bottle, and where to verify an archive against its attestation.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• refactor: Code refactoring (no functional changes)
• perf: Performance improvement
• docs: Documentation update
• test: Adding or updating tests
• chore: Maintenance tasks (dependencies, config, etc.)
• ci: CI/CD configuration changes
• style: Code style/formatting changes
• build: Build system changes
• BREAKING CHANGE: Breaking API change (requires major version bump)

Related Issues/Stories

• Story: n/a
• Issue: n/a
• Architecture: RELEASES-RATIONALE.md § Why make_latest: false then finalize-release
• Related PRs: ci(release): build the release matrix once, at the tag #174 is the branch this one is based on. feat(ci): test a prebuilt-archive formula without building a bottle homebrew-tap#153, ci(rulesets): require CI on dev and three more checks on main #157, and #158 make the tap behave as these documents say, so the tap's change reaches its main before the release that carries these documents. chore(release): take the postflight tap gate from the template #175 brings the postflight gate that knows the Publish formula name.

Testing

• Unit tests added/updated
• Integration tests added/updated
• Manual testing completed
• All tests passing

Test Summary:

• Documentation and workflow comments only. markdownlint-cli2 and actionlint are clean on the changed files.

Files Modified

Modified:

• RELEASES.md, RELEASES-RATIONALE.md, RELEASES-POSTFLIGHT.md
• README.md
• scripts/SYNCS.md
• .github/workflows/release.yml, .github/workflows/finalize-release.yml: header comments only.

Created:

• None.

Renamed:

• None.

Deleted:

• None.