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/publish-gui-all.yml

@@ -58,7 +58,7 @@ jobs:
     # Retargeted arm64 self-hosted (spark, frequently offline) → the always-up
     # in-cluster amd64 ARC pool. @hanzogui/* are pure-JS; publishing is
     # arch-independent, so amd64 is safe and far more reliable.
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     if: github.event_name == 'push' || github.event.inputs.confirm == 'publish'
     steps:
       - uses: actions/checkout@v4

.hanzo/workflows/publish-gui.yml

@@ -30,7 +30,7 @@ jobs:
     name: Build, smoke-test, publish
     # Retargeted arm64 self-hosted (spark, frequently offline) → the always-up
     # in-cluster amd64 ARC pool. Pure-JS publish is arch-independent.
-    runs-on: [hanzo-build-linux-amd64]
+    runs-on: [linux-amd64]
     steps:
       - uses: actions/checkout@v4
         with:

hanzo.yml

@@ -4,7 +4,7 @@
 #
 # WHERE THIS RUNS: git.hanzo.ai, not github.com. `gh api
 # /orgs/hanzoai/actions/runners` returns total_count 0 — GitHub has no runner
-# that answers the `hanzo-build-linux-amd64` label the reusable asks for, so a
+# that answers the `linux-amd64` label the reusable asks for, so a
 # `.github/workflows/cicd.yml` would queue forever. Gitea collects workflows
 # from the FIRST of WORKFLOW_DIRS present in a commit, and `.hanzo/workflows`
 # wins, which is also why `.github/workflows` is dark on Hanzo Git.