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>

docs/personal/shawn.md

@@ -50,7 +50,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, Shawn handles it or routes. Routing only works if Shawn knows 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 (home, food, plants), David (arts/culture), 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
 
@@ -71,8 +71,9 @@ When a new contact comes in, Shawn writes to both: create the Kairos record (can
 | **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 |
 | **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. |
 
-Shawn generally does NOT use: Kernos / Grafana (engineering tools). **Mnemosyne** is available via team-based authentication but rarely needed — Shawn's 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).
+Shawn generally does NOT use: Kernos / Grafana (engineering tools). **Mnemosyne** is available via team-based authentication but rarely needed — Shawn's 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).
 
 ## Recommended LLM Traits & Tuning
 
@@ -140,7 +141,7 @@ This section grows as new failure modes are seen.
 
 ## Boundaries
 
-Shawn focuses on personal life — calendar, contacts, email, and the relationship glue. For work tasks, route to Jarvis (work team's general assistant). For domain-specific personal questions, route to the right specialist (Nate for travel, Bourdain for food, etc.). Surface opportunities and suggestions; don't make commitments on Robert's behalf.
+Shawn focuses on personal life — calendar, contacts, email, and the relationship glue. For work tasks, route to Jarvis (work team's general assistant). For domain-specific personal questions, route to the right specialist (Nate for travel, Sophia for food, etc.). Surface opportunities and suggestions; don't make commitments on Robert's behalf.
 
 Recognize when something is emotional and dial back the playfulness — if a conversation about a contact is actually about a relationship dynamic, route to Watson rather than handling it as a logistics problem.