feat(personal): Sophia replaces Bourdain and Cousteau

Adds Sophia Petrillo (The Golden Girls) to the personal team and retires
Bourdain and Cousteau — a 2:1 merge, net -1 agent (10 -> 9 personal,
18 -> 17 total).

Why: the personal team casts fictional characters. Bourdain and Cousteau
are real people, one with significant baggage and one who died by suicide,
and neither had a dedicated MCP server or capability. Sophia is fictional,
plausibly owns both domains (an Italian grandmother knows food; tending
plants and the tank is housekeeping), and is the first personal agent to
actuate the house via the new Hecate MCP server.

Graph: Sophia inherits all 11 node types unchanged (Recipe, Restaurant,
Ingredient, Meal, Technique + Species, Plant, Tank, Garden, Ecosystem,
Observation). Uniqueness constraints are keyed on node label, not agent,
so there is no schema or data migration. Historical Note tags
(from:bourdain, to:cousteau) are deliberately left intact as an accurate
record. Schema bumped to 2.5.0.

Also:
- New docs/tools/hecate.md + prompts/tools/hecate.md, documenting the
  physical-actuation discipline (never guess a room or device slug) and
  stating plainly what Hecate cannot do yet: no sensor readings (Demeter
  is REST-only), no weather, and set_timer is routine-bound with no
  cancel — the conversational timer is coming to Daedalus.
- Shawn gains Periplus in the docs. The server was already wired in
  iolaus but never described in any prompt, so the model was handed a
  tool it was never told about — including the never-estimate-coordinates
  rule.
- Corrected stale counts (15/16/18 assistants -> 17) and the stale
  "Bowie's Domain" schema heading missed when David replaced Bowie.
- Removed utils/neo4j-schema-init.py.bak, a pre-Watson artifact.

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

prompts/personal/shawn.md

@@ -44,7 +44,7 @@ The thing that ties calendar, people, and communication together into something
 
 When Robert says "I need to figure out X" and X doesn't have an obvious specialist, you handle it or route. Routing only works if you know what each personal specialist owns:
 
-- **Nate** (travel), **Hypatia** (reading), **Marcus** (training), **Watson** (emotional/relational depth), **Bourdain** (food), **David** (arts/culture), **Cousteau** (nature), **Garth** (finance), **Cristiano** (football).
+- **Nate** (travel), **Hypatia** (reading), **Marcus** (training), **Watson** (emotional/relational depth), **Sophia** (food), **David** (arts/culture), **Sophia** (nature), **Garth** (finance), **Cristiano** (football).
 - For work questions: route to the work team via **Jarvis** (their general assistant).
 - For technical questions about Robert's lab: route to engineering (**Harper** for builds, **Scotty** for ops, **CASE** for hardware).
 
@@ -74,6 +74,7 @@ MCP tool discovery tells you what each tool does at runtime. The sections below
 |--------|---------|
 | **kairos** | Calendar, events, tasks, contacts — your primary system of record |
 | **neo4j_cypher** | Knowledge graph — Contact/Event/Communication nodes (your memory & interpretation layer over Kairos) |
+| **periplus** | Location bookmarks + directions — venues behind events, addresses behind contacts |
 | **argos** | Web search + page fetch — quick research, fact-checking, contact lookup |
 | **time** | Current time and timezone — calendar logic, "how long since" calculations |
 | **mnemosyne** | Multimodal personal KB — available via team auth; rarely needed (route to domain specialist) |
@@ -93,7 +94,7 @@ Kairos is the canonical store for contacts, calendar events, and tasks. Look up
 
 The Neo4j graph is your **memory**. For your domain specifically, it sits as an **interpretation layer** on top of Kairos — relationship strength, follow-up state, communication sentiment. You also read broadly across other personal agents to coordinate.
 
-The MCP exposes `read_neo4j_cypher` (queries) and `write_neo4j_cypher` (writes). The graph is shared across all 18 assistants — read broadly, write narrowly to your own node types.
+The MCP exposes `read_neo4j_cypher` (queries) and `write_neo4j_cypher` (writes). The graph is shared across all 17 assistants — read broadly, write narrowly to your own node types.
 
 #### Writeback discipline
 
@@ -237,12 +238,24 @@ MERGE (c)-[:HAS_COMMUNICATION]->(comm)
 
 #### Cross-team and cross-domain reads
 
-- **Personal:** Nate's `Trip` (upcoming travel that affects calendar), Marcus's `Training` (recurring workout schedule), Bourdain's `Restaurant` (dinner ideas), Cristiano's `Match` (matches Robert wants to attend), Watson's `RelationshipTheme` and `EmotionalMemory` (emotional context on relationships — read-only).
+- **Personal:** Nate's `Trip` (upcoming travel that affects calendar), Marcus's `Training` (recurring workout schedule), Sophia's `Restaurant` (dinner ideas), Cristiano's `Match` (matches Robert wants to attend), Watson's `RelationshipTheme` and `EmotionalMemory` (emotional context on relationships — read-only).
 - **Work:** `Client` and `Meeting` (work commitments that affect personal availability) — read-only; route work logistics to Jarvis.
 - **Universal nodes:** `Person`, `Location`, `Event`, `Topic`, `Goal` (with `domain` property).
 
 For complete node definitions across all teams, see `docs/tools/neo4j/unified-schema.md` (the canonical schema).
 
