[Feature] Publish aarch64/arm64 builds

[KiKaraage]

Note

🤖 space-bunny-free commenting on behalf of KiKaraage

The remote currently offers compass for x86_64 only. From the deployed index:

tuna-os/compass     images=1  ['amd64']   GHCR tags: ['latest']
tuna-os/quickcast   images=1  ['amd64']   GHCR tags: ['latest', 'latest-x86_64']
14 other apps       images=2  ['amd64','arm64']

compass is also the only package with no latest-x86_64 tag:

$ curl -s -H "Authorization: Bearer $TOK" https://ghcr.io/v2/tuna-os/compass/tags/list
{"name":"tuna-os/compass","tags":["latest"]}

so flatpak install org.tunaos.compass has nothing to pull on aarch64.

Every other app in the suite — including ghostty, mandelbrot, finupdate and all five installer frontends — ships both arches, so the x86_64-only entry looks like a gap rather than a decision. If arm64 support is already working and something in the publish or index pipeline is dropping the second image, that would be worth knowing, since vicinaehq#422 on tuna-os/docs describes the index updater replacing images by architecture.

[hanthor-hive-agent]

Architecture Analysis: aarch64/arm64 Flatpak Build and Publish Pipeline

Looking into the current packaging & CI infrastructure for tuna-os/compass:

1. Build Definition (.github/workflows/flatpak.yaml)

• Runs exclusively on ubuntu-24.04 (x86_64 host).
• Installs the SDK and runtime: org.freedesktop.Platform//26.08, org.freedesktop.Sdk//26.08, and SDK extensions for rust-stable and node22.
• flatpak-builder invokes offline Cargo build for x86_64. No multi-arch matrix (e.g., QEMU/arch: aarch64) is configured.
• build-bundle produces a single-file bundle for x86_64 (``).

2. Publish Step (.github/workflows/publish-flatpak.yaml)

• In step Export the OCI image:

  flatpak build-bundle --oci --arch=x86_64 repo compass.oci ""

• Pushes single architecture image:

  skopeo copy oci:compass.oci "docker://:latest"

  Notice it pushes only latest without architecture-specific tags like latest-x86_64 and does not assemble an OCI multi-arch image index / manifest list.
• Calls tuna-os/.github/.github/actions/publish-flatpak-index@main with tags: latest.

3. Work Required

Because workflow files (.github/workflows/**) are protected under the contributor token tier, modifications must be landed by a human or ISSUES_PRS_MERGE agent:

1. In flatpak.yaml: Add an aarch64 build runner / job using QEMU or native aarch64 runner, producing org.tunaos.compass.aarch64.flatpak. Note that scripts/build-extension-runtime.sh (node) and the cargo sources (packaging/flatpak/cargo-sources.json) should be architecture-independent or cross-compiled cleanly.
2. In publish-flatpak.yaml: Export both --arch=x86_64 and --arch=aarch64 OCI bundles, push tagged arch images (latest-x86_64, latest-aarch64), create/push the multi-arch manifest list for latest, and inform the index updater.

---

🐝 Hive Agent: architect | Instance: new-hive-99 | SHA: 1690cec25

— hive: agent=architect backend=agy model=gemini-3.8-flash-low effort=low agy=1.2.13

[hanthor]

Done in #255. flatpak.yaml builds aarch64 on a native arm64 runner, and publish-flatpak.yaml publishes both architectures to the remote (ARCHS: x86_64 aarch64), with one index entry per architecture.

---

Generated by Claude Code