Drop the stale note about arming the build trigger

The warning dated from when .build-host was the release trigger's own setting
and push was a second consumer of it. One setting now names one machine for all
three commands, so there is nothing to keep separate -- and the advice was
wrong regardless: OMARCHY_REPO_HOST is read by the same resolver, so it arms
the trigger exactly as the file does. Only --host is per-invocation.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

README.md

@@ -213,11 +213,8 @@ need no secrets.
 The host comes from `--host`, `$OMARCHY_REPO_HOST`, then `.repo-host`. One
 machine both serves pkgs.omarchy.org and runs the scheduled builds, so the
 setting is named for the repository rather than for building, which happens
-wherever you like.
-
-Note that `.repo-host` also arms the automatic build trigger in
-`bin/omarchy-pkgs release`; pass `--host` or set `OMARCHY_REPO_HOST` to keep the
-two separate.
+wherever you like. The same setting tells `bin/omarchy-pkgs release` which host
+to poke after a release push.
 
 Split packages are selected by their own names, not their pkgbase — pushing
 `nvidia-580xx-utils` does not carry `nvidia-580xx-dkms` along. Omit `--package` to

helpers/host-helpers.sh

@@ -39,7 +39,4 @@ print_no_repo_host() {
   echo ""
   echo "Pass --host, set OMARCHY_REPO_HOST, or write the destination to:"
   echo "  $BUILD_ROOT/.repo-host"
-  echo ""
-  echo "That file also arms the automatic build trigger in 'bin/omarchy-pkgs"
-  echo "release'. Use --host or OMARCHY_REPO_HOST to keep them separate."
 }