feat(services): add service discovery infrastructure with NATS + Supabase integration

.claude/context/mcp-api.md

@@ -394,13 +394,104 @@ MCP activity is logged to NATS subjects:
 - Completion events
 - Error notifications
 
+## Persona-Based Agent Creation
+
+**NEW:** `POST /mcp/subordinate/create-with-persona`
+
+Create a subordinate agent from a persona configuration stored in Supabase. Personas define agent behavior, tools, and personality.
+
+```bash
+curl -X POST http://localhost:8080/mcp/subordinate/create-with-persona \
+  -H "Authorization: Bearer $MCP_CLIENT_SECRET" \
+  -H "Content-Type: application/json" \
+  -d '{
+    "persona_id": "uuid",
+    "context_allocation": 0.3,
+    "parent_agent_id": "agent-0",
+    "overrides": {
+      "model": "claude-opus-4-5",
+      "temperature": 0.5
+    },
+    "enhancement_ids": ["uuid1", "uuid2"],
+    "create_subordinate": true
+  }'
+```
+
+**Request Parameters:**
+- `persona_id` (required): UUID of persona from Supabase `pmoves_core.personas`
+- `context_allocation` (optional): Context window allocation (0.0-1.0, default: 0.3)
+- `parent_agent_id` (optional): Parent agent for subordinate relationship
+- `overrides` (optional): Runtime parameter overrides (model, temperature, max_tokens, tools)
+- `enhancement_ids` (optional): Specific enhancement IDs to apply
+- `create_subordinate` (optional): Whether to create the agent (default: true)
+
+**Response:**
+```json
+{
+  "agent_id": "agent-2",
+  "config": {
+    "name": "Developer",
+    "specialization": "Software engineering specialist for PMOVES.AI",
+    "thread_type": "chained",
+    "model": "claude-sonnet-4-5",
+    "temperature": 0.3,
+    "max_tokens": 4096,
+    "tools": ["git", "code-review", "testing", "documentation"],
+    "behavior_weights": {"decode": 0.3, "retrieve": 0.4, "generate": 0.3},
+    "nats_subscriptions": ["claude.code.tool.executed.v1"],
+    "grounding_packs": ["pmoves-architecture@1.0", "python-patterns@1.0"]
+  },
+  "persona": {
+    "persona_id": "uuid",
+    "name": "Developer",
+    "version": "1.0",
+    "thread_type": "chained"
+  },
+  "enhancements_applied": [
+    {"enhancement_id": "uuid1", "type": "tool", "name": "code-review-access"}
+  ]
+}
+```
+
+### Thread Types
+
+Personas support different orchestration patterns via `thread_type`:
+
+| Thread Type | Description | Use Case | Coordination |
+|-------------|-------------|----------|--------------|
+| `base` | Single agent, single task | Simple queries, direct actions | none |
+| `parallel` | Multiple independent agents | Multi-source research, concurrent tasks | result_aggregation |
+| `chained` | Sequential agent handoff | Multi-step workflows, validation pipelines | sequential_handoff |
+| `fusion` | Collaborative single output | Complex analysis, consensus building | collaborative_merge |
+| `big` | Large context orchestration | Complex projects, architectural design | central_planner |
+| `zero_touch` | Fully automated execution | Background tasks, scheduled operations | event_driven |
+
+### Persona Management Endpoints
+
+**`GET /api/persona/list`** - List available personas
+```bash
+curl http://localhost:8080/api/persona/list?active_only=true&thread_type=chained
+```
+
+**`GET /api/persona/{persona_id}`** - Get persona details
+```bash
+curl http://localhost:8080/api/persona/{uuid}
+```
+
+**`GET /api/persona/enhancements/{persona_id}`** - Get persona enhancements
+```bash
+curl http://localhost:8080/api/persona/enhancements/{uuid}
+```
+
 ## Future MCP Enhancements
 
 Planned features:
 - **Streaming responses** - Real-time task progress via SSE
 - **Batch operations** - Submit multiple tasks in one call
 - **Agent scheduling** - Schedule tasks for future execution
 - **Agent pools** - Dedicated agent groups for specific workloads
+- **Persona versioning** - A/B test different persona versions
+- **Persona analytics** - Track persona performance metrics
 
 ## Developer Notes
 

.claude/context/submodule-workflow.md

