Reverts the move to `infra`. Verified on a fedora-43 runner that the ssh
reachability check ran fine (it added the host key and connected) — the
earlier deploy failure was the unprovisioned remote sudo step, not a missing
ssh client. Every runner has ssh: `git` (installed for checkout) pulls
`git-core`, which hard-requires `openssh-clients`. So fedora-43 (ssh + rsync +
curl) is the right, lighter runner for these deploy jobs.
See architecture gitea-runners.md.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
Run #2 exposed two runner-mismatch bugs (now documented in architecture
gitea-runners.md):
- build-web failed with `corepack: command not found` — the fedora runners
ship pnpm preinstalled via npm, not corepack. Call pnpm directly.
- deploy jobs need an ssh client, which the base fedora images lack (they have
rsync but not openssh-clients). Move deploy-api/deploy-web to `runs-on: infra`.
build-api already passes on `runs-on: rust`.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
The first run failed with `cargo: command not found` — `runs-on: fedora-43`
is the generic (node) runner, not the Rust toolchain. Split the build:
Rust on `runs-on: rust`, the SPA on `fedora-43` (matching the fleet's
existing conventions, cf. cichlid/helexa workflows).
Also drop the musl static-cross build: the entire fleet is Fedora 43, so
native binaries built on the `rust` runner run on the targets without glibc
skew (deployment-gitea-actions.md §6 permits building on a runner no newer
than the oldest target). Removes the unverifiable musl-toolchain dependency.
Pin pnpm via packageManager so corepack resolves it deterministically.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
