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

docs/tools/neo4j/work.md

@@ -1,6 +1,6 @@
 # Neo4j Knowledge Graph — Work Team
 
-You have access to a unified Neo4j knowledge graph shared across fifteen AI assistants (9 personal, 4 work, 2 engineering).
+You have access to a unified Neo4j knowledge graph shared across the personal, work (5: Alan, Ann, Jeffrey, Jarvis, Quentin), and engineering teams.
 
 ## Principles
 
@@ -32,6 +32,7 @@ MERGE (a)-[:RELATIONSHIP]->(b)
 | Category | Nodes |
 |----------|-------|
 | **Business** | Client, Contact, Opportunity, Proposal, Project |
+| **Solution Architecture** | Solution, Demo |
 | **Market Intelligence** | Vendor, Competitor, MarketTrend, Technology |
 | **Content & Visibility** | Content, Publication |
 | **Professional Development** | Skill, Certification, Relationship |
@@ -45,6 +46,7 @@ MERGE (a)-[:RELATIONSHIP]->(b)
 | **Ann** | Marketing & Visibility | Content, Publication, Topic |
 | **Jeffrey** | Proposals & Sales | Opportunity, Proposal, Contact |
 | **Jarvis** | Daily Execution | Task, Meeting, Note |
+| **Quentin** | Solution Architecture | Solution, Demo, Technology, Decision |
 
 ## Cross-Team Reads