Plan the CommandKit adoption sprint

This commit is contained in:
2026-11-20 04:05:11 +00:00
parent bcbfc0fa4a
commit 86692d58f9
2 changed files with 677 additions and 11 deletions

View File

@@ -3,8 +3,9 @@
Status: agreed target; implementation pending.
This roadmap consolidates the [migration discussion](commandkit-notepad.md).
It defines the intended end state and required work. Detailed implementation
sequencing belongs in a subsequent plan.
It defines the intended end state and required work. The
[implementation plan](implementation.md) defines the ordered implementation
stages.
## Objective And Scope
@@ -294,7 +295,7 @@ and applicable file/directory selectors.
## Required Work
These work areas describe scope, not mandatory buildable milestones.
The required changes span these areas.
1. **Replace the command boundary.** Add the selected dependencies and native
application/command declarations. Wire typed inputs to domain operations,
@@ -356,12 +357,6 @@ services, real credentials, and paid model calls. Run the repository's establish
final checks from [Development](../development.md#validation): tests, race-enabled
tests, vet, and build, including documentation and maintained-example checks.
Carry out implementation as one end-to-end sprint. Intermediate commits may be
incomplete, incoherent, or noncompiling; use focused checks where useful and
report their state accurately. Do not add compatibility scaffolding to make each
commit independently shippable. Completion requires the coherent, compilable,
validated final application and its documentation.
## Migration And Deferred Work
Release guidance will include an old-to-new command table and explain identity
@@ -383,5 +378,5 @@ separate work. The catalog exposes Narratio's configured knowledge; this
migration does not promise to discover prompt requirements or prove that every
configured pipeline can complete.
No significant design decisions remain open. Implementation sequencing and
release selection do not block preparation of the implementation plan.
No significant design decisions remain open. Release selection remains separate
from implementation.