Defer appended-message flags and preserve operator use cases
This commit is contained in:
@@ -88,10 +88,9 @@ commands, composed through existing core bindings.
|
||||
[Roadmap OD-2](promptkit-v0.19.0.md#od-2-request-controls-and-provider-parameter-grammar)
|
||||
records the agreed canonical naming, scoped convenience aliases, integration
|
||||
installation collection, and selected text/file input forms; no core extension
|
||||
is required. Appended-message flags remain open for individual review. These
|
||||
are CLI features;
|
||||
general-purpose helpers for application-internal PromptKit use are outside
|
||||
CommandKit's ownership boundary.
|
||||
is required. Output-contract overrides and appended-message flags are deferred
|
||||
below. These are CLI features; general-purpose helpers for application-internal
|
||||
PromptKit use are outside CommandKit's ownership boundary.
|
||||
|
||||
- **Focused backend inspection.** Defer a standard backend detail command
|
||||
until a released PromptKit version provides a suitable public backend
|
||||
@@ -112,11 +111,22 @@ CommandKit's ownership boundary.
|
||||
application builders remain available. Revisit when the standard `promptkit`
|
||||
commands have a demonstrated need for this workflow.
|
||||
|
||||
Appended-message flags remain a scope choice under
|
||||
[roadmap OD-2](promptkit-v0.19.0.md#od-2-request-controls-and-provider-parameter-grammar).
|
||||
Inline text and explicit file input are now selected there for single-prompt
|
||||
validation and preview. Native API availability alone does not select further
|
||||
CLI syntax or require a convenience API for application execution.
|
||||
- **Appended-message flags.** Deferred from the current adoption. The potential
|
||||
operator task is reproducing a single request with application-added messages
|
||||
through `promptkit show prepared` or `promptkit requirements validate`, to
|
||||
inspect roles, ordering, and content or check preparation. These commands do
|
||||
not test model responses or application workflows. Appended messages follow
|
||||
definition messages in supplied order; they are already rendered and do not
|
||||
satisfy missing named prompt inputs. Revisit when request reproduction is a
|
||||
demonstrated operator requirement. An ordered message-list file is a candidate,
|
||||
but no flag syntax, file format, or supported-role selection is decided.
|
||||
Deferring flags does not remove native appended messages from preview reports
|
||||
when an application builder supplies them.
|
||||
|
||||
[Roadmap OD-2](promptkit-v0.19.0.md#od-2-request-controls-and-provider-parameter-grammar)
|
||||
selects inline text and explicit file input for single-prompt validation and
|
||||
preview. Native API availability alone does not select further CLI syntax or
|
||||
require a convenience API for application execution.
|
||||
|
||||
### Alias completion and discovery
|
||||
|
||||
|
||||
@@ -187,8 +187,8 @@ values and whole-map replacement semantics. Support deliberate subsets for
|
||||
actual command needs while retaining common flag names and meanings, using a
|
||||
proportionate composition API. Keep parsing in CommandKit and domain validity
|
||||
in PromptKit. Existing application builders remain authoritative as agreed in
|
||||
OD-2. That decision also selects literal-text and file input bindings, defers
|
||||
output-contract overrides, and leaves appended-message controls open.
|
||||
OD-2. That decision also selects literal-text and file input bindings and defers
|
||||
output-contract overrides and appended-message controls.
|
||||
|
||||
### Namespace selection
|
||||
|
||||
@@ -364,8 +364,8 @@ Default tests remain offline and independent of real credentials.
|
||||
including empty text, reaches native inline inputs; file bindings remain file
|
||||
references. Examples, help, and documentation use the selected meanings.
|
||||
Resolve and cover duplicate-name precedence across the two input forms.
|
||||
- [ ] Appended-message options receive an explicit scope decision before
|
||||
implementation; output-contract override flags remain deferred.
|
||||
- [ ] Output-contract override and appended-message flags remain outside this
|
||||
adoption, with their operator use cases retained in future work.
|
||||
- [ ] Namespace defaults, explicit clearing, qualified selections, and catalog
|
||||
filters are forwarded according to the selected design.
|
||||
- [ ] The full configuration suite retains six subcommands. Explanation
|
||||
@@ -434,7 +434,8 @@ handle lifecycle, sessions, and observer convenience APIs remain application
|
||||
responsibilities. Persistent configuration editing, new live probes, dynamic completion,
|
||||
JSON report formats, and unrelated deferred proposals are not added by this
|
||||
roadmap. Transient acquisition overrides remain an explicit choice in OD-11.
|
||||
Output-contract override flags are also deferred under OD-2 and retained in
|
||||
Output-contract override and appended-message flags are deferred under OD-2
|
||||
and retained in
|
||||
[future work](future.md#promptkit-inspection-and-selection-extensions).
|
||||
Discovery tracing and secrets-directory bootstrap commands remain deferred:
|
||||
the source inventory is not a trace of rejected search candidates, and bootstrap
|
||||
@@ -568,9 +569,16 @@ adoption. Retain the candidate in
|
||||
[future work](future.md#promptkit-inspection-and-selection-extensions);
|
||||
existing configuration and application builders remain available.
|
||||
|
||||
**Remaining request surface:** discuss appended-message flags individually
|
||||
before selecting scope and syntax. No general-purpose request-building API
|
||||
follows from these CLI choices.
|
||||
**Deferred appended-message flags:** no CLI message-appending option is included
|
||||
in this adoption. The potential standard-command task is reproducing a request
|
||||
with application-added messages for preparation validation or preview. Revisit
|
||||
when that is a demonstrated operator requirement; ordinary named inputs remain
|
||||
available for inspecting prompt definitions with concrete content. Retain the
|
||||
candidate in [future work](future.md#promptkit-inspection-and-selection-extensions).
|
||||
No message-file format, flag syntax, or role-selection interface is selected.
|
||||
Native application-supplied appended messages remain part of prepared-request
|
||||
inspection; deferring flags does not remove that report evidence. No
|
||||
general-purpose request-building API follows from these CLI choices.
|
||||
|
||||
### OD-3: Namespace flags and loader defaults
|
||||
|
||||
|
||||
Reference in New Issue
Block a user