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>

AGENTS.md

@@ -8,6 +8,8 @@ Unix sockets. You are implementing it one task at a time.
 1. The owner gives you one task file, `docs/plans/M<n>/NN-name.md`. Read it fully. Do that task and
    nothing else. Do not start the next task.
 2. Do the steps in order. Where a step shows a command and its expected output, run it and compare.
+   The first step is almost always a `cp`. Run that command before you Read any crate source.
+   Do not `ls` a tests directory. Do not read `tests/support/`.
 3. Do not read `docs/design.md` or other plans unless the task tells you to. The task file quotes
    what you need. Do not read `docs/implementer-log.md` until the log-and-commit step, and then
    only the first 12 lines (the title through the header row). The rest of that file will fill
@@ -72,6 +74,8 @@ These come from defects found in review. The evidence is in `docs/implementer-le
 - Report every problem you find, not only the first.
 - Log every attempt, including one you abandon.
 - Never end a turn by describing what you are about to do. Do it, then report.
+- Run the task's step 1 (the `cp`) before you Read crate source. Do not `ls` a tests directory.
+  Do not read `tests/support/`. The facts table is the API.
 - A refused or failed tool call is not a reason to end your turn. Read the error, then continue
   with another tool call.
 - Fill `todo!()` bodies one at a time, and run `cargo check` after each.