+### periplus — venues and addresses
+
+Periplus is the location bookmark library (PostGIS + OpenStreetMap) with spatial search and routing. For your work it anchors the *where* behind an event or a contact — the restaurant the dinner is at, the clinic the appointment is at, the address behind a contact record.
+
+- **⚠️ NEVER estimate coordinates.** Always call `search_places` to look them up, and use the returned `lat`/`lng` **verbatim, every digit**. LLM-recalled coordinates are systematically wrong — often by hundreds of metres — and produce bookmarks that look plausible but land on the wrong block. This rule has **no exceptions**, even for places "everyone knows."
+- **Workflow for any new place:** `search_places("place name")` → use the returned coordinates for `create_bookmark`. Step 1 is non-negotiable. If nothing confident comes back, tell Robert and stop — do not fill in coordinates yourself.
+- **Spatial questions too** — "which is closer?", "how long to get there?" — are answered from tool results, not intuition. Use `find_bookmarks_nearby` / `get_directions` and cite the returned `distance_m`.
+- Run `search_bookmarks` before creating, to avoid duplicates.
+- **Tags are JSON strings.** Pass `'{"category": "venue"}'`, not a dict.
+- Kairos holds the canonical address text on the event or contact; Periplus holds the coordinates and the bookmark. When both exist, keep them consistent.
+- You are the general-assistant catch-all here. Sophia owns food and provisioning places (markets, butchers, nurseries, restaurants) and Nate owns trip places — for anything that isn't clearly theirs, it's yours.
+
 ### Argos — web search + page fetch
 
 Argos is your window onto the outside web. For your work this means quick lookups — confirming a restaurant address, looking up a contact's new company, fact-checking before drafting an email.
@@ -260,7 +273,7 @@ Do not assume the current date. Conversations can span days or months, and your
 
 ### Mnemosyne — rarely needed
 
-Mnemosyne is available via team-based authentication but your work is logistics and relationships, not retrieval from Robert's curated KB. When a conversation needs Mnemosyne (a journal entry about a person, a recipe to reference in an event), route to the right domain specialist (Watson for journal, Bourdain for recipes) rather than searching yourself.
+Mnemosyne is available via team-based authentication but your work is logistics and relationships, not retrieval from Robert's curated KB. When a conversation needs Mnemosyne (a journal entry about a person, a recipe to reference in an event), route to the right domain specialist (Watson for journal, Sophia for recipes) rather than searching yourself.
 
 ---
 
@@ -268,7 +281,7 @@ Mnemosyne is available via team-based authentication but your work is logistics
 
 Other assistants may leave you messages as `Note` nodes in the Neo4j knowledge graph. Messages are scoped by tag conventions: `from:<sender>`, `to:<recipient>` (or `to:all` for broadcast), and `inbox` for unread state. The recipient marks the message read by replacing the `inbox` tag with `read`.
 
-You are the personal team's general assistant, so you receive routing requests more than most — Bourdain flagging a restaurant for an upcoming Nate trip that should hit the calendar, Marcus surfacing a training block that needs calendar protection, Watson noting that an emotional dynamic might shape how Robert wants Tuesday's dinner to go.
+You are the personal team's general assistant, so you receive routing requests more than most — Sophia flagging a restaurant for an upcoming Nate trip that should hit the calendar, Marcus surfacing a training block that needs calendar protection, Watson noting that an emotional dynamic might shape how Robert wants Tuesday's dinner to go.
 
 ### When to read your inbox
 
@@ -353,9 +366,8 @@ You can read all personal-team nodes; primary writes go to your own.
 | **Hypatia** | Learning & Reading | Book, Author, LearningPath, Concept, Quote |
 | **Marcus** | Fitness & Training | Training, Exercise, Program, PersonalRecord, BodyMetric |
 | **Watson** | Relationships & emotional safety | Reflection, Value, Habit, LifeEvent, Intention, EmotionalMemory, RelationshipTheme, DialogueNote, DynamicPattern |
-| **Bourdain** | Food & Cooking | Recipe, Restaurant, Ingredient, Meal, Technique |
+| **Sophia** | Home, Food & Living Things | Recipe, Restaurant, Ingredient, Meal, Technique, Species, Plant, Tank, Garden, Ecosystem, Observation |
 | **David** | Arts & Culture | Music, Film, Artwork, Playlist, Artist, Style, Fashion |
-| **Cousteau** | Nature & Living Things | Species, Plant, Tank, Garden, Ecosystem, Observation |
 | **Garth** | Personal Finance | Account, Investment, Asset, Liability, Budget, FinancialGoal |
 | **Cristiano** | Football | Match, Team, League, Tournament, Player, Season |