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

Plan PromptKit implementation stages

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-12 01:40:15 +00:00
parent 20e19b9569
commit d825538921
4 changed files with 453 additions and 648 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/roadmap/promptkit.md
View File

@@ -30,8 +30,9 @@ and [ADR 0012](../adr/0012-typed-configuration-comparison-pairs.md) govern captu
declarations and input/state lifetimes. Existing deliberately selected contracts
control; prototype implementation shapes receive no compatibility preference.
This roadmap defines the selected end state. A later implementation plan should
sequence the work. The present pass updates only this roadmap.
This roadmap defines the selected end state. The
[implementation plan](implementation.md) assigns the ordered work and records
stage completion evidence.
## Current baseline
@@ -140,9 +141,11 @@ construction errors remain attached when capabilities are narrowed.
For the bundled adapter, retain diagnostics from each reached load or inspection,
identify left/right context and native source legends, keep left diagnostics if
right acquisition fails, and keep both sides' diagnostics if comparison fails.
Use existing cancellation checks at operation boundaries and finish report
preparation before delivery. The upstream Diff method is synchronous and takes
no context; do not promise interruption inside it or transactional writer output.
Capture completed inspection diagnostics before honoring cancellation observed
after a successful load. Use cancellation checks at operation boundaries and
finish report preparation before delivery. The upstream Diff method is
synchronous and takes no context; do not promise interruption inside it or
transactional writer output.
Equal selections alone do not skip the pair provider or the bundled adapter's
reached loader calls. Application caches determine whether calls construct new
@@ -310,11 +313,6 @@ serialization of an upstream Go struct does not define the CLI schema.
- Extend `ConfigScope` with the native PromptKit comparison provider, retaining
ordinary acquisition and appropriate side diagnostics. Route results through
the existing ckconfig comparison implementation.
- Adapt diagnostic acquisition for comparison deliberately. The current
`loadPromptKitEngine` helper uses a single `promptkit` scope label and can
return on cancellation before collecting inspection diagnostics. Account for
side labels, source legends, and retained diagnostics at failure and
cancellation boundaries when reusing or adjusting it.
- Extend `Suite`, `FromEngine`, and family assembly for independent prompt/profile
catalog providers. Use core declarations and typed binding composition for
selection and input preparation; add no second parser.
@@ -350,7 +348,8 @@ serialization of an upstream Go struct does not define the CLI schema.
- Establish compatibility through relevant module suites, maintained consumers,
and workspace-off dependency/import checks. Local replacements for unpublished
CommandKit prerequisites prove local-source compatibility, not availability of
future tags. These checks belong to implementation, not this prose-only pass.
future tags. The [implementation plan](implementation.md) owns the validation
assignments and evidence.
## Scope limits and completion