Improve release automation after PR merge

[zachyzissou]

Problem

After PRs merge, the app can be left in a confusing state if Xcode Cloud fails or uploads a build that is not assigned to testers. We need reliable post-merge automation.

Acceptance criteria

• After merge, monitor the exact Xcode Cloud run for the merge commit.
• If Archive fails, inspect and file/fix the concrete failure.
• If a build uploads, verify processing, beta state, and group assignment.
• If latest uploaded build is unassigned, either assign it automatically where allowed or report the exact blocker.
• Report the visible TestFlight build number, not just the latest uploaded build number.

Agent execution contract

Readiness: agent:senior-required
Lane: Release automation

Start in these files:

• scripts/app_store_connect.py
• ci_scripts/*
• CONTRIBUTING.md
• docs/*

Required verification:

• Run relevant App Store Connect script commands with current ASC credentials.
• Confirm exact Xcode Cloud run and TestFlight visibility state.

Non-goals / guardrails:

• Do not auto-assign external testers or alter release workflow without owner approval.
• Do not claim upload equals tester visibility.

PR expectation: Senior release automation PR with live ASC evidence.

Low-thinking agents must follow docs/AGENT_EXECUTION_RUNBOOK.md. If the touched code falls outside the files above, stop and tighten the issue or ask for senior review before continuing.

[zachyzissou]

Status: senior-required, release-tooling cluster

This issue plus #104, #117, #121 (and tangentially #38) are really one piece of work: "make release/build visibility honest, automated, and recoverable." All four require ASC API key access and authority to mutate Xcode Cloud workflow configuration.

These can't move without owner action; consider grouping them into a single milestone ("Release Lane") and tackling them together in one focused session.

Discovered while reviewing the kanban post-session 2026-04-30.