Align Narratio requirements with native CommandKit reports
This commit is contained in:
@@ -208,6 +208,32 @@ qualified IDs and explicit namespace flags when selecting namespaced resources,
|
||||
while retaining upstream behavior for unqualified IDs. Configurable defaults
|
||||
can be considered later if a need arises.
|
||||
|
||||
### Native inspection reports and consumer requirements
|
||||
|
||||
Decision recorded 2026-11-19: adopt native inspection reports and the native
|
||||
`promptkit requirements show` interface for Narratio's early dependency
|
||||
discovery. Its consumer needs and acceptance scenarios are recorded in the
|
||||
[aligned Narratio proposal](narratio-feature-request.md). This direction is
|
||||
accepted; Scriptorium integration remains to be implemented.
|
||||
|
||||
Consume native report fields without a Scriptorium-specific schema-version
|
||||
envelope. Use native nonzero outcomes and diagnostics for invocation failures;
|
||||
JSON report selection does not require JSON errors. Neither a separately
|
||||
versioned envelope nor programmatic invocation-failure categories blocks this
|
||||
migration. A future concrete need for either belongs in an upstream discussion.
|
||||
|
||||
PromptKit owns requirement classification, discovery completeness, and structured
|
||||
discovery issues. Completeness is distinct from satisfied bindings or execution
|
||||
readiness; Narratio owns comparison against its planned inputs. Keep early
|
||||
discovery separate from concrete request validation. Use current exact resource
|
||||
identities and native input/variable metadata, without restoring obsolete prompt
|
||||
versions or inventing input schemas or variable-default semantics.
|
||||
|
||||
Standard prompt inspection includes captured messages; prepared preview includes
|
||||
rendered content. Adopt these native reports without rebuilding Scriptorium's
|
||||
previous summary projections, and explain the changed presentation in migration
|
||||
guidance. Requirements discovery retains its distinct upstream content boundary.
|
||||
|
||||
## Upstream baseline
|
||||
|
||||
The initial review covered CommandKit **v0.7.0**, ckconfig **v0.9.0**, and
|
||||
@@ -252,33 +278,7 @@ responsibilities. Decide their mapping to the CommandKit invocation context
|
||||
and PromptKit operation timeout, separately from the standard per-attempt
|
||||
timeout flag.
|
||||
|
||||
### 2 Native reports and executable consumer needs
|
||||
|
||||
Adopt native inspection reports as the starting point. Standard prompt
|
||||
inspection includes captured prompt messages, unlike the current Scriptorium
|
||||
summary. Document that change and confirm how native inspection and preparation
|
||||
reports meet operator needs without rebuilding custom projections.
|
||||
|
||||
Reconcile the proposed [Narratio requirements request](narratio-feature-request.md)
|
||||
with native `promptkit requirements show`. Its central need remains valid:
|
||||
discover input requirements before expensive upstream work and before input
|
||||
files exist. Preserve the distinction between successful discovery and complete
|
||||
discovery; a successful partial report does not establish all requirements.
|
||||
|
||||
The proposal's legacy syntax and prompt-version assumptions need revision. Its
|
||||
illustrative versioned JSON envelope and structured-error request also need a
|
||||
decision: native reports do not add that Scriptorium envelope, and `--format
|
||||
json` does not automatically turn diagnostics into a JSON error protocol.
|
||||
Determine which consumer requirements are essential and whether any genuine
|
||||
gap belongs upstream. Avoid treating the existing proposal as a mandate for a
|
||||
new compatibility facade.
|
||||
|
||||
Keep discovery distinct from concrete request validation: validation prepares a
|
||||
real request and may read input artifacts and check relevant credentials;
|
||||
discovery must work before those artifacts exist. Neither guarantees a future
|
||||
generation will succeed.
|
||||
|
||||
### 3 Application commands and standard request flags
|
||||
### 2 Application commands and standard request flags
|
||||
|
||||
Decide the final generation command operands and application-specific flags
|
||||
around the reusable ckprompt request flag groups. Use their standard names,
|
||||
|
||||
Reference in New Issue
Block a user