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

Plan dependency upgrades and PromptKit diagnostics

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-17 18:10:34 +00:00
parent 38b49f29fb
commit 29582dd6b7
2 changed files with 750 additions and 546 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1272
docs/roadmap/implementation.md
View File

File diff suppressed because it is too large Load Diff

24
docs/roadmap/upgrades.md
View File

@@ -3,7 +3,7 @@
Status: adoption roadmap; implementation has not started. The release targets, Status: adoption roadmap; implementation has not started. The release targets,
adoption order, and OD-1 through OD-4 are accepted. Smoke testing is included adoption order, and OD-1 through OD-4 are accepted. Smoke testing is included
in the current scope. This document defines the desired end state and required in the current scope. This document defines the desired end state and required
work; a separate implementation plan will sequence coding tasks. work; the [implementation plan](implementation.md) sequences coding tasks.
## Purpose and authority ## Purpose and authority
@@ -43,7 +43,8 @@ outcomes. ckconfig owns the configuration family. ckprompt currently supplies
prompt/profile catalogs, named inspection, requirements discovery, and concrete prompt/profile catalogs, named inspection, requirements discovery, and concrete
request validation; its engine configuration scope is composed through ckconfig. request validation; its engine configuration scope is composed through ckconfig.
The completed requirements roadmap, implementation plan, and remediation record The completed requirements roadmap and remediation record, together with their
[original implementation plan](https://gitea.maximumdirect.net/eric/CommandKit/src/commit/38b49f29fb3a8f22ff02528d2a0ed413e5c6ab1e/docs/roadmap/implementation.md),
remain historical evidence for the delivered baseline. This roadmap describes remain historical evidence for the delivered baseline. This roadmap describes
new work and does not restart those completed assignments. new work and does not restart those completed assignments.
@@ -58,18 +59,13 @@ Reviewed upstream references:
All three releases retain Go 1.26.0 as their consumer minimum. The adoption does All three releases retain Go 1.26.0 as their consumer minimum. The adoption does
not require changing CommandKit's Go minimum or selected release toolchain. not require changing CommandKit's Go minimum or selected release toolchain.
## Adoption order and delivery boundaries ## Dependency and delivery boundaries
| Order | Adoption | Reason | The target includes all three upgrades, richer configuration source inspection,
| --- | --- | --- | expanded PromptKit discovery, and explicitly invoked smoke testing. The
| First | ReleaseKit v0.4.2 | A small, independent maintainer-tool update establishes the selected tool before integration migration. | [implementation plan](implementation.md) owns coding order and stage boundaries.
| Next | ConfigKit v0.8.0, including richer source inspection | Supplies the prerequisite for PromptKit v0.16.0 and exposes useful native evidence through ckconfig. | These changes can be delivered in one coordinated sprint without separately
| Then | PromptKit v0.16.0 API/configuration migration | Removes obsolete version selectors and bundled-catalog assumptions across ckprompt. | releasable intermediate commits.
Expanded PromptKit discovery and explicitly invoked smoke testing are included
after its base migration. These are product/dependency relationships, not a staged
implementation plan or a requirement for separately releasable intermediate
commits. ConfigKit and PromptKit can be handled in one coordinated sprint.
ReleaseKit has no runtime ordering dependency on the other two. ConfigKit must ReleaseKit has no runtime ordering dependency on the other two. ConfigKit must
be adopted before, or atomically with, PromptKit: Go module selection would be adopted before, or atomically with, PromptKit: Go module selection would
@@ -201,7 +197,7 @@ its native scope. Migration guidance should link to the upstream
### Expanded operator discovery ### Expanded operator discovery
After the base migration, extend the existing optional family with: The optional family exposes these additional catalogs:
| Operation | Native capability | | Operation | Native capability |
| --- | --- | | --- | --- |