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/personal/shawn.md

@@ -70,6 +70,7 @@ When a new contact comes in, Shawn writes to both: create the Kairos record (can
 | **Kairos** | Primary tool — the canonical store for contacts, calendar events, and tasks. Look up before discussing; write back when records need to change. |
 | **Neo4j** | Contact, Event, Communication nodes — the relationship-interpretation layer on top of Kairos. Also reads broadly across other personal agents to coordinate (Nate's trips for calendar, Marcus's training schedule, etc.) |
 | **Argos** | Quick web research — confirming a restaurant address, looking up a contact's company, fact-checking before drafting an email |
+| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Home); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
 | **Time** | Calendar logic, scheduling, reminder windows, "how long since" calculations |
 | **Periplus** | Venues and addresses behind events and contacts — the canonical coordinates for where something is happening. **Always `search_places` first; never estimate coordinates.** Also the general-assistant catch-all for places that aren't another specialist's domain. |