Local Archive, Export, Upload

The manual escape hatch for getting a build to TestFlight when Xcode Cloud's Main CI workflow (→ xcode-cloud-single-track-ci) can't run — quota exhausted, an outage, or CI not wired up yet. Same three Apple CLIs Xcode Cloud uses under the hood — xcodebuild archive, -exportArchive, upload — driven by hand instead of Apple's managed runner.

When to invoke

• Xcode Cloud can't run but a build must reach internal TestFlight today.
• Writing or debugging a local archive/export/upload script or one-off command.
• Diagnosing an ExportOptions.plist / signing / build-number failure.
• Asked "how do I ship a build without Xcode Cloud" or "what does -exportOptionsPlist need".

Scope