diff --git a/deploy/tap/README.md b/deploy/tap/README.md
index cc6122b..24985b3 100644
--- a/deploy/tap/README.md
+++ b/deploy/tap/README.md
@@ -26,18 +26,14 @@ a `quest.atmo.connection` record — no `/repos/add` calls needed.
 
 ## Deploying
 
-Redeploys go through one **manual** Tangled pipeline:
-[deploy-tap.yml](../../.tangled/workflows/deploy-tap.yml). Trigger it from the
-repo's Pipelines page (any branch — `manual` ignores the branch filter). It
-just runs `flyctl deploy` from this directory, so it needs `FLY_API_TOKEN` in
-the repo's Tangled settings → secrets.
+Redeploys run on merge/push to `main` via
+[deploy-tap.yml](../../.tangled/workflows/deploy-tap.yml), alongside the main
+`atmoquest` deploy. It just runs `flyctl deploy` from this directory, so it
+needs `FLY_API_TOKEN` in the repo's Tangled settings → secrets. A version bump
+takes effect by editing `INDIGO_VERSION` in the Dockerfile and merging to main.
 
 Equivalently, by hand: `( cd deploy/tap && flyctl deploy --remote-only )`.
 
-Tap rarely changes, so it is intentionally **not** part of the per-push
-`atmoquest` deploy — redeploy via the pipeline when you bump the indigo/Tap
-version in the Dockerfile.
-
 ## Keeping versions in sync
 
 `deploy/tap/Dockerfile`'s `INDIGO_VERSION` **must** match the