feat: AMP Integration — Bring Your Own Agent Memory

[mmorris35]

Problem

DevPlan MCP is stateless. Every session starts fresh with no memory of:

• Previous project analyses
• Lessons learned
• Wave execution history
• File dependency graphs

Adding hosted persistence would increase costs from $5/mo to $20-50+/mo for a free tool.

Solution

Bring Your Own AMP (Agent Memory Protocol)

• DevPlan MCP Worker stays stateless ($5/mo) ✓
• Users run their own AMP endpoint (Nellie on localhost)
• Memory lives client-side at $0 cost to DevPlan

Claude Code → DevPlan MCP (CF Worker) → User's Local AMP (Nellie)
                    ↓
              Stateless, cheap            Persistent, user-owned

Features

Config Schema

amp:
  enabled: true
  endpoint: "local"  # localhost:8765, or remote URL
  persist:
    plans: true
    lessons: true
    wave_history: true
    file_graphs: true  # For wave planner (#131)

What Gets Persisted

• Project plans and analysis
• Lessons learned (searchable)
• Wave execution history
• File dependency graphs (enables smart wave planning)

CLI Commands

devplan amp status          # Check connection
devplan lessons search "merge conflicts"
devplan plans list

Benefits

1. $0 hosting cost — Memory is client-side
2. Privacy — Project data never leaves user's machine
3. Offline-capable — Works without internet
4. Federated (future) — Optional MESH for community sharing

Spec

Full specification: docs/amp-integration-spec.md (PR #TBD)

Dependencies

• Nellie extensions for DevPlan-specific tools
• Config file loading in CLI
• AmpClient with retry/fallback logic

Related

• feat: Wave Planner - file-aware parallel agent orchestration #131 — Wave Planner (uses file graphs from AMP)