@@ -0,0 +1,167 @@
+# PMOVES.AI Submodule Workflow
+
+This document describes the proper workflow for working with PMOVES.AI submodules.
+
+## Branch Strategy
+
+### Branch Flow
+```
+feature work → PMOVES.AI-Edition-Hardened-v3-clean → PMOVES.AI-Edition-Hardened → main
+```
+
+1. **PMOVES.AI-Edition-Hardened-v3-clean** - Staging branch for features
+   - All feature work targets this branch first
+   - Once verified and stable, merges to PMOVES.AI-Edition-Hardened
+
+2. **PMOVES.AI-Edition-Hardened** - Production-ready hardened branch
+   - Only receives merges from v3-clean after verification
+   - More conservative, stable deployments
+
+3. **main** - Latest stable release
+   - Receives merges from hardened branch after full testing
+
+### Submodule Branch Strategy
+- Each submodule fork has a `PMOVES.AI-Edition-Hardened` branch
+- Submodules are custom forks for PMOVES.AI integration
+- Nested submodules exist (e.g., PMOVES-DoX contains PMOVES-Agent-Zero)
+
+## Submodule Workflow
+
+### Key Principle: Work IN Submodules, Not Worktrees
+
+**DO:**
+- Work directly in the submodule directory
+- Commit changes to the submodule's hardened branch
+- Push to submodule's origin repository
+- Then update main repo submodule reference
+
+**DON'T:**
+- Create worktrees in main repo for submodule work
+- Modify submodule files from main repo worktrees
+- Commit submodule changes through main repo
+
+### Correct Workflow Example
+
+```bash
+# 1. Work in the submodule
+cd PMOVES-Archon
+# Make changes...
+git add .
+git commit -m "feat: add new feature"
+git push origin PMOVES.AI-Edition-Hardened
+cd ..
+
+# 2. Update main repo reference
+git add PMOVES-Archon
+git commit -m "chore(submodules): Update PMOVES-Archon reference"
+git push origin feature/my-feature
+```
+
+### Incorrect Pattern (Avoid This)
+
+```bash
+# DON'T DO THIS - Creates worktree for submodule work
+git worktree add PMOVES-Archon pmoves-archon-feature
+# Work in worktree...
+# This breaks submodule workflow!
+```
+
+## Directory Structure
+
+### Top-Level PMOVES-* Directories
+These are submodules (custom forks):
+- `PMOVES-Archon/` - Agent knowledge management
+- `PMOVES-Agent-Zero/` - Agent orchestrator
+- `PMOVES-BoTZ/` - BoTZ framework
+- `PMOVES-Creator/` - Content creation
+- `PMOVES-Deep-Serch/` - Deep research orchestrator
+- `PMOVES-DoX/` - Document processing
+- `PMOVES-HiRAG/` - Hybrid RAG system
+- `PMOVES-Jellyfin/` - Media integration
+- `PMOVES-Open-Notebook/` - Knowledge base integration
+- `PMOVES-Pipecat/` - Voice communication
+- `PMOVES-Remote-View/` - Remote viewing
+- `PMOVES-Tailscale/` - VPN integration
+- `PMOVES-ToKenism-Multi/` - Tokenism framework
+- `PMOVES-Wealth/` - Wealth tracking
+- `PMOVES.YT/` - YouTube integration
+- `PMOVES-A2UI/` - A2UI integration
+- `PMOVES-n8n/` - Workflow automation
+
+### Integration Directories
+- `pmoves/integrations/archon/` - Archon integration point
+- `pmoves/vendor/*` - Vendored dependencies
+
+## Nested Submodules
+
+Some PMOVES submodules contain their own nested submodules:
+- **PMOVES-DoX** contains PMOVES-Agent-Zero (hardened variant)
+- These nested submodules have `PMOVES.AI-Edition-Hardened` branches
+
+When working with nested submodules:
+1. Navigate to the parent submodule first
+2. Update nested submodule from within parent
+3. Commit parent submodule changes
+4. Update main repo reference
+
+## Common Patterns
+
+### Adding a New Submodule
+```bash
+git submodule add -b PMOVES.AI-Edition-Hardened \
+  https://github.com/POWERFULMOVES/PMOVES-NewSubmodule.git \
+  PMOVES-NewSubmodule
+```
+
+### Updating Submodule References
+```bash
+# After submodule changes are pushed
+git submodule update --remote --recursive
+git add PMOVES-Submodule
+git commit -m "chore(submodules): Update PMOVES-Submodule reference"
+```
+
+### Checking Submodule Status
+```bash
+git status                    # Show modified submodules
+git submodule status          # Detailed submodule status
+git diff PMOVES-Submodule     # Show submodule diff
+```
+
+## Troubleshooting
+
+### Submodule Shows as "Modified Content"
+This means the submodule has uncommitted changes OR is on a different commit than expected.
+
+**Solution:**
+```bash
+cd PMOVES-Submodule
+git status                    # Check what's changed
+# Either commit changes or reset to expected commit
+git checkout PMOVES.AI-Edition-Hardened
+cd ..
+```
+
+### Untracked PMOVES-* Directories
+If PMOVES-* directories show as untracked but should be submodules:
+
+**Solution:**
+```bash
+git submodule sync --recursive
+git submodule update --init --recursive
+```
+
+### Worktree Conflicts
+If you accidentally created a worktree for submodule work:
+
+**Solution:**
+```bash
+git worktree remove incorrect-worktree
+git branch -D incorrect-branch
+```
+
+## See Also
+
+- `.gitmodules` - Complete submodule configuration
+- `.claude/context/submodules.md` - Submodule catalog
+- `.claude/context/ci-runners.md` - CI/CD runner configuration