launch

# launch ## Purpose Orchestrate the full deployment and marketing pipeline. Launch coordinates testing, deployment, live site verification, marketing asset creation, and public announcement. One command to go from "code ready" to "product live and marketed." <HARD-GATE> - ALL tests must pass before any deploy attempt. Zero exceptions. Block deploy if any of: tests failing, TypeScript errors present, build fails, or sentinel CRITICAL issues detected. </HARD-GATE> ## Triggers - `/rune launch` — manual invocation - Called by `team` when delegating launch tasks ## Calls (outbound) - `test` (L2): pre-deployment full test suite - `audit` (L2): pre-launch health check — full 7-phase quality gate - `deploy` (L2): push to target platform - `incident` (L2): if post-launch health check fails → triage and contain - `retro` (L2): post-launch retrospective — what went well, what didn't - `browser-pilot` (L3): verify live site screenshots and performance - `marketing` (L2): create launch assets (landing copy, social, SEO) - `watchdog` (L3): setup post-deploy monitoring - `video-creator` (L3): create launch/demo video content - L4 extension packs: domain-specific launch patterns when context matches (e.g., @rune/devops for infrastructure, @rune/ecommerce for storefront) ## Called By (inbound) - User: `/rune launch` direct invocation - `team` (L1): when team delegates launch phase --- ## Execution ### Step 0 — Artifact Readiness Check Before starting the pipeline, verify that pre...