ci: a runner label names the platform, not the org

hanzo-build-linux-amd64, lux-build-linux-amd64, zoo-build-linux-amd64 and
every other org-prefixed spelling all meant the same machine. Which org a
job belongs to does not change which host can build it, so the org bought
one pool name per org per arch and each could go stale on its own -- the
evo host alone answered to fourteen names for one label.

One vocabulary now: linux-amd64, linux-arm64, macos-arm64, win-amd64. The
generic labels every plain workflow uses (ubuntu-latest, self-hosted) are
untouched, so naive CI keeps working.

Co-authored-by: Hanzo Dev <[email protected]>

.hanzo/workflows/deploy.yml

@@ -1,5 +1,5 @@
 # speech — build the image. Same lane as billing: git.hanzo.ai push → act_runner
-# (hanzo-build-linux-amd64) → docker build → ghcr.io/hanzoai/speech:<semver>.
+# (linux-amd64) → docker build → ghcr.io/hanzoai/speech:<semver>.
 #
 # SEMVER, NEVER SHA. The version is pyproject's, and a published tag is never
 # overwritten — two digests behind one name is the fleet's oldest trap.
@@ -15,7 +15,7 @@ concurrency:
 
 jobs:
   build:
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     steps:
       - uses: actions/checkout@v4