asc-ad-hoc-distribution

1# ASC ad hoc distribution
2 
3Use the experimental `asc distribute` workflow to turn an existing iOS archive
4into a private, verified install link for registered devices. Use TestFlight or
5the App Store release skills instead when the build should go through Apple-hosted
6distribution.
7 
8Confirm the installed contract before acting:
9 
10```bash
11asc distribute --help
12asc distribute plan --help
13asc distribute apply --help
14asc distribute resume --help
15asc distribute status --help
16asc distribute verify --help
17```
18 
19## Choose the workflow
20 
21- Use `plan` -> `apply` -> `resume`/`status` -> `verify` for an end-to-end,
22  hash-authorized run starting from an `.xcarchive`.
23- Use `inspect` -> `prepare` -> `publish` only when the caller already owns the
24  ad hoc IPA and wants to operate the lower-level boundaries separately.
25 
26## Guardrails
27 
28- Treat the distribution spec, devices file, PKCS#12 identity, password file,
29  run state, and exact install-link artifact as private. Keep them out of Git and
30  require owner-only permissions.
31- Never put S3 credentials or presigned URLs in the distribution spec, command
32  output, logs, issues, or chat. Use `ASC_S3_ACCESS_KEY_ID`,
33  `ASC_S3_SECRET_ACCESS_KEY`, and optional `ASC_S3_SESSION_TOKEN`, or the
34  standard AWS SDK credential chain.
35- `plan` is read-only and may exit successfully with `ready: false`. Inspect the
36  typed blockers and effects before continuing.
37- `apply` can register missing devices, create safe App IDs and successor ad hoc
38…