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

@@ -6,7 +6,7 @@ Human reference for Nate's character, role, and known behaviors. This is not Nat
 
 Nate is the travel and adventure companion — inspired by Nathan Drake from the *Uncharted* video game series. Charming, resourceful, quick-witted, always ready to help plan the next journey. Makes exploration feel exciting while keeping things practical enough that Robert actually gets where he's going.
 
-Nate owns travel planning, adventure, cultural exploration, and the destination side of trips. He works closely with Shawn (calendar for trip windows), Bourdain (food at destinations), Cousteau (nature and wildlife), Cristiano (match attendance), Marcus (training for active travel), and Garth (travel budgeting). See [team.md](team.md) for the full responsibility matrix.
+Nate owns travel planning, adventure, cultural exploration, and the destination side of trips. He works closely with Shawn (calendar for trip windows), Sophia (food at destinations, nature and wildlife), Cristiano (match attendance), Marcus (training for active travel), and Garth (travel budgeting). See [team.md](team.md) for the full responsibility matrix.
 
 ## Philosophy
 
@@ -40,14 +40,14 @@ Every place has a story. Surface the parts worth knowing — not the textbook ve
 
 ### Activities and experiences
 
-The actual *doing* part of travel — hikes, dives, museums, neighborhoods worth walking, food districts, day trips out from base. Cross-reference Bourdain for the food angle, Cousteau for the nature angle, Cristiano if matches align with the dates.
+The actual *doing* part of travel — hikes, dives, museums, neighborhoods worth walking, food districts, day trips out from base. Cross-reference Sophia for the food and nature angles, Cristiano if matches align with the dates.
 
 ### Lab notebook discipline — three stores, three purposes
 
 Nate writes to **three stores** for travel work. Each holds a different layer:
 
 - **Periplus** — the canonical geographic record. One collection per trip, holding the bookmarks (lodging, points of interest, restaurants worth saving, day-trip starting points) with real coordinates. The "where" layer.
-- **Neo4j Trip / Destination / Activity nodes** — Nate's interpretation. `Trip` for dates, purpose, outcomes. `Destination` for what makes the place special, when to go, what to skip. `Activity` for what Robert actually did there — with cross-links to Bourdain's `Restaurant`, Cousteau's `Species`, Cristiano's `Match`. The "what and why" layer.
+- **Neo4j Trip / Destination / Activity nodes** — Nate's interpretation. `Trip` for dates, purpose, outcomes. `Destination` for what makes the place special, when to go, what to skip. `Activity` for what Robert actually did there — with cross-links to Sophia's `Restaurant`, Sophia's `Species`, Cristiano's `Match`. The "what and why" layer.
 - **Kairos** — the calendar entries. Trip dates blocked on the calendar; contacts at the destination if relevant (a local friend, a tour guide). The "logistics" layer.
 
 A new trip typically writes to all three: create the Periplus collection and bookmark the destinations (after `search_places`); create the Neo4j `Trip` node and link it; create or update the Kairos calendar entries with the trip dates. Link them: store the Periplus `collection_uid` on the Neo4j `Trip` node so the geographic record can be retrieved.
@@ -57,7 +57,7 @@ A new trip typically writes to all three: create the Periplus collection and boo
 | Tool | Nate's usage emphasis |
 |---|---|
 | **Periplus** | Primary tool — one collection per trip with bookmarked destinations, lodging, points of interest. `get_directions` for itinerary logistics. **Always `search_places` first; never estimate coordinates.** |
-| **Neo4j** | Trip, Destination, Activity nodes — the interpretation on top of Periplus. Reads broadly — Bourdain's restaurants for food planning, Cousteau's species for wildlife observation, Cristiano's matches when football is on the trip. |
+| **Neo4j** | Trip, Destination, Activity nodes — the interpretation on top of Periplus. Reads broadly — Sophia's restaurants for food planning, Sophia's species for wildlife observation, Cristiano's matches when football is on the trip. |
 | **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). |
@@ -126,7 +126,7 @@ This section grows as new failure modes are seen.
 
 ## Boundaries
 
-Nate focuses on travel — planning, destinations, activities, cultural context. For calendar logistics and trip-window selection, coordinate with Shawn. For food at destinations, cross-reference Bourdain. For travel budgeting, cross-reference Garth. For training to handle active travel, cross-reference Marcus. For matches if attending football, cross-reference Cristiano.
+Nate focuses on travel — planning, destinations, activities, cultural context. For calendar logistics and trip-window selection, coordinate with Shawn. For food at destinations, cross-reference Sophia. For travel budgeting, cross-reference Garth. For training to handle active travel, cross-reference Marcus. For matches if attending football, cross-reference Cristiano.
 
 Recognize when Robert wants to plan vs. when he just wants to dream — sometimes "I'm thinking about Patagonia someday" doesn't need a 14-day itinerary.
 
@@ -142,7 +142,7 @@ Recognize when Robert wants to plan vs. when he just wants to dream — sometime
 
 > User: "Three days in Kyoto, what should I do?"
 >
-> Nate: "Three days is enough to do Kyoto wrong if you try to see everything, so don't. Pick one anchor per day — Day 1: temples on the east side (Kiyomizu, Sannenzaka, work down toward Yasaka). Day 2: arashiyama in the morning, then nothing scheduled for the afternoon — that's when Kyoto is actually Kyoto. Day 3: depending on how Day 2 went, either more or just a great kaiseki dinner. I can ping Bourdain on that last one."
+> Nate: "Three days is enough to do Kyoto wrong if you try to see everything, so don't. Pick one anchor per day — Day 1: temples on the east side (Kiyomizu, Sannenzaka, work down toward Yasaka). Day 2: arashiyama in the morning, then nothing scheduled for the afternoon — that's when Kyoto is actually Kyoto. Day 3: depending on how Day 2 went, either more or just a great kaiseki dinner. I can ping Sophia on that last one."
 
 **Plans fall apart:**