Exercise 3: Why submit_for_review Must Wait for the Pre-Flight Checklist — Possible Solution ================================================================================================== Chapter 7 established that App Review checks a real, specific, guideline-numbered list of common rejection reasons - a missing demo account for a login-gated app under 2.1(a), a screenshot that shows only a launch screen under 2.3.3, an app that doesn't genuinely elevate itself beyond a repackaged website under 4.2, and several others. Step 6 of this capstone exists specifically to check TaskFlow against every one of those real, known triggers before submission ever happens. If the submit lane's own submit_for_review: true step ran automatically, immediately after Step 5's own metadata was filled in, with no real pre-flight check in between, TaskFlow could genuinely be submitted while still missing something Chapter 7 already identified as a common, real rejection trigger - the demo account credentials never actually added to the review notes, for instance, or a screenshot that quietly still shows the launch screen instead of the real, populated task list. The real risk of skipping that order is a genuinely avoidable rejection: a reviewer encountering exactly the kind of problem Chapter 7 already named specifically, resulting in a real delay while the missing piece gets fixed and the app is resubmitted - time that Step 6's own deliberate, manual check, done first, would have caught for free, before ever consuming a real App Review cycle at all. ANSWER: submit_for_review: true should only run after Step 6's own pre-flight checklist passes because that checklist exists specifically to catch the real, known rejection triggers Chapter 7 identified - skipping it risks submitting a build that's still missing something Chapter 7 already flagged, like demo credentials or a compliant screenshot, resulting in a real, avoidable rejection and a wasted review cycle instead of a clean first submission. WHY THIS WORKS AS AN ANSWER ------------------------------ This ties the ordering requirement directly to Chapter 7's own specific, named rejection triggers and explains the concrete, real cost (an avoidable rejection and wasted review cycle) of skipping the pre-flight step, rather than just asserting that checking first is good practice.