Publish Releases for app-v* tags in build workflow

[Copilot]

The release job only ran for v* tags. This repo's tags look like app-v0.2.64-71, so Actions builds finished without publishing a Release, and the Windows ZIPs only ever showed up as 14-day Artifacts.

• Trigger: on.push.tags now includes app-v*.
• Release gate: the release job's if accepts refs starting with refs/tags/v or refs/tags/app-v.

on:
  push:
    tags: ['v*', 'app-v*']
...
  release:
    if: >
      ...
      (startsWith(github.ref, 'refs/tags/v') || startsWith(github.ref, 'refs/tags/app-v'))

The asset collection, notes generation and stale-asset cleanup steps are unchanged. Windows ZIPs are published through those existing steps.

• The release is still gated on Android, Windows and iOS all succeeding. A failure in any one of them still skips publishing.
• Pushing a new app-v* tag triggers the new path. The existing app-v0.2.64-71 tag won't re-run by itself.

[Copilot]

Copilot review overview

🟢 Approval recommended

The trigger and release condition are consistently updated without changing existing release safeguards.

Review effort: Balanced
Findings: None

What changed in this PR

Extends the build workflow to publish releases for the repository’s app-v* tag format.

Changes:

• Triggers builds for app-v* tags.
• Allows successful tagged builds to enter the existing release job.

File	Description
.github/​workflows/​build.yml	Adds app-v* support to the trigger and release gate.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.