Release build fails after org threads changes: missing generated authorization protos

[rowan-stein]

User request

Unblock delivery of org-scoped Threads feature (console-app#67) by producing a releasable threads service chart containing merged org threads RPCs (threads#22).

Currently, tagging v0.4.7 fails the release workflow, so bootstrap cannot be bumped off threads_chart_version=0.4.6 and console-app e2e remains broken.

Specification (from research)

Observed failure

• Release workflow run: https://github.com/agynio/threads/actions/runs/24628800756 (tag v0.4.7)
• Docker build fails at go build ./cmd/threads with:
  • cmd/threads/main.go:14:2: no required module provides package github.com/agynio/threads/.gen/go/agynio/api/authorization/v1

Root cause

• Merged changes (threads#22) introduce usage of Authorization API stubs (.gen/go/agynio/api/authorization/v1).
• The Dockerfile runs buf generate buf.build/agynio/api with a restricted --path list that omits agynio/api/authorization/v1, so those stubs are never generated during image build.
• CI’s buf generate path list already includes agynio/api/authorization/v1, which is why CI can pass while release fails.

Required fix

1. Update the Dockerfile buf generate invocation to include:
   • --path agynio/api/authorization/v1
2. Preferably keep the Dockerfile buf generate path list aligned with the CI workflow to prevent drift.

Validation

• Confirm the Docker image build succeeds (equivalent to the release workflow’s build step).

Release follow-up

• After the fix is merged, cut a new patch tag (recommended: v0.4.8) to publish the chart/image.