ci: keep npm and Next compile caches across image builds

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

.gitea/workflows/ci.yml

@@ -79,9 +79,6 @@ jobs:
       - id: plano
         run: scripts/plano-imagem.sh "$REGISTRY" "${{ gitea.repository }}" >> "$GITHUB_OUTPUT"
 
-      - if: ${{ steps.plano.outputs.reuse != 'true' }}
-        uses: docker/setup-buildx-action@v4
-
       - if: ${{ steps.plano.outputs.reuse != 'true' }}
         uses: docker/login-action@v4
         with:
@@ -89,16 +86,12 @@ jobs:
           username: ${{ gitea.actor }}
           password: ${{ secrets.REGISTRY_TOKEN }}
 
+      # `docker build` simples, no daemon persistente do runner: as camadas e os
+      # cache mounts do Dockerfile (npm e compilação do Next) sobrevivem entre
+      # execuções. Um buildx criaria um BuildKit novo, e vazio, a cada job.
       - name: Build
         if: ${{ steps.plano.outputs.reuse != 'true' }}
-        uses: docker/build-push-action@v7
-        with:
-          context: .
-          platforms: linux/arm64
-          load: true
-          tags: espdocs:ci
-          cache-from: type=registry,ref=${{ steps.plano.outputs.image }}:buildcache
-          cache-to: type=registry,ref=${{ steps.plano.outputs.image }}:buildcache,mode=max
+        run: docker build -t espdocs:ci .
 
       - name: Trivy na imagem
         if: ${{ steps.plano.outputs.reuse != 'true' }}