Clarify the internal adapter and handler ownership boundary

This commit is contained in:
2026-10-07 18:28:44 +00:00
parent 8b6835b84b
commit e421099de6
2 changed files with 15 additions and 10 deletions

View File

@@ -13,18 +13,21 @@ provider adapters. Configuration reports adapt ConfigKit's public records and
writers. PromptKit scope and definition handlers use PromptKit's public
inspection methods and map their results to CommandKit-owned reports.
The root package imports `internal/cobra` to bridge its command declarations and
invocations to Cobra parsing and routing. Application callbacks, output streams,
context, and supported error identity cross that bridge through the root's typed
contracts.
The root lowers registered command metadata into the internal adapter's neutral
bridge. The adapter returns raw parsed values and neutral syntax-failure data;
the root prepares typed input, invokes application/standard handlers, and
coordinates outcomes and diagnostic delivery. Application callbacks and their
supported error identity remain in the root's typed contracts rather than
crossing the backend bridge. Context and streams are passed to the adapter for
its parsing and help operations.
## `internal/cobra`
This package owns the Cobra-specific command tree and argument/flag parsing
adapter. It translates neutral command metadata and parsed values into a bridge
This package owns the Cobra-specific command tree, argument/flag parsing,
and help rendering. It translates neutral command metadata and parsed values into a bridge
result consumed by the root package. It does not import `commandkit` and does not
own registry policy, public command declarations, provider loading, or report
rendering.
own registry policy, public command declarations, provider loading, or standard
inspection report rendering.
## External implementation boundaries