Plan coordinated ConfigKit and PromptKit adoption
This commit is contained in:
@@ -115,9 +115,11 @@ reporting are likely to overlap this migration. Design their shared target model
|
||||
first. If another change will substantially reshape those areas, avoid migrating
|
||||
the same concepts twice. Work independent of configuration can proceed separately.
|
||||
|
||||
The migration may provide the configuration foundation for later features, or join
|
||||
other changes in one major release. Neither ordering is selected yet. Prefer
|
||||
reviewable implementation units even if the final release combines several changes.
|
||||
The [coordinated library-adoption roadmap](library-adoption.md) owns the proposed
|
||||
sequence with PromptKit: shared boundary design and a PromptKit prototype, then
|
||||
ConfigKit implementation, then PromptKit implementation, followed by a combined
|
||||
v2.0.0 release. Revisit that sequence alongside other major changes. Keep
|
||||
implementation units reviewable even when the release combines them.
|
||||
|
||||
The separate [runtime behavior decisions](runtime-behavior.md) remain unresolved.
|
||||
Coordinate the retry-count question with the new configuration semantics where
|
||||
|
||||
Reference in New Issue
Block a user