base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Verify and complete alias implementation

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-19 20:02:07 +00:00
parent 42d9989533
commit a54a9354b1
3 changed files with 22 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/roadmap/aliases.md
View File

@@ -1,8 +1,8 @@
# Application-owned aliases
Status: command- and flag-alias behavior and consumer API direction accepted;
implementation has not started. OD-1 through OD-6 are resolved. This roadmap
records the target and selected behavior. The
Status: implementation complete; core v0.3.0 release note prepared and
publication pending. OD-1 through OD-6 are resolved. This roadmap records the
target and selected behavior. The
[staged implementation plan](implementation.md) owns delivery sequencing and
stage-specific validation.
[ADR 0013](../adr/0013-application-alias-routing.md) records the accepted

16
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Application-owned aliases implementation plan
Status: in progress; Stages 1–14 completed.
Status: complete; Stages 1–17 completed.
## Authority, baseline, and scope
@@ -815,6 +815,20 @@ boundary, the selected checks pass against local source, documentation matches
the implementation, and no unresolved feature decisions or implementation work
remain. Publishing and dependent-version availability are separate operations.
**Completed:** All workspace suites passed on Go 1.26.8: root, ckconfig, and
ckprompt, including maintained examples. Independent `GOWORK=off` checks also
passed for all three modules using the root module graph and disposable local
source replacements; only replacement directives changed in temporary module
files, with no sum changes. The final review confirmed core has no optional
integration dependency, backend imports remain internal, integration factories
return canonical commands, and alias composition is covered without provider
loads during help. Routing, flag interpretation, help, diagnostics, identity,
installation recovery, typed bindings, and consumer composition are covered by
the focused evidence recorded in Stages 1–14. Documentation links and
candidate-note paths resolve; prose whitespace checks passed. The alias feature
roadmap now records completed implementation while leaving core publication
and dependent integration release preparation separate.
## Target evidence index
| Accepted behavior | Primary stages |