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

@@ -62,6 +62,7 @@ Matches Robert watched or attended get `Match` nodes — date, competition, team
 | **Kairos** | Calendar entries for matches — when Robert is attending, when must-watch fixtures are scheduled, tournament windows. Reads to know what's coming; writes when Robert commits to attending. Coordinate with Shawn for the broader calendar. |
 | **Mnemosyne** | Robert's curated football reading — books on tactics, club histories, biographies. Scope by `library_type`: `nonfiction` for football writing, `journal` for Robert's own match notes. |
 | **Argos** | Quick reference — vendor announcements, transfer news, the article everyone's talking about, fact-checks before strong claims |
+| **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** | Match timing, kick-off windows in different timezones, season calendar math |
 
 For deep research on a topic — a tactical question across multiple matches, a comparison spanning eras, a deep-dive on a club's recent history — delegate to the **research** subagent.

docs/personal/david.md

@@ -84,6 +84,7 @@ Music gets `Music` nodes (title, artist, year, rating, notes — the notes are w
 | **Periplus** | Stores, theatres, studios, apothecaries — the *places* where culture and good taste live. Collections by city or by type. **Always `search_places` first; never estimate coordinates.** |
 | **Orpheus** | Robert's Kawai piano. David's lens is *demonstration through play* — illustrating a chord progression he's recommending, playing the passage he's describing, setting a mood with a piece while talking about it. Different from Hypatia's pedagogical use; David uses Orpheus to *show* rather than *teach*. |
 | **Argos** | Looking up an exhibition's dates, a film's release, a designer's recent collection, a music release Robert mentioned |
+| **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** | Cultural calendar — when an exhibition closes, when an album drops, the era of a piece |
 
 For deep multi-query research on an artist, a movement, or a body of work, delegate to the **research** subagent.

docs/personal/garth.md

@@ -70,6 +70,7 @@ Accounts get `Account` nodes — TFSA, RRSP, non-registered, joint, etc. — wit
 | **Neo4j** | Primary tool — Account, Investment, Asset, Liability, Budget, FinancialGoal nodes. The long arc of Robert's financial life lives here. Reads broadly — Nate's `Trip` for travel budgeting, Watson's `Value` nodes for finance-versus-life-values alignment, Hypatia's `Book` for financial-literacy reading. |
 | **Mnemosyne** | Robert's curated financial reading. Scope by `library_type`: `finance` for statements, tax records, market commentary (quote figures exactly), `nonfiction` for personal-finance books, `journal` for Robert's own notes on money decisions. |
 | **Argos** | Current rates, ETF performance, market news, Canadian-specific announcements (BoC rate decisions, federal budget changes, tax-bracket updates) |
+| **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** | Tax-year math, time-value-of-money calculations, "how long until retirement" framing |
 
 For deep multi-query research on a specific security, sector, or financial strategy, delegate to the **research** subagent.

docs/personal/hypatia.md

@@ -58,6 +58,7 @@ Books get `Book` nodes (title, author, status, themes, takeaways). Authors get `
 | **Neo4j** | Book, Author, Topic, LearningPath, Concept, Quote nodes. Cross-references across other agents — Watson's `Reflection` and `EmotionalMemory` when reading touches relationships; Garth's books for financial literacy; David's `Music` and `Film` for adaptations. |
 | **Argos** | Researching a book before recommending it; finding what's been written about a concept; locating primary sources |
 | **Orpheus** | Pedagogical use — demonstrating music-theory concepts on the piano. A scale to hear, a chord progression to compare, a fugue's opening to dissect. Use when *hearing* the concept teaches faster than describing it. |
+| **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** | Date-stamping reading sessions, tracking when Robert read what, "when did I last read about X" calculations |
 
 For deep multi-query research on a topic or author, delegate to the **research** subagent rather than running long Argos chains.

docs/personal/marcus.md

@@ -53,6 +53,7 @@ Each training session gets a `Training` node — date, exercises performed, perc
 |---|---|
 | **Neo4j** | Primary tool — Training, Exercise, Program, PersonalRecord, BodyMetric nodes. The long arc of practice lives here. Reads broadly — Watson's `EmotionalMemory` for "how is Robert really doing," Nate's upcoming trips when training needs to prep for activity, Sophia's nutrition for performance support. |
 | **Mnemosyne** | Robert's curated training and fitness reading — what he's been studying, what frameworks he's found useful. Scope by `library_type`: `nonfiction` (training books), `journal` (Robert's own notes on his training experience). |
+| **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** | Workout timing, "how long since last session" calculations, recovery windows, scheduling progression |
 | **Argos** | Quick reference — exercise form cues, programming approaches, current research on training topics. Light use; most training context lives in Neo4j or Mnemosyne already. |
 

docs/personal/nate.md

@@ -61,6 +61,7 @@ A new trip typically writes to all three: create the Periplus collection and boo
 | **Kairos** | Trip windows on the calendar; contacts at the destination when relevant. Coordinate with Shawn when calendar conflicts surface. |
 | **Argos** | Heavy use — destination research, current conditions, visa requirements, weather windows, recent news affecting travel |
 | **Mnemosyne** | Robert's curated journal and travel writing — past trips, places he wants to go. Scope queries by `library_type` (`journal` for personal entries, `nonfiction` for travel writing). |
+| **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** | Trip date math, time zones, "when's the best month to go" calculations |
 
 For deep multi-query research on a destination, delegate to the **research** subagent rather than running long Argos chains in context.

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. |
 

docs/personal/sophia.md

@@ -76,6 +76,7 @@ The `Observation` node carries extra weight for Sophia, because until Hecate exp
 | **Periplus** | Places where provisioning happens — markets, butchers, fish shops, nurseries, garden suppliers, restaurants. Collections by city or type. **Always `search_places` first; never estimate coordinates.** |
 | **Mnemosyne** | Robert's curated reading. Scope by `library_type`: `nonfiction` for food writing and natural history, `technical` for care manuals and aquarium chemistry, `journal` for Robert's own notes. |
 | **Argos** | Quick lookups — is that restaurant still open, what is eating the tomatoes this year, current care guidance for a species. Light use; depth lives in Neo4j and Mnemosyne. |
+| **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** | Seasonality is fundamental in both halves of the domain — what is in season, when to plant, when blooms come, when the tank needs a water change. Never assume the date. |
 
 For deep research on a cuisine, a species, or a horticultural problem, delegate to the **research** subagent.

docs/personal/team.md

@@ -135,6 +135,8 @@ The personal team's distinctive tools beyond the shared ones:
 - **Orpheus** — Kawai piano MCP. Primarily used by David for actually playing music rather than just talking about it, but available to any agent with a legitimate reason to play something. See [docs/tools/orpheus.md](../tools/orpheus.md).
 - **Mnemosyne** — Robert's curated multimodal KB. Available to all personal agents via team-based authentication; each agent self-filters by `library_type` based on their domain (Hypatia → fiction/nonfiction, David → music/film/art, Watson → journal, Sophia → nonfiction food writing and natural history, Garth → finance, etc.). See [docs/tools/mnemosyne.md](../tools/mnemosyne.md).
 
+**Daedalus** is shared by every agent on every team — the workspace document store, and the assistants' only persistent place to write prose. The personal team is filed under the **Personal** scope, which reaches the **Home**, **Assistant**, and **World Cup 2026** 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

docs/personal/watson.md

@@ -75,6 +75,7 @@ Watson's writes carry more emotional weight than other agents'. Some specific pa
 | **Neo4j** | Primary tool — the 9 node types (Reflection, Value, Habit, LifeEvent, Intention, EmotionalMemory, RelationshipTheme, DialogueNote, DynamicPattern). The relationship memory and pattern tracking live here. Reads broadly — Shawn's `Contact` and `Communication` for who Robert is talking about and the recent interaction history, Marcus's `Training` to see whether the body has been a factor. |
 | **Kairos** | Read-heavy. Pull contact context (who Robert is talking about — name, relationship, history) and event context (a wedding, a funeral, a kid's birthday — life events that ground emotional conversations). Writes only when adding life events Watson is specifically tracking; the relationship-interpretation layer stays in Neo4j. |
 | **Mnemosyne** | Robert's curated journal and reading. Scope by `library_type`: `journal` for his own entries (the most relevant for Watson's work — what Robert was already thinking about a person or a pattern), `nonfiction` for books on relationships, attachment, communication. |
+| **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** | Date-stamping reflections, "how long since" calculations, knowing what season or life-phase a memory belongs to |
 
 Watson generally does NOT use: Kernos/Grafana (engineering), Periplus (geographic — Nate's domain), Nike (football — Cristiano's domain), Orpheus (music — David's or Hypatia's domain), Argos (the outside web is rarely what Watson needs; what he needs is Robert's own context).