Improve App Store Connect upload release evidence

[shiny-code-bot]

Objective

Make App Store Connect upload evidence first-class in the release process and remove the current naming confusion around the workflow currently called TestFlight.

Finish Line

Apple upload workflow summaries make uploaded version, build number, commit, destination, TestFlight beta opt-in state, and result obvious.

Current Status

State: Active
Next action: Add structured release summary output for App Store Connect uploads and clarify/rename TestFlight terminology.
Blocked by: None
Waiting for: None
Last verified: 2026-05-28, App Store Connect upload for version 1.0.11, build 202605281949, succeeded from main commit 97238144f569d3298b804a5814293e87f1a19aef through the workflow currently named TestFlight. Logs show Apple Distribution signing, MARKETING_VERSION=1.0.11, CURRENT_PROJECT_VERSION=202605281949, and Upload succeeded.

Scope

• In: Apple upload workflow summaries, artifact naming, upload evidence, TestFlight beta opt-in/default semantics, docs.
• Out: App Store review submission automation and App Store Connect metadata management.

Acceptance Criteria

• Workflow summary states version, build number, target SHA, upload/export mode, destination, and result.
• Summary makes clear whether TestFlight beta distribution was skipped or explicitly requested.
• Export/upload artifacts are named with version and build number.
• Failure cases point to the signing/profile/API category that failed when practical.
• Docs explain that App Store Connect upload is not the same as TestFlight beta testing or App Store review submission.
• The default Apple release path does not require a TestFlight beta step.

Relationships

Part of the release hardening parent plan.

Validation

• Run export-only mode and inspect artifact names/summary.
• Run upload mode when approved and inspect summary/log evidence.

Decisions

• 2026-05-28: App Store review submission remains manual/out of scope for this plan.
• 2026-05-28: TestFlight beta distribution should be opt-in, not the default release path, because it adds friction while Context Panel effectively has one user.

Open Questions

• Should the workflow query App Store Connect after upload to confirm processing/build visibility, or is upload success enough for the first pass?
• Should the current TestFlight workflow be renamed to App Store Connect Upload?