M5c-2 plan: task 07, local recall items in the one indented form; later tasks renumbered

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/plans/M5c2/06-memoryd-honcho-recalled.md

@@ -7,11 +7,11 @@ is empty; otherwise stop. Never switch branch.
 
 ## Goal
 
-From task 07 on, `recall` searches other agents' Honcho workspaces and the fleet's beside the
+From task 08 on, `recall` searches other agents' Honcho workspaces and the fleet's beside the
 local index (M5c spec, section 8). This task writes the pure part: what `recall` makes of
 Honcho's results. A new module, `crates/memoryd/src/honcho/recalled.rs`, turns one source's
 results into items, interleaves the sources' items after the local hits, and labels the answer.
-It does no I/O; nothing calls it until task 07.
+It does no I/O; nothing calls it until task 08.
 
 - **The inputs, per source**: its `Label` (task 05); the messages Honcho's workspace search
   returned (`roncho::Message`); and for another agent's workspace, the conclusions of two
@@ -47,7 +47,7 @@ It does no I/O; nothing calls it until task 07.
 - **The label** of the answer's Honcho part: the highest class of the items shown, `private` at
   the least, and untrusted when any shown item is. An item dropped as irrelevant, as a duplicate,
   or because `k` was full labels nothing (T58).
-- **`{name}: unavailable`**: one line per source that did not answer, after the items. Task 07
+- **`{name}: unavailable`**: one line per source that did not answer, after the items. Task 08
   decides which did not.
 
 ## Every place that changes