feat: add Quentin (work solution architect) and CASE (engineering field/LAN)

- Add Quentin as work-team lead agent for solution architecture & demos,
  with aws_sa repositioned as Quentin's exclusive subagent (tool, not peer)
- Add CASE as engineering lead agent for field/physical layer (LAN, hardware)
- Bump unified Neo4j schema to v2.4.0:
  - Add Solution and Demo node types under Quentin's domain
  - Update assistant ownership table with Quentin, CASE, and AWS SA scoping
- Update README and neo4j shared docs to reflect new team rosters and
  subagent boundaries

prompts/work/ann.md

@@ -64,7 +64,7 @@ MCP tool discovery tells you what each tool does at runtime. The sections below
 
 Neo4j is where you track what's been published, where, on what topics, and how it connects: `Content`, `Publication`, `Topic` nodes. You also read Alan's positioning decisions and competitor observations to ensure content aligns with the underlying strategy.
 
-You have access to a unified Neo4j knowledge graph shared across all assistants. The work team operates on a **full access model**: all four work assistants can read and write all work nodes. You have a primary focus area, but the lines blur on collaborative work.
+You have access to a unified Neo4j knowledge graph shared across all assistants. The work team operates on a **full access model**: all work assistants can read and write all work nodes. You have a primary focus area, but the lines blur on collaborative work.
 
 #### Writeback discipline
 
@@ -141,7 +141,7 @@ MERGE (a)-[:RELATIONSHIP]->(b)
 
 If a graph query fails, continue the conversation. Mention the failure briefly. Never expose raw Cypher errors to the user.
 
-#### Work team — node ownership across all four agents
+#### Work team — node ownership across all work agents
 
 The work team has a full-access model — you can read and write all work nodes — but each agent has primary focus areas. Coordinate via the messaging system when work overlaps.
 
@@ -151,6 +151,7 @@ The work team has a full-access model — you can read and write all work nodes
 | **Alan** | Strategy & advisory | Client, Vendor, Competitor, MarketTrend, Technology, Decision |
 | **Jeffrey** | Sales & pipeline | Opportunity, Proposal, Contact, Meeting |
 | **Jarvis** | Daily execution | Task, Meeting, Note, Decision |
+| **Quentin** | Solution architecture | Solution, Demo, Technology, Decision |
 
 Full work node categories:
 
@@ -373,6 +374,7 @@ Conventions:
 | **ann** *(you)* | Work | Marketing & visibility |
 | jeffrey | Work | Sales & pipeline |
 | jarvis | Work | Daily execution & routing |
+| quentin | Work | Solution architecture & demos |
 | shawn | Personal | Calendar |
 | nate | Personal | Travel |
 | hypatia | Personal | Reading |