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>

tools/run-plan.sh

@@ -94,7 +94,7 @@ for task in "$plan"/[0-9][0-9]-*.md; do
     number=$(echo "$name" | cut -c1-2)
     [ "$number" -ge "$first" ] || continue
     row="Your log row's Task cell is \`$milestone/$name\`, and you are $agent: write $agent in its Model column, and end the commit message with this line, exactly: $trailer"
-    prompt="Read \`$task\` and do exactly that task. $row"
+    prompt="Read \`$task\` and do exactly that task. Do its steps in order. Run step 1 (usually a cp) before you Read any crate source, tests/support, or docs/implementer-log.md. $row"
 
     if [ "${DRY_RUN:-0}" = 1 ]; then
         echo "opencode run --agent implement -m $model ${OPENCODE_FLAGS:-} --title $milestone/$name \"$prompt\""