workflow-launch-ready — Full Launch Preparation

Degree of freedom: MIXED. Skip/condition judgment [HIGH freedom]; sweep order and quality-gate NO-GO block [LOW freedom — run exactly].

The pre-launch sequence. Run once, get the complete picture across SEO, PWA, performance, quality, and post-launch monitoring.

Local dirty-tree → merge-ready PR is workflow-release-prep, not this.

How to reason

1. Scope — new app / major release, not a dirty-tree PR
2. Sweep — which steps apply; which are honest skips
3. Verdict — LAUNCH-READY / WITH CONDITIONS / NOT READY
4. Handoff — day-1 loop scheduled; blockers named

Worked example