# Launch Checklist

Checked against ATM main `59432c22e` on 2026-10-12. This distinguishes code
present in main from deployment, publication and pilot acceptance. An implemented
method is not evidence that a target environment is ready for live sales.

## Implemented in ATM main

- [x] Event/type configuration with current organizer/co-organizer authority.
- [x] Private type capacity, optional shared event cap and transactional holds.
- [x] Guarded processor-session recovery/expiry and idempotent issuance.
- [x] Verified free claims with delivery email and authenticated free release.
- [x] Forms, waitlists/offer holds and dual-consent organizer collaboration.
- [x] Hosted email/QR/pass presentation, staff grants and scanner check-in audit.
- [x] Refund/void/cancellation lifecycle with admission revocation and durable jobs.
- [x] App-scoped callback delivery, test events and redrive tooling.
- [x] Public config discovery through ATM AppView.
- [x] Unified payment views and organizer/app ticket workspaces.

## Documentation verification

- [x] Copy all 30 generated schemas from the exact ATM main revision.
- [x] Replace retired type/capacity APIs and fix query parameter reference fields.
- [x] Align paid/free examples and agent guides with current wire contracts.
- [x] Pin the published SDK beta.5; document its remaining contract gaps.
- [ ] Record deployed sandbox acceptance with a real event-app adapter.

## Before a target-environment release

- [ ] Confirm required migrations, runtime configuration and environment endpoints
  from ATM's canonical `docs/ENVIRONMENTS.md` and release runbook.
- [ ] Retain independent implementation approval and required CI for the exact
  release scope. A docs refresh or plan review does not approve runtime release.
- [ ] Verify namespace resolution/publication separately. Served lexicon JSON
  and this copied bundle do not prove authoritative protocol publication.
- [ ] Verify app registration, module flags, callback configuration and organizer
  selling approval in the same target environment.
- [ ] Confirm paid organizer setup and exact ticket Product/Price refs.
- [ ] Exercise concurrent type/event-cap holds without oversell, ambiguous
  retries, expiry/release, settled issuance and durable callback recovery.
- [ ] Exercise signed-in/guest paid identity, fixed payer binding, and any
  explicitly supported payer switch with final-buyer reconciliation.
- [ ] Exercise fresh free claim email validation, replay and authenticated free
  release, plus the distinct paid-with-Free-coupon $0 path.
- [ ] Exercise hidden-type access, ticket-quantity code budgets and purchase limits.
- [ ] Verify pass/email delivery, wallet fallback and presentation restrictions
  without changing an existing valid ticket's admission authority.
- [ ] Scan once, rescan, reject cross-event/list tokens and revoke a staff grant.
- [ ] Verify refunded/voided/canceled tickets cannot admit entry.
- [ ] For machine-scanner pilot, separately validate its exact origin/config,
  credential lifetime, grant revocation and safe bounded retry behavior.

Local starter typecheck/smoke and static docs checks validate contracts and
fixtures only. They do not perform live charges, email delivery, production
publication, deployment or protected merge.