A plan that names a task you never wrote no longer runs in the wrong order.loop-cohort schedule used to drop a Depends on: entry pointing at a task the plan did not contain — no warning, no error. The dependency edge vanished, the tasks collapsed into one wave, and because gates run per wave, the gate run collapsed with them. schedule now stops, names every offending task->dependency pair, and writes no state, so you fix the plan instead of discovering the wrong order later.