Implement Phase 2 & 3: Complete HAP Terminal Interface with Patch Management

🎭 Phase 2: HAP Terminal Interface Implementation
✅ **Core Terminal Interface**: Interactive command-driven HAP terminal with help system
✅ **HMMM Message Composition System**:
   - New reasoning messages, thread replies, network queries, decision proposals
   - Complete message metadata handling (topics, threads, timestamps)
✅ **UCXL Context Browsing System**:
   - Address parsing, content retrieval from DHT encrypted storage
   - Search functionality, content creation, history navigation
✅ **Decision Participation System**:
   - Active decision listing, decision details with voting status
   - Vote casting with reasoning, decision proposals, HMMM integration

🔧 Phase 3: Enhanced Human Workflows
✅ **Patch Creation and Submission Workflows**:
   - Complete patch lifecycle management (create, review, submit, track)
   - Multiple patch types (context, code, config, docs)
   - UCXL integration with DHT storage, HMMM coordination
✅ **Time-Travel Diff Support**:
   - Temporal navigation operators (~~<n>, ^^<n>, @<time>)
   - Decision-hop analysis, visual diff display, version comparison

🏗️ **Architecture Highlights**:
- **Multi-binary structure**: Separate chorus-agent and chorus-hap binaries
- **Shared P2P runtime**: Both binaries use identical libp2p, DHT, HMMM, UCXL systems
- **Interactive sub-shells**: Dedicated command environments for HMMM, UCXL, patches, decisions
- **Network integration**: All features connect to distributed P2P agent network
- **Human-agent parity**: Humans participate as first-class network citizens

📦 **New Files**:
- internal/hapui/terminal.go: Complete HAP terminal interface (2400+ lines)
- prompts/human-roles.yaml: Role-based prompt configuration
- docs/decisions/*: HAP conversion decision record

🔗 **Integration Points**:
- HMMM: Collaborative reasoning and patch/decision announcements
- UCXL: Context addressing and version management
- DHT: Distributed storage of patches and content
- Decision System: Formal approval and consensus workflows

The HAP terminal interface now provides comprehensive human portal into the CHORUS
autonomous agent network, enabling collaborative reasoning, context sharing, patch
management, and distributed decision-making between humans and AI agents.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

docker/docker-compose.prompts.dev.yml

@@ -0,0 +1,36 @@
+version: "3.9"
+
+services:
+  chorus-agent:
+    # For local dev, build from repo Dockerfile; alternatively set a pinned image tag
+    build:
+      context: ..
+      dockerfile: docker/Dockerfile
+    # image: registry.home.deepblack.cloud/chorus/agent:0.1.0
+    container_name: chorus-agent-dev
+    env_file:
+      - ./chorus.env
+    environment:
+      # Prompt sourcing (mounted volume)
+      CHORUS_PROMPTS_DIR: /etc/chorus/prompts
+      CHORUS_DEFAULT_INSTRUCTIONS_PATH: /etc/chorus/prompts/defaults.md
+      CHORUS_ROLE: arbiter # change to your role id (e.g., hmmm-analyst)
+
+      # Minimal AI provider config (ResetData example)
+      CHORUS_AI_PROVIDER: resetdata
+      RESETDATA_BASE_URL: https://models.au-syd.resetdata.ai/v1
+      # Set RESETDATA_API_KEY via ./chorus.env or secrets manager
+
+      # Required license id (bind or inject via env_file)
+      CHORUS_LICENSE_ID: ${CHORUS_LICENSE_ID}
+
+    volumes:
+      # Mount prompts directory read-only
+      - ../prompts:/etc/chorus/prompts:ro
+    ports:
+      - "8080:8080"  # API
+      - "8081:8081"  # Health
+      - "9000:9000"  # P2P
+    restart: unless-stopped
+    # profiles: [prompts]
+