docs: add Homebrew install for fff-mcp (#345)

[gustav-fff]

Closes #345

Root cause

Feature request, not a bug. Users wanted a familiar package-manager install path for fff-mcp instead of piping curl to bash.

Fix

Published a Homebrew tap at gustav-fff/homebrew-tap with fff-mcp.rb (formula adapted from @Aeron's tap, per maintainer instruction). Formula pulls the prebuilt binaries from the GitHub release assets of dmtrKovalenko/fff.nvim v0.8.1, with sha256 pins for darwin/linux × arm64/x86_64. README updated with one new section under MCP server install.

Steps to reproduce

Pre-fix main: no Homebrew install path documented; only curl script.

grep -i homebrew README.md  # no match on origin/main

How verified

brew install gustav-fff/tap/fff-mcp
which fff-mcp           # /opt/homebrew/Cellar/fff-mcp/0.8.1/bin/fff-mcp
fff-mcp --version       # fff-mcp 0.8.1 (6645a68ebc1f1a0dc98c1669a7e3f6d91625f79f)
fff-mcp --help          # prints usage

Tap installs cleanly on darwin-arm64. SHA256 values verified against *.sha256 sidecar files on the v0.8.1 release.

Notes for maintainer:

• Tap lives under bot account gustav-fff/homebrew-tap. If you want canonical ownership, fork it under dmtrKovalenko/homebrew-tap and swap the tap path in README — formula is portable.
• Formula targets fff-mcp only (the user-facing binary). The .dylib/.so/.dll artifacts for the Neovim plugin remain installed via the plugin's own download step — Homebrew is not the right channel for them.
• Version is hard-pinned to 0.8.1. Bumping requires updating version + 4 sha256 fields in the tap, ideally automated from the release workflow.

Automated triage via Gustav. Honk-Honk 🪿

[dmtrKovalenko]

@gustav-fff can we somehow make the version update automatically? does it make sense? should we update the formula tap on every release to make this happen or we can just use "latest as a version?

[gustav-fff]

[triage-bot] DIRECTED:

"latest" not viable. Homebrew formulas require pinned url + sha256 per arch — no latest redirect support, and unpinned tarballs break brew audit and reproducibility.

Two automation paths:

1. Release-workflow bump (recommended). Add job to .github/workflows/release.yaml that runs after assets upload: download the 4 *.sha256 sidecars, sed the new version + sha256 fields into fff-mcp.rb, push to gustav-fff/homebrew-tap via PAT. ~30 LOC of bash. Fully hands-off; tap always matches latest release.

2. brew bump-formula-pr GH Action. Use dawidd6/action-homebrew-bump-formula — opens PR against the tap on each release. Adds review step but lets you sanity-check before publish.

Recommend (1) since tap is bot-owned and fff-mcp release cadence is yours. Want me to wire it into release.yaml? Needs a HOMEBREW_TAP_TOKEN secret with write access to the tap repo.

Honk-Honk 🪿