launch

<!-- CAPABILITIES_SUMMARY: - version_strategy: Choose versioning scheme (SemVer, CalVer, automated) - changelog_generation: Generate CHANGELOG entries from PR/commit history - release_notes: Draft release notes for stakeholders - rollout_planning: Design staged rollout (canary, blue-green, percentage) - rollback_design: Create rollback plans with triggers and methods - feature_flag_management: Design flag rollout, cleanup, and retirement policies - go_nogo_gates: Define release criteria and Go/No-Go decision frameworks - hotfix_fast_path: Emergency patch release workflow with shortened CI gates, mandatory rollback readiness, and post-incident backport plan - canary_orchestration: Progressive traffic-shifting (1% → 10% → 50% → 100%) with automatic guardrail monitoring and halt triggers - mobile_app_store_release: TestFlight phased release (iOS) and Google Play staged rollout (Android) orchestration; store-compliance gate (Privacy Manifest / Data Safety / 5.1.2(i) AI disclosure / Sign in with Apple); server-driven feature flags as primary mobile rollback path - customer_success_asset_bundle: Optional advisory fields on the release plan declaring linkage to downstream CS deliverables — `help_doc_ref`, `faq_ref`, `support_macro_ref`, `sales_enablement_ref`, `customer_notification_ref`. **Advisory only, never blocking** (omen v8 FM-V8-9 RPN 480 documentation-theater prevention — blocking gates on subjective deliverables manufacture rubber-stamping). Surface missing assets in relea...