Clarify completed implementation records and later corrections
This commit is contained in:
@@ -1,10 +1,29 @@
|
||||
# Initial CommandKit implementation plan
|
||||
|
||||
Status: implementation complete; Stages 1-14 complete.
|
||||
Status: completed execution record; Stages 1-14 complete.
|
||||
|
||||
Date: 2026-10-07.
|
||||
|
||||
## Purpose and instructions for the implementation agent
|
||||
## Record scope and current owners
|
||||
|
||||
The staged instructions and API illustrations below are retained as the record
|
||||
of the completed initial implementation. They describe the assignments used to
|
||||
produce the [selected feature target](initial.md), not work to restart. The
|
||||
[CLI reference](../cli.md) owns current operator behavior, Go declarations and
|
||||
GoDoc own current API contracts, the [consumer guide](../consumers/guide.md) owns
|
||||
usage guidance, and the [internal overview](../internal/overview.md) owns mechanics.
|
||||
|
||||
### Subsequent code remediation
|
||||
|
||||
After original stage completion at `85f44cd`, ten code-remediation units were
|
||||
committed from `d8db15f` through `cb0b8dd`. They corrected scope-specific required
|
||||
selectors, inline YAML framing, cancellation boundaries, help failure delivery,
|
||||
validation delivery errors, outcome defaults, nil diagnostic handling, scope
|
||||
choices, selector-name collisions, and metadata-only help discovery. These
|
||||
corrections are reflected in current code and its regression checks. Original
|
||||
stage completion notes remain historical evidence, not a new validation run.
|
||||
|
||||
## Historical instructions for the implementation agent
|
||||
|
||||
Implement the selected end state in [the feature roadmap](initial.md). Read this
|
||||
whole plan before starting. Complete Stage 1, then each subsequent stage in numeric
|
||||
@@ -778,8 +797,10 @@ func RegisterPromptKit[C any](app *App, suite PromptKitSuite[C]) error
|
||||
bookkeeping. Configuration scope installation remains independent.
|
||||
3. Accept ID as one required operand. Prompt alone has singleton `--version`
|
||||
(default empty). Both accept standard Config/Overlay selection, context-selector
|
||||
bindings, and `--format text|yaml` (text default), plus help. No `--scope` is
|
||||
installed for definition commands. Selector target is `promptkit`; empty Scopes
|
||||
bindings, and `--format text|yaml` (text default), plus help. No built-in configuration-scope selector is
|
||||
installed for definition commands; a custom context selector can use the name
|
||||
`scope` when it does not collide with an installed flag. Selector target is
|
||||
`promptkit`; empty Scopes
|
||||
or a list containing promptkit applies, independent of a config scope registry.
|
||||
Other explicit targets are miswired metadata at registration.
|
||||
4. Reuse Stage 7's input/context creation and input-check rules. Missing ID is
|
||||
|
||||
Reference in New Issue
Block a user