fix: threads v0.1.1 image missing arm64 platform

[rowan-stein]

User Request

After applying the latest bootstrap, threads and chat fail to start with:

rpc error: code = NotFound desc = failed to pull and unpack image "ghcr.io/agynio/threads:v0.1.1": no match for platform in manifest: not found

Chat depends on threads, so both services are broken.

Root Cause

The v0.1.1 release was built from commit ee5fba4, which used the old release.yml workflow:

1. Missing docker/setup-qemu-action — no arm64 emulation available on the runner.
2. Missing platforms: linux/amd64,linux/arm64 in docker/build-push-action — only the runner's native amd64 was built.
3. CI logs confirm the builder only had linux/amd64 variants; no arm64 manifest entry was created.

The current main branch (5959888) already has the corrected workflow with QEMU setup and multi-platform builds matching the CI/CD architecture spec.

Specification

• No code or workflow changes are needed — main already has the fix.
• Tag a new release v0.1.2 from current main to trigger the corrected release workflow.
• After the release, verify the new image manifest includes both linux/amd64 and linux/arm64.
• Update bootstrap to reference threads_chart_version = "0.1.2" so the correct multi-arch image is deployed.

[rowan-stein]

Update: Helm Chart Lint Failure

The v0.1.2 container image was successfully built with both linux/amd64 and linux/arm64 ✅

However, the Helm chart publish step failed due to a lint error:

[ERROR] templates/service-base.yaml: unable to parse YAML: error converting YAML to JSON: yaml: line 10: did not find expected key

This is a pre-existing issue — the old release workflow at v0.1.1 skipped helm lint and helm dependency build, so the chart was never validated before.

Immediate Fix (bootstrap)

Since the chart 0.1.1 already exists and the only problem is the container image architecture, the bootstrap fix is:

• Keep threads_chart_version = "0.1.1" (existing published chart)
• Set threads_image_tag = "v0.1.2" (new multi-arch image)

Follow-up

The Helm chart lint issue in service-base.yaml should be fixed separately so future releases publish both image and chart correctly.