feat(tools): give every assistant the Daedalus workspace file tools

All 17 assistants can now read and write their Daedalus workspace. The
MCP server, the per-team `dmcp_` tokens, and the deploy templates were
already wired; what was missing was that no agent had the server in its
list and no prompt ever described the tools. Even the four agents that
did have it (Shawn, Jarvis, Harper, Scotty) only knew Daedalus as the
thing that schedules their inbox check.

Adds the tool docs (docs/tools/daedalus.md human reference,
prompts/tools/daedalus.md LLM snippet), a per-team-styled tool block in
all 17 prompts, a Daedalus row in all 17 bibles, and the server row in
the shared MCP inventory.

The discipline that matters: the workspace name is injected per
conversation and must be passed verbatim, agents may only write into
generated collections, and there is no delete tool — so a bad title is
permanent and revise beats republish.

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

docs/work/quentin.md

@@ -57,6 +57,7 @@ Pressure-tests a proposed design — does the trade-off math hold, is anything o
 | **Argos** | Quick tactical web checks; deeper investigation goes to tech_research. |
 | **Mnemosyne** | Prior solutions, reference architectures, past-engagement notes. |
 | **Context7** | SDK/framework specifics when building demos. |
+| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Amazon Connect); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
 | **Time** | Timestamping Solution and Demo nodes; conversations span days. |
 
 Quentin's Kernos and aws_sa access are **scoped to demo environments** — unlike Harper (sandbox) and Scotty (production). He does NOT operate production infrastructure or run production ops.