ci: re-enable actions cache now that the runner serves it

The Gitea Actions cache service now answers on 10.200.0.1:43513
(post nftables fix on the runner side). Turn `cache: true` and
`cache: pnpm` back on so setup-go/setup-node can use it for
cross-job tarball caching on top of the host-persistent caches we
already rely on.

The setup-* actions still tolerate the cache being unavailable, so
this is reversible to `cache: false` if the service goes away again.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.gitea/workflows/dev-deploy.yaml

@@ -40,8 +40,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: true
-          cache: false
 
       - name: Set up pnpm
         uses: pnpm/action-setup@v4
@@ -52,11 +51,8 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          # `cache: pnpm` pushes the pnpm store through the Gitea
+          cache: pnpm
-          # Actions cache service which is currently unreachable
+          cache-dependency-path: ui/pnpm-lock.yaml
-          # (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
-          # store lives in ~/.local/share/pnpm and persists between
-          # jobs without any action plumbing.
 
       - name: Install UI dependencies
         working-directory: ui

.gitea/workflows/go-unit.yaml

@@ -46,13 +46,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          # `cache: true` here pushes/pulls archives through the Gitea
+          cache: true
-          # Actions cache service at 192.168.0.222:43513. That endpoint
-          # currently does not answer, and the action wastes minutes
-          # per run on reserveCache retries. In host-mode the real
-          # caches live in $HOME (~/go/pkg/mod, ~/.cache/go-build) and
-          # persist between jobs without any actions/cache plumbing.
-          cache: false
 
       - name: Run Go tests
         # client/ is the deprecated Fyne client; excluded from CI per

.gitea/workflows/integration.yaml

@@ -53,8 +53,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: true
-          cache: false
 
       - name: Run integration suite
         # `make integration` precleans leftover docker-compose state and

.gitea/workflows/prod-build.yaml

@@ -37,8 +37,7 @@ jobs:
         uses: actions/setup-go@v5
         with:
           go-version-file: go.work
-          # See go-unit.yaml for why `cache: true` is disabled.
+          cache: true
-          cache: false
 
       - name: Set up pnpm
         uses: pnpm/action-setup@v4
@@ -49,7 +48,8 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          # See dev-deploy.yaml for why `cache: pnpm` is disabled.
+          cache: pnpm
+          cache-dependency-path: ui/pnpm-lock.yaml
 
       - name: Resolve image tag
         id: tag

.gitea/workflows/ui-test.yaml

@@ -37,11 +37,8 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: 22
-          # `cache: pnpm` pushes the pnpm store through the Gitea
+          cache: pnpm
-          # Actions cache service which is currently unreachable
+          cache-dependency-path: ui/pnpm-lock.yaml
-          # (192.168.0.222:43513 ETIMEDOUT). In host-mode the real
-          # store lives in ~/.local/share/pnpm and persists between
-          # jobs without any action plumbing.
 
       - name: Install npm dependencies
         working-directory: ui