Deploy to brick-host instead of cube-host

cube.local and brick.local swapped IPs and brick is now the deploy
target — rename the native runner label everywhere it's referenced.

docs/deployment.adoc

@@ -11,7 +11,7 @@ against the Gitea instance:
   `ubuntu-latest`/`ubuntu-24.04`/`ubuntu-22.04` — runs the `check` job
   in a fresh, isolated container per job, same as before.
 * A dedicated native runner, installed directly on the host (no Docker
-  around it), label `cube-host` — runs only the `deploy` job.
+  around it), label `brick-host` — runs only the `deploy` job.
 
 They're separate because the Docker-based runner's jobs (whether in
 its usual isolated per-job containers, or tried directly inside its
@@ -84,7 +84,7 @@ label:
 ----
 runner:
   labels:
-    - "cube-host"
+    - "brick-host"
 ----
 
 The `host` scheme means jobs run directly via the runner process's own
@@ -237,7 +237,7 @@ webhook simply won't receive that session; nothing breaks.
 == CI deploy job
 
 `.gitea/workflows/ci.yml`'s `deploy` job runs after `check` passes, only
-on a push to `main`, with `runs-on: cube-host`:
+on a push to `main`, with `runs-on: brick-host`:
 
 . Checks out the repo with plain `git` (`fetch` + `checkout`,
   authenticated via a one-off `http.extraHeader`) rather than