Establish native CommandKit command composition

This commit is contained in:
2026-11-20 03:35:49 +00:00
parent 83d33777e7
commit 26ac62fbb7
8 changed files with 239 additions and 21 deletions

View File

@@ -152,6 +152,20 @@ filesystem hardening is requested.
## Stage 1: Select Released Dependencies And Establish Command Composition
**Status: Complete.** Selected CommandKit v0.7.0
(`b57bfe176cff05a892e6cb07ebb5f350239e55d4`), ckconfig v0.9.0
(`9962368f0c1ea1f6ad010638e94621091105d745`), and ckprompt v0.10.0
(`c9a56e1b15f2169881a91fca4e1f4a1c475e057a`); retained ConfigKit v1.2.1,
PromptKit v0.23.3, Go minimum 1.27.0, and validation toolchain 1.27.4.
Native composition now owns dispatch and finalization; application acquisition
and command effects remain explicit unfinished callbacks for subsequent work.
Verified configuration-free help/version/scope discovery and Bash/Zsh/Fish
completion, all-package test compilation, tidy module metadata, linked dependency
selection (including Windows-only mousetrap), and release notice paths.
Full behavioral checks remain deferred to Stage 9: the old CLI integration tests
still describe the retired interface, and the new application handlers are not
yet implemented. No compatibility dispatch was retained.
**Primary files:** `go.mod`, `go.sum`, `internal/adapter/cli` composition,
`docs/oss/attribution.md`, and applicable `docs/oss/licenses/` texts.