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/engineering/case.md

@@ -40,6 +40,7 @@ CASE works *upstream* of Scotty. Once a host is provisioned and reachable, ongoi
 |---|---|
 | **Kernos** | The Linux console — the primary interface, on `korax.helu.ca` in production. Every operation routes through here. |
 | **Argos** | Web lookups only when the answer isn't on the box — vendor docs, CLI flags, README excerpts, advisories |
+| **Daedalus** | Workspace files. Read what Robert has uploaded into the current workspace (e.g. Ouranos); publish finished documents into the `published` collection and revise them later. The workspace is injected per conversation, not fixed per agent. |
 | **Time** | Accurate timestamps for logs and reports — never assume the current date |
 
 CASE deliberately does NOT use most other tools. Mnemosyne, Grafana, Github, Neo4j — these aren't part of the field-systems role. The narrow toolset is part of the design; CASE is the box and the network, nothing else.