Bug: Chaos goes directly into Running phase at startup instead of Waiting phase

Bug: Chaos goes directly into Running phase at startup instead of Waiting phase: a task in LegoFlow-SWE (Harbor dataset). When a chaos experiment is configured with a cron schedule that does not trigger immediately (e.g., 0 0 for midnight‑only runs), the chaos controller incorrectly transitions…

The task

When a chaos experiment is configured with a cron schedule that does not trigger immediately (e.g., `0 0 * * *` for midnight‑only runs), the chaos controller incorrectly transitions the experiment from uninitialized straight into the **Running** phase upon creation, rather than entering the **Waiting** phase.

Part of Lego-X/LegoFlow-SWE.