f6446c25156e442df2e4733975afaf5c7ba09bbf
The step ran `sudo k3s ctr images pull` / `ctr run` against the host's containerd. That worked when the runner was the Arch host; since it was containerized (infra#233) the image has no sudo, no ctr and no containerd socket, so the step fails with `sudo: command not found`. It only surfaced now because the buildah wall (infra#241) killed the job before this step ever ran. The deploy job's `Verify rollout` and `Confirm pod running new image` assert the same property against the real workload rather than a 5s throwaway container, which is why tapir dropped its smoke test under the same issue. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011PL5XcG68SvQqz3vGVbWbf
gitea-mcp
Streamable HTTP MCP service exposing Gitea repo operations to Claude apps.
See ~/dev/AI/infra/docs/superpowers/specs/2026-05-04-gitea-mcp-gitops-workflow-design.md.
Quickstart
task setup:hooks # installs .githooks/pre-push — runs task check before every push
task check # context sync + lint + test + vet
task build # produces bin/gitea-mcp
This repo uses Trunk-Based Development. Commit directly to main. The pre-push
hook enforces the quality gate locally; CI re-runs task check on every push.
Languages
Go
97.9%
Shell
1.9%
Dockerfile
0.2%