CI: per-project path-filtered workflows + per-platform releases

[patrickrb]

Why

The repo holds three FT8 clients that share one C DSP core (ft8af/app/src/main/cpp/), but all CI was Android-only and fired on every push/PR with no path filtering. An iOS-only change still ran the full Android NDK build, and iOS/desktop had no CI at all. Releases were Android-only.

What changed

Split into per-project pipelines that only run when their files — or the shared C core — change:

Workflow	Trigger scope	Does
android.yml (renamed from build-release.yml)	ft8af/** or shared core	unit+coverage, instrumented, folds in static analysis, signed APK/AAB + GitHub Release + Play publish. All prior behavior preserved (NDK retry, signing, tag derivation, play-publish concurrency); job names test/instrumented/build unchanged.
ios.yml (new)	ios/** or shared core	swift test on FT8AFKit + unsigned iOS-Simulator build (xcodegen generate → xcodebuild) on macos-14. No release (needs Apple signing).
desktop.yml (new)	desktop/** or shared core	Tauri compile-check on Windows/macOS/Linux for PRs; on main/desktop-v* builds native bundles on all three OSes and publishes a namespaced desktop-v* / desktop-dev-N release via tauri-action.

native-tests.yml stays always-on as the shared-core golden gate. main-gate.yml and the discord workflows are untouched. static-analysis.yml was deleted (merged into android.yml).

Behavior model

• PR → only the affected project's checks (+ always: native golden tests, main-gate).
• push dev → only affected platform(s) build + publish a prerelease (dev-N / desktop-dev-N).
• push main → all platforms build, one release each (v* Android+Play, desktop-v*); iOS = verify only.
• tag v* → Android production release (unchanged). tag desktop-v* → desktop production release.

"Affected" = project's own paths or the shared C core changed.

⚠️ Required: update branch protection after merge

Path-filtered jobs can be skipped, and a skipped required check leaves branch protection stuck "pending" (already noted in native-tests.yml). Each workflow ends with an always-run aggregator that is the intended required check. In Settings → Branches → main (and dev if protected):

• Add required checks: android-gate, ios-gate, desktop-gate
• Keep: FT8 encode/hash golden vectors, enforce-source-is-dev
• Remove direct requirements on Unit tests & coverage / Build APK (now reached via android-gate)

Verification

• actionlint clean on all workflows (locally).
• Routing to confirm on first runs: an ios/-only change runs only iOS (android/desktop gates still green via all-skipped); a desktop/-only change runs only desktop; a ft8af/app/src/main/cpp/** change runs all three.

Notes / risks

• Android keeps bare v* tags (drives Play + version history); only desktop is namespaced — this is the "separate release per platform" layout requested.
• macOS/Linux desktop bundle legs may surface portability gaps (e.g. vendored Hamlib is Windows-only DLLs) on first run — that's expected feedback, not a regression introduced here.
• iOS produces no installable until Apple cert + provisioning are added as secrets; the chosen scope (tests + simulator build) needs neither.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 11.18%. Comparing base (05394ec) to head (5fe2f4e).
⚠️ Report is 13 commits behind head on dev.

Additional details and impacted files

@@             Coverage Diff              @@
##                dev     #296      +/-   ##
============================================
+ Coverage     11.15%   11.18%   +0.02%     
  Complexity      105      105              
============================================
  Files            81       81              
  Lines         11426    11430       +4     
  Branches       2051     2052       +1     
============================================
+ Hits           1275     1278       +3     
- Misses        10023    10024       +1     
  Partials        128      128              

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR restructures CI for the repo’s multi-client layout by splitting Android/iOS/desktop into separate, path-filtered workflows (including the shared C DSP core) and introducing per-platform release behavior (Android v*, desktop desktop-v*, iOS verify-only).

Changes:

• Replaced the monolithic Android-only CI triggering with per-project change detection and “always-run” gate jobs intended for branch protection (android-gate, ios-gate, desktop-gate).
• Added new iOS workflow to run swift test for FT8AFKit and perform an unsigned iOS Simulator build on macOS.
• Added new desktop workflow to compile-check on PRs and build/publish Tauri bundles on main pushes and desktop-v* tags; removed standalone static-analysis.yml by folding it into android.yml.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/android.yml	Adds Android path detection, folds static analysis into Android CI, and introduces android-gate as a branch-protection-friendly aggregator.
.github/workflows/ios.yml	Introduces path-filtered iOS verification (Swift package tests + simulator build) with an always-run ios-gate.
.github/workflows/desktop.yml	Introduces path-filtered desktop CI and release publishing via Tauri across Windows/macOS/Linux with an always-run desktop-gate.
.github/workflows/static-analysis.yml	Deleted in favor of embedding lint/detekt/ktlint into android.yml.

Comments suppressed due to low confidence (1)

.github/workflows/android.yml:585

• android-gate doesn't depend on detect, so if detect fails, test/build can be skipped and the gate still reports success. Since android-gate is intended to be the required check, it should fail on a failed/cancelled detect as well.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.