Fix docker proto cache with buf.lock

[casey-brooks]

Summary

• include buf.lock in the Docker build context to avoid stale proto stubs
• refresh buf.lock via buf dep update

Testing

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Fixes #31

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[noa-lucent]

Clean, minimal fix that directly addresses #31. Both changes are correct:

1. Dockerfile: Adding buf.lock to the COPY layer ensures BuildKit invalidates the RUN buf generate cache when proto dependencies change — exactly the missing cache-busting mechanism described in the issue.
2. buf.lock: Updated via buf dep update with the latest agynio/api commit that includes GetFileContent.

Verified that buf.lock is not excluded by .gitignore or .dockerignore. LGTM.

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[casey-brooks]

Test & Lint Summary

Commands

• buf generate buf.build/agynio/api --path agynio/api/files/v1
• go vet ./...
• go build ./...
• go test ./...

Tests: passed 1, failed 0, skipped 0

Lint: go vet ./... (no errors)

[noa-lucent]

Re-reviewed after significant updates (6 commits, 4 files). All changes are clean and well-motivated.

Dockerfile + buf.lock — Same as before, correctly addresses #31.

ci.yml — Good simplification. Removing the Docker build+push steps and GHCR login is the right call now that e2e no longer deploys a PR-specific image. Dropping packages: write permission follows least-privilege.

devspace.yaml — Solid rework of the e2e pipeline:

• Removed the deploy_pr_image function and the entire image-hot-swap approach — now uses DevSpace sync directly, which is simpler and eliminates the GHCR dependency in CI.
• Fixed deployment name files-files → files in patch_deployment.
• Pipeline renamed test:e2e → test-e2e (colons in DevSpace pipeline names are fragile).
• Proper trap-based cleanup with explicit cleanup on the success path and trap - EXIT to avoid double-cleanup.
• Separated buf generate and go test into distinct exec_container calls — better error attribution.
• Security context and resource limits added to e2e-runner deployment — good hardening.
• Label selectors updated to DevSpace defaults (devspace-app / e2e-runner component), consistent with the deployment config.
• noWatch: true on e2e sync is correct (one-shot sync for CI).
• No dangling references to removed functions or old names.

No issues found. LGTM.