testing on the new images!

AGENTS.md

@@ -80,7 +80,7 @@ env:
 jobs:
   build:
     name: Build Image
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     steps:
       - uses: actions/checkout@v4
       - uses: https://git.ivanch.me/ivanch/pipeline-actions/build-and-push@main
@@ -91,7 +91,7 @@ jobs:
 
   deploy:
     name: Deploy (internal)
-    runs-on: ubuntu-amd64
+    runs-on: runner-slim-amd64
     needs: build
     steps:
       # Deployment specs live in the repo; apply them with kubectl-apply.
@@ -126,7 +126,7 @@ Consumer projects must set these secrets in Gitea repo settings (Settings → Ac
 - Pin composite action refs to `@main` until version tags are created.
 - Every job **must** have a `name:` field (e.g. `name: Build Image`, `name: Deploy (internal)`). Unnamed jobs render as their raw ID (`build`, `deploy`, …) in the Gitea Actions UI and run logs. The workflow template above includes `name:` on every job — copy it as-is.
 - Always use the full URL `https://git.ivanch.me/ivanch/pipeline-actions/<action>@main` for `uses:` — Gitea cannot resolve the bare GitHub-style `ivanch/pipeline-actions/...` path.
-- Always use `runs-on: ubuntu-amd64` (homelab Gitea runner label).
+- Default to `runs-on: runner-slim-amd64` (or `runner-slim-arm64`) as the default runner label. If further development/build binaries are required (or an Ubuntu-based environment is needed), use `runner-full-amd64` (or `runner-full-arm64`).
 - Always build `linux/amd64,linux/arm64` — the cluster has mixed arch (iris+vega=amd64, nebula+nexus=arm64).
 - Workflow files go in `.gitea/workflows/main.yaml` of the consuming project.
 - The consuming project must have a working `Dockerfile` at the repo root (or pass `build_dockerfile` input).