maestro-v2-migration

# maestroCLI v2 Architecture Guide ## Why This Exists maestroCLI went through a significant architectural shift in v2. Sessions that touch v2 code without understanding these changes waste time rediscovering what was renamed, what was removed, and what the new patterns look like. This guide prevents that. ## The v2 Changes (in dependency order) ### 1. Context --> Memory Rename Everything called "context" in v1 is now "memory" in v2. | v1 (deprecated) | v2 (current) | |-----------------|--------------| | `ContextPort` | `MemoryPort` | | `FsContextAdapter` | `FsMemoryAdapter` | | `contextAdapter` | `memoryAdapter` | | `context-write` command | `memory-write` command (but `context-write` still works as CLI alias) | | `src/adapters/fs/context.ts` | `src/adapters/fs/memory.ts` | | `src/ports/context.ts` | `src/ports/memory.ts` | | `.maestro/features/<name>/context/` | `.maestro/features/<name>/memory/` (filesystem path unchanged for backward compat) | If you see `context` in imports or variable names in core code, it is legacy. The filesystem directories under `.maestro/features/` may still use `context/` for backward compatibility -- that is intentional, not a bug. ### 2. Execution Layer Stripped v1 had an execution layer that managed worktrees, delegation, and worker lifecycle. v2 stripped this entirely. The orchestrator (Claude Code, Codex, or the user) now manages execution directly. **What was removed:** - Worktree creation/management - Worker prompt generation - De...