Rename Homebrew tap repo to homebrew-tap for a cleaner one-command install

[groksrc]

Current state

Our Homebrew install is documented as a multi-step:

brew tap basicmachines-co/basic-memory
brew trust basicmachines-co/basic-memory   # Homebrew 5.1+; required in 6.0
brew install basic-memory

None of that is necessary. Homebrew's fully-qualified form auto-taps and records per-formula trust in one shot (per the Tap Trust docs: "Installing a fully-qualified formula or cask name trusts only that item"). But because the tap repo is named homebrew-basic-memory and the formula inside is also basic-memory, the one-liner stutters:

brew install basicmachines-co/basic-memory/basic-memory

Proposal (v1.0)

Rename the tap repo homebrew-basic-memory → homebrew-tap, following the common single-tap convention (hashicorp/tap/terraform, goreleaser/tap/goreleaser), so the install becomes:

brew install basicmachines-co/tap/basic-memory

Migration checklist

• Rename the GitHub repo (GitHub redirects the old name, so existing users' taps keep fetching)
• Update the Homebrew bump step in .github/workflows/release.yml to target the renamed repo
• Update install docs on docs.basicmemory.com (quickstart-local, local-install) to the new one-liner
• Update README / release runbook (.claude/commands/release/release.md) install references
• Update formula caveats (trust hint becomes brew trust basicmachines-co/tap)
• Release notes: tell existing users they can stay on the old tap name (redirect keeps working) or re-tap; short-name brew install basic-memory users should brew trust once before Homebrew 6

Why v1.0

Cosmetic rename with real churn (docs, workflow, user-facing name), so it batches naturally with the v1.0 surface cleanup. Cheapest to do while the Homebrew user base is small.

[claude]

Claude finished @groksrc's task in 1m 19s —— View job

---

Issue Triage

• Analyze issue
• Classify type, priority, component, complexity
• Check for duplicate issues
• Apply labels
• Provide triage summary

---

Triage Summary

No duplicates found. This is a standalone request.

Classification:

Dimension	Assessment
Type	Enhancement — UX improvement to the install flow
Priority	Low — cosmetic change, no functionality is broken, author explicitly batches it with v1.0
Components	ci (release workflow), docs (README, install docs, release runbook)
Complexity	Medium — touches multiple systems (GitHub repo rename, release workflow, external docs site, formula caveats) but each individual step is straightforward

Labels applied: enhancement, documentation

---

Analysis

The proposal is well-scoped and the migration checklist is complete. A few notes for the implementer:

1. GitHub repo rename — this is the one step that requires manual action by a repo admin via the GitHub UI (Settings → Rename). GitHub auto-redirects the old name, so existing users' brew tap basicmachines-co/basic-memory will keep working.

2. .github/workflows/release.yml — the Homebrew bump step that pushes the updated formula to the tap repo will need to target homebrew-tap instead of homebrew-basic-memory. This is a one-line change.

3. Docs and README — install snippets on docs.basicmemory.com (quickstart-local, local-install pages) and the README need to be updated to brew install basicmachines-co/tap/basic-memory. The formula caveat should also update the trust hint from brew trust basicmachines-co/basic-memory → brew trust basicmachines-co/tap.

4. Release runbook (.claude/commands/release/release.md) — any install references there should also be updated.

5. Migration note for existing users — worth adding a one-liner in the next release notes: users already on the old tap name don't need to do anything (redirect keeps working); short-name brew install basic-memory users should run brew trust once before Homebrew 6.

The author's v1.0 milestone timing makes sense — cheapest to do while the Homebrew user base is small.