fix(ci): the package-count assertion lives in two scripts and only one was updated

D29 removed byedpi, so the feed carries three packages. sdk-build-apk.sh was
changed to >=3; build-feed-apk.sh still demanded >=4 and killed both arch lanes
of v0.2.22 with `expected >=4 .apk … found 3`. Nothing was published from that
run. The comment now says the count is duplicated, because reading one script
was what made this look done.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BHw89tdWddzhjUc4bAH4tS

ci/build-feed-apk.sh

@@ -110,7 +110,12 @@ docker run --rm --volumes-from "$(hostname)" \
 # --- 2) sanity: the per-arch apk repo dir must be complete -------------------
 [ -s "$OUT/packages.adb" ] || { echo "[apk-feed] ERROR: $OUT/packages.adb missing/empty" >&2; exit 4; }
 apks=$(find "$OUT" -maxdepth 1 -name '*.apk' | wc -l)
-[ "$apks" -ge 4 ] || { echo "[apk-feed] ERROR: expected >=4 .apk in $OUT, found $apks" >&2; exit 5; }
+# Three, since D29 removed byedpi: shaterd, shater-core, luci-app-shater. The
+# count lives in TWO scripts — sdk-build-apk.sh asserts what it collected out of
+# bin/, this one asserts what reached the feed dir. v0.2.22 shipped with only the
+# first one updated and the aarch64 lane died here on `found 3`, so if the set of
+# packages ever changes again, change it in both.
+[ "$apks" -ge 3 ] || { echo "[apk-feed] ERROR: expected >=3 .apk in $OUT, found $apks" >&2; exit 5; }
 if [ -n "${KEY_APK:-}" ] && [ ! -s "$OUT/shater-apk.pem" ]; then
   echo "[apk-feed] ERROR: signed feed but shater-apk.pem missing from $OUT" >&2; exit 6
 fi