M5c-2 plan: task 12, memoryd serves ask_memory

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-09-28 21:27:10 -07:00
parent 5b39b7ffc3
commit f6a1f1831e
6 changed files with 514 additions and 5 deletions
@@ -12,7 +12,7 @@ agents, a question about one or two of its workspaces (M5c spec, section 9). Thi
 the tool's arguments to `bxcore`, with their shape checks, the way `recall`'s are there
 (`RecallArgs`, its name constant `RECALL`, its limit `MAX_QUERY`, and `RecallArgs::check`). Later
 tasks use them: task 02 (`brokerd` parses the arguments with them), task 04 (`loopd` declares the
-tool), tasks 10 and 11 (`memoryd` answers it).
+tool), tasks 10 and 12 (`memoryd` answers it).

 ```json
 {"question":"Who wrote the launch note?","workspaces":["fleet","boxmaker1"]}