Milestones
List view
## Goal Make NestM a first-class MCP client host with composable client-role capabilities, observable lifecycle state, safe recovery, and production-grade outbound policy while preserving the official SDK as the protocol engine. ## Scope - Capability contributions and strict advertise/enforce validation - Nest-native elicitation and catalog-change providers - Runtime events, typed failures, subscription supervision, and availability policy - Mandatory outbound authorization, approvals, and concurrency controls - Static module and dynamic manager parity - Optional Tasks extension, legacy transport compatibility, testing support, and documentation ## Delivery principles - Advertise only capabilities with a complete installed handler path. - Treat elicitation as the primary current client feature; keep sampling, roots, and protocol logging compatibility-only. - Never replay non-idempotent operations by default. - Partition state and policy by server and authorization context. - Model modern connections around peer configuration, requests, subscriptions, and durable task IDs rather than transport sessions. - Use public SDK APIs and immutable provider-resolved configuration. ## Exit criteria - Every milestone issue is complete and its dependency relationship is satisfied. - New behavior has focused unit, integration, race, shutdown, and interoperability coverage. - Static Nest configuration and dynamically managed generations share the same client-role semantics. - Public APIs, migration guidance, security guidance, and runnable examples are documented.
No due date•0/13 issues closed