docs: M5d-2: after gate: ok, do not sum test results

Task 01 told Ornith to add up every `test result:` N passed. A greedy
sed kept the last digit (1512 became 1022) and it stopped with the
correct T1 and given test uncommitted. T50/T59: the last line of
make gate is the count; summing is not a stop.

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

docs/plans/M5d2/10-memoryd-tiers.md

@@ -226,7 +226,8 @@ Do not edit `cli_memory.rs`. This file is the M5c pin of the same USAGE string.
 - [ ] **5. Check.** `git diff --stat` lists the files in "Every place that changes" except
   the new tests and starter (those are untracked until `git add`).
 - [ ] **6. Run the gate.** `cargo fmt --all`, then `make gate`, timeout 600000 ms. Last line
-  `gate: ok`. Test count **1574** (1568 before, plus 6).
+  `gate: ok`. Test count **1574** (1568 before, plus 6). After `gate: ok`, do not add up
+  `test result:` lines.
 - [ ] **7. Log and commit.** Task cell `M5d2/10-memoryd-tiers`. Stage with
   `git add crates/bxcore crates/memoryd crates/bxctl config/jobs docs/implementer-log.md
   Cargo.lock`, then commit as `AGENTS.md` says.
@@ -239,7 +240,7 @@ Do not edit `cli_memory.rs`. This file is the M5c pin of the same USAGE string.
 ## Stop and report if
 
 - The branch check fails; a "before" block is not found exactly once; step 2 differs; `cargo
-  check` warns; a test fails; the gate count is not 1574; you edit `cli_memory.rs`; you leave
+  check` warns; a test fails; the gate's last line is not `gate: ok`; you edit `cli_memory.rs`; you leave
   the `cli_memory_sync` USAGE pin on the old string; identity entries show a non-zero hit
   count; untrusted notes are omitted; you add a cron crate; you special-case the name `tier`
   in `loopd`.