Defer appended-message flags and preserve operator use cases
This commit is contained in:
@@ -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