Leave Hyprland and rebuild detection to their own changes

PR builds link against published edge, so a Hyprland bump in the same merge
cannot see the carry, and as a fast-ring package it would reach every aarch64
channel. The rebuild detection fix that bumps it once the carry publishes
moves to its own PR, so this change only adds the aquamarine carry.

helpers/paths.sh

@@ -43,20 +43,6 @@ reference_arch() {
   published_arches | head -1
 }
 
-# Architectures a merge to master builds and publishes: bin/build-matrix plans
-# a PR build for each one a package supports, and publish.yml ships them. This
-# is independent of PUBLISHED_ARCHES, so anything deciding what a merge has to
-# rebuild (bin/sync-rebuilds) follows this list. CI_ARCHES overrides it.
-CI_ARCHES="${CI_ARCHES:-x86_64 aarch64}"
-
-ci_arches() {
-  local arch
-  for arch in $CI_ARCHES; do
-    require_valid_arch "$arch"
-    echo "$arch"
-  done
-}
-
 # Scheduled-pipeline state, one file per channel and architecture, so one
 # architecture's queue or backoff never gates another's.
 STATE_DIR="${OMARCHY_STATE_DIR:-/root/.state}"