Complete CommandKit consumer documentation
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Initial CommandKit implementation plan
|
||||
|
||||
Status: implementation underway; Stages 1-13 complete and Stage 14 pending.
|
||||
Status: implementation complete; Stages 1-14 complete.
|
||||
|
||||
Date: 2026-10-07.
|
||||
|
||||
@@ -818,7 +818,7 @@ selection errors, optional capabilities, and help without engine construction.
|
||||
|
||||
## Stage 14: substantiate consumer fit and complete documentation
|
||||
|
||||
**Status:** pending. **Prerequisite:** Stage 13.
|
||||
**Status:** complete. **Prerequisite:** Stage 13.
|
||||
|
||||
1. Add complete maintained examples using only the public root API and published
|
||||
upstream packages. Use two ordinary example directories (separate Go main
|
||||
@@ -860,8 +860,12 @@ selection errors, optional capabilities, and help without engine construction.
|
||||
into the implementation. Record completed stage status and checks, then commit
|
||||
the completed unit under the local policy. Publishing remains separate work.
|
||||
|
||||
**Completion evidence:** each included roadmap feature has observable behavior
|
||||
and its appropriate checks; examples compile and use the real public dispatcher;
|
||||
default tests do not require real services/credentials; documents describe only
|
||||
implemented contracts. The final report identifies the commits, checks, and
|
||||
deferred capabilities without claiming downstream migrations or release completion.
|
||||
**Completion evidence:** added maintained `examples/simple` and
|
||||
`examples/composed` consumers, public consumer guidance, internal architecture
|
||||
overview, and updated CLI/development/README/feature-roadmap documentation. The
|
||||
examples compile and use the public dispatcher with synthetic data. Shared
|
||||
selector helpers serve both configuration suites. Reviewed exported declarations,
|
||||
root and adapter imports, dependency replacements, attribution, and retained
|
||||
deferred feature IDs. Verified with `gofmt`, `go test ./...`, `go mod tidy -diff`,
|
||||
document link checks, example smoke commands, and `git diff --check`. Publishing,
|
||||
downstream migrations, and deferred capabilities remain outside this stage.
|
||||
|
||||
@@ -1,16 +1,25 @@
|
||||
# Initial CommandKit feature roadmap
|
||||
|
||||
Status: selected initial implementation target; unimplemented.
|
||||
Status: selected initial implementation target; implemented.
|
||||
|
||||
Date: 2026-10-07.
|
||||
|
||||
## Purpose and authority
|
||||
|
||||
This document defines the selected end state of the initial library: packages,
|
||||
features, integration contracts, dependencies, and completion evidence. It is
|
||||
prepared using [the agreed checklist](initial-plan.md). Implementation steps belong
|
||||
in [the implementation plan](implementation.md). This document describes the target
|
||||
state; CommandKit currently has no Go module or dispatcher implementation.
|
||||
This document defines the selected initial target for the library: packages,
|
||||
features, integration contracts, dependencies, and completion evidence. It was
|
||||
prepared using [the agreed checklist](initial-plan.md). Implementation steps and
|
||||
stage evidence belong in [the implementation plan](implementation.md). The
|
||||
included target is implemented; the table below records feature status.
|
||||
|
||||
| Included feature IDs | Status | Evidence |
|
||||
| --- | --- | --- |
|
||||
| API-01, REG-01, INPUT-01, BACK-01, INV-01, OUT-01 | complete | Root API and dispatcher tests; `go test ./...`. |
|
||||
| HELP-01, VER-01 | complete | Help/version behavior tests; `go test ./...`. |
|
||||
| INT-01, CFG-01–05 | complete | Configuration scope, validation, show, sources, and explain tests; `go test ./...`. |
|
||||
| PK-01 | complete | PromptKit scope adapter tests; `go test ./...`. |
|
||||
| PK-02, PK-03 | complete | Prompt/profile inspection tests; `go test ./...`. |
|
||||
| DIFF-01, CAT-01 | deferred | Require upstream safe snapshot and catalog APIs; see [deferred capability targets](#deferred-capability-targets). |
|
||||
|
||||
The [architecture policy](../policy/architecture.md) and nine accepted ADRs control
|
||||
this roadmap. The delivery scope, typed API model, selector/report behavior, and
|
||||
@@ -63,11 +72,10 @@ module still declares the dependencies used by its bundled helpers.
|
||||
| PromptKit definitions | `promptkit show prompt` and `promptkit show profile`, including effective `ExtraParams` |
|
||||
| Application commands | Typed custom leaf commands, nested groups, and groups with their own runnable handler |
|
||||
|
||||
Defer catalog listing and semantic comparison until the owning libraries expose
|
||||
the required public contracts. These accepted standard operations remain future
|
||||
implementation targets. Their absence must appear accurately in help and
|
||||
capabilities. Initial delivery uses the current released inspection APIs; upstream
|
||||
snapshot/catalog enhancements are separate follow-up work.
|
||||
Catalog listing and semantic comparison remain deferred until the owning
|
||||
libraries expose the required public contracts. Their absence appears accurately
|
||||
in help and capabilities. The implemented target uses the released inspection
|
||||
APIs; upstream snapshot/catalog enhancements are separate follow-up work.
|
||||
|
||||
This scope provides meaningful configuration inspection immediately and avoids
|
||||
requiring an initial consumer migration to wait for every future capability.
|
||||
|
||||
Reference in New Issue
Block a user