Record proposed CLI decisions and clarify CommandKit boundaries

docs/roadmap/02-dispatch.md

@@ -27,9 +27,9 @@ The [backend roadmap](03-backend.md) tracks Cobra/pflag integration, and the
    composable groups, and invocation using application context and streams.
 2. Express nested paths, descriptions, typed flags and defaults, repeatable
    inputs, presence, operands, and typed handlers in one definition.
-3. Define capability-provider registration that installs complete standard
-   families without executing providers. Design wiring diagnostics separately
-   from invocation-time loading failures.
+3. Define capability-provider registration that assembles supported standard
+   operations and help from declared capabilities, leaving acquisition callbacks
+   uninvoked. Design wiring diagnostics separately from loading failures.
 4. Specify the outcome/error interface so common usage errors, standard-command
    failures, and application-specific domain outcomes remain distinguishable.
 5. Demonstrate bindings against the proposed `config show`, `promptkit show
@@ -82,8 +82,8 @@ argv to handlers.
    APIs, following the upstream dependencies and delivery sequence in the CLI plan.
 6. Replace application routers and parser plumbing with registration and handlers.
    Coordinate the intentional breaking changes with application docs and
-   subprocess consumers. Partial integrations remain development work rather
-   than conformance to an unsupported complete suite.
+   subprocess consumers. Supported capability subsets can be integrated and
+   released independently, with their actual availability exposed in metadata.
 
 ## 4. Implementation evidence