---
name: launch-preflight
description: Consolidate observed visual, source, accessibility, rights and product-flow evidence into a concrete release gate table. Use when a cinematic project is being prepared for review, public launch or paid-library release.
---

# Launch preflight

Set the actual scope: preview, public free release or paid library. Use `plan_launch_preflight` to track evidence; absent checks stay unverified. A passing result records supplied observations and does not itself authorize deployment.

Use `plan_visual_qa` and `get_export_checklist` to gather desktop/phone frames at 0/25/50/75/100%, reverse continuity, native scroll, decoded fonts/media, pause/reduced motion and the exact exported files. Inspect useful content after the hero and real form destinations.

Use `check_motion_accessibility`, `check_accessibility_markup` and actual browser keyboard/focus checks together. Source signals and color calculations cannot establish accessibility compliance. Run `validate_asset_manifest`, `audit_dependencies`, `review_licensing` and `check_media_provenance` for real packaging evidence.

For public releases, confirm operator-approved privacy/contact information and asset distribution rights. For paid libraries, verify actual checkout, recurring-price disclosure, cancellation, refunds and plan entitlements; a pricing card or waitlist is not billing. Do not invent an address, jurisdiction, certification, legal clearance or paid transaction evidence.

Return the gate table, evidence paths and a short prioritized defect list. If a user asks for a narrower review, honor that scope. The guide does not start autonomous agents, generate media, submit paid jobs, publish, or message others.