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/alan.md

@@ -69,6 +69,7 @@ Strategic decisions get a `Decision` node — title, context, options considered
 | **Neo4j** | Strategic decisions, competitive intelligence, market trends, client portfolio assessments — the primary tool |
 | **Athena** | Client portfolio analysis, relationship strategy, account reviews — the CRM-side view of clients and opportunities. Read-heavy; occasional writes for strategic-level notes on clients and competitive vendor records. |
 | **Argos** | Quick web checks — vendor announcements, industry news, competitor moves |
+| **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** | Date-stamping decisions and observations |
 
 Alan generally does NOT use: Kernos (no shell work), Grafana (no ops), Mnemosyne (some overlap with content but Ann owns the curated KB side), Context7/GitHub/Gitea (no code work).

docs/work/ann.md

@@ -53,6 +53,7 @@ Content shipped gets a `Content` node — title, type, status, where it appeared
 | **Neo4j** | Content tracking — what's been published where, on what topics — and reading Alan's positioning decisions to ensure content aligns |
 | **Argos** | Research for content — current state of a topic, what's been said by others, sources to link to |
 | **Mnemosyne** | Robert's curated reading and notes — the raw material for authentic content. What has he actually been reading, thinking about, working on? |
+| **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** | Publishing dates, content scheduling |
 
 Ann generally does NOT use: Athena (the CRM-level client/opp data isn't her primary lens — that's Jeffrey/Alan/Jarvis), Kernos (no shell work), Grafana, Context7/GitHub/Gitea (no code work).

docs/work/jarvis.md

@@ -60,6 +60,7 @@ Tasks get `Task` nodes (title, status, priority, due date). Meetings get `Meetin
 |---|---|
 | **Neo4j** | Task, Meeting, Note, Decision nodes. Daily operations memory — what's pending, what got done, what's coming up. |
 | **Athena** | Client and contact context for meetings, scheduling exchanges, and follow-up. Less deep than Jeffrey's use; more "who am I talking to and what's the history." Writes back new contacts and post-meeting contact notes when appropriate. |
+| **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** | Calendar logic, due dates, meeting time-windows |
 | **Argos** | Quick research for meeting prep, fact-checks for drafted messages |
 | **Mnemosyne** | Past notes and reference material relevant to the current task |

docs/work/jeffrey.md

@@ -62,6 +62,7 @@ Opportunities get `Opportunity` nodes (stage, value, probability, next action).
 |---|---|
 | **Athena** | Primary source for client and opportunity intelligence. Look up history *before* any sales conversation or proposal work; write back stage transitions, notes, and new contacts after a meaningful interaction. |
 | **Neo4j** | Pipeline progression and sales intelligence — Opportunity, Proposal, Contact, Meeting nodes. The institutional memory of every deal. |
+| **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** | Date-stamping every interaction; pipeline cadence calculations |
 | **Inbox** | Cross-agent messages — handoffs from Alan, content drops from Ann, scheduling from Jarvis |
 

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.

docs/work/team.md

@@ -130,6 +130,8 @@ Each agent's tool usage is documented in their own doc — the agent doc is the
 
 The work team's distinctive tool is **Athena** — a CRM-like platform for clients, vendors, contacts, opportunities, and pipeline. Alan, Jeffrey, and Jarvis use Athena heavily. Ann generally doesn't. See [docs/tools/athena.md](../tools/athena.md).
 
+**Daedalus** is shared by every agent on every team — the workspace document store, and the assistants' only persistent place to write prose. The work team is filed under the **Work** scope, which reaches the **Amazon Connect** and **Infrastructure** workspaces; the workspace an agent is operating in is injected per conversation rather than fixed per agent. See [docs/tools/daedalus.md](../tools/daedalus.md).
+
 The canonical graph schema (all 17 assistants, all node types) is at [docs/tools/neo4j/unified-schema.md](../tools/neo4j/unified-schema.md).
 
 ## Cross-Team Touchpoints