Complete ConfigKit adoption validation
This commit is contained in:
@@ -2,10 +2,11 @@
|
||||
|
||||
## Status And Intent
|
||||
|
||||
Drafted on 2026-11-17. The maintainer selected an interim ConfigKit v1.2.0
|
||||
upgrade, followed by ConfigKit v1.2.1 as part of the upcoming PromptKit upgrade.
|
||||
This roadmap describes that interim target and the changes needed to reach it;
|
||||
it is not an implementation plan or a claim that the upgrade has landed.
|
||||
Drafted on 2026-11-17. The interim ConfigKit v1.2.0 adoption is implemented;
|
||||
the [implementation plan](implementation.md) records its verification. The
|
||||
upcoming PromptKit upgrade retains the separate ConfigKit v1.2.1 and stable
|
||||
YAML handoff, including retirement of the old module when no longer needed.
|
||||
This roadmap preserves the interim target, rationale, and scope.
|
||||
|
||||
The maintainer is adopting ConfigKit across an application suite to standardize
|
||||
configuration semantics. Scriptorium should use the selected ConfigKit's native
|
||||
|
||||
Reference in New Issue
Block a user