From bd20469df92d1d666e31ce4c160ca5861836bc27 Mon Sep 17 00:00:00 2001
From: HeapSmasher <98077186+las7@users.noreply.github.com>
Date: Thu, 13 Aug 2026 20:57:07 +0000
Subject: [PATCH] README: install the formula, not the cask
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

The tap ships reachpad as a Homebrew formula now (Reachpad/homebrew-tap#1),
because a cask stages its files with com.apple.quarantine and macOS then
refuses to run our un-notarized binary. `brew install --cask` stops
resolving once that lands.

README.md is repo-local — assemble-cli-repo.sh preserves it — so this is
not overwritten by the next source sync. The matching change to what the
CLI itself prints belongs in the private repo.

Greentree-Change-Id: 3f07ab69d223355dec2271282297e7b6
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index decd0ca..9965bb4 100644
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ machine underneath, so a paused workspace resumes mid-session.
 With Homebrew on Apple silicon macOS or x86_64/arm64 Linux:
 
 ```sh
-brew install --cask reachpad/tap/reachpad
+brew install reachpad/tap/reachpad
 ```
 
 Or with the checksum-verifying installer:
@@ -60,7 +60,7 @@ reachpad completions fish
 ```
 
 `reachpad update` respects how Reachpad was installed: Homebrew installs are
-directed to `brew upgrade --cask reachpad`, while installer-managed binaries
+directed to `brew upgrade reachpad`, while installer-managed binaries
 are updated in place after the release checksum is verified.
 
 Docs: [reachpad.dev/docs/cli](https://reachpad.dev/docs/cli)