docs: M5d-2 task 06: cp first, tick is glue

The second 06 session listed tests/, read eight loopd modules and
support/mod.rs, grepped bxcore, then hit Context size exceeded with
no commit. The cp is now the first action; tick is glue over two
todo!() bodies; run-plan tells the session to run step 1 before
reading crate source.

Co-Authored-By: Grok 4.6 <noreply@x.ai>

docs/plans/M5d2/07-loopd-scheduler-cron.md

@@ -5,6 +5,10 @@ is empty; otherwise stop. Never switch branch.
 **Commit subject:** `loopd: cron tick, new session per run`
 **Log row:** the Task cell is `M5d2/07-loopd-scheduler-cron`.
 
+**First action.** Copy the given test before any other Read of crate source. Do not `ls`
+`crates/loopd/tests/`. Do not Read `tests/support/` or `docs/implementer-log.md` (except the
+first 12 lines at the log step).
+
 ## Goal
 
 After the heartbeat work, `tick` loads `{home}/jobs/*.toml` and runs each job whose schedule