Settle native configuration and namespace conventions
This commit is contained in:
@@ -175,6 +175,39 @@ not itself extend the native inspection commands. File-output convenience does
|
||||
not justify retaining a separate preview command. Update maintained examples
|
||||
and release migration guidance to use `promptkit show prepared`.
|
||||
|
||||
### Configuration selection and namespaces
|
||||
|
||||
Decision recorded 2026-11-19: fully adopt native configuration and namespace
|
||||
conventions. Expose the `app` and `promptkit` configuration scopes through
|
||||
ckconfig. `app` inspects Scriptorium's application settings; `promptkit`
|
||||
inspects the framework configuration assembled from the selected sources.
|
||||
Collections do not become separate configuration scopes. Application-only
|
||||
inspection must not require constructing a PromptKit engine.
|
||||
|
||||
`--config` consistently selects Scriptorium's application configuration,
|
||||
including when inspecting the `promptkit` scope. That configuration selects
|
||||
the framework sources and collection-discovery file. Adopt the standard
|
||||
`--overlay` spelling and use consistent source-selection and loading rules
|
||||
across generation, preview, inspection, requirements, and other applicable
|
||||
commands. Keep the established ConfigKit collection-import model.
|
||||
|
||||
Enable the native prompt, profile, and backend namespace selectors on
|
||||
applicable commands. They independently scope short caller-supplied resource
|
||||
IDs; qualified IDs remain exact selections. Namespace selection does not
|
||||
rewrite stored references or change collection discovery. Keep configuration
|
||||
scope, resource namespace, and profile selection distinct.
|
||||
|
||||
Use native inventory filters, including namespace selection and
|
||||
`--all-namespaces`, and retain upstream default listing behavior. Support
|
||||
standard temporary configuration overrides where the upstream loader supports
|
||||
them. The reviewed PromptKit configuration scope does not support those
|
||||
overrides; do not add local override semantics to compensate.
|
||||
|
||||
Do not add configurable default namespaces in the initial migration. Use
|
||||
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.
|
||||
|
||||
## Upstream baseline
|
||||
|
||||
The initial review covered CommandKit **v0.7.0**, ckconfig **v0.9.0**, and
|
||||
@@ -219,24 +252,7 @@ responsibilities. Decide their mapping to the CommandKit invocation context
|
||||
and PromptKit operation timeout, separately from the standard per-attempt
|
||||
timeout flag.
|
||||
|
||||
### 2 Configuration selection and namespace experience
|
||||
|
||||
Use consistent application configuration and PromptKit source selection across
|
||||
generation, inspection, requirements, and previews. Application-only
|
||||
configuration inspection should not require constructing a PromptKit engine.
|
||||
|
||||
Decide how the standard `app` and `promptkit` configuration scopes are exposed,
|
||||
how application selectors map into their loaders, and which temporary overrides
|
||||
are supported. Configuration scope, resource namespace, and profile selection
|
||||
are distinct concepts and should remain clear to operators.
|
||||
|
||||
For installations with many collections, decide whether to enable the optional
|
||||
prompt, profile, and backend namespace selectors and how to present the native
|
||||
namespace-filtered and all-namespace inventory views. Begin with upstream
|
||||
behavior; identify any unmet collection-navigation need before adding local
|
||||
conventions. Collection discovery itself does not need redesign for CommandKit.
|
||||
|
||||
### 3 Native reports and executable consumer needs
|
||||
### 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
|
||||
@@ -262,7 +278,7 @@ 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.
|
||||
|
||||
### 4 Application commands and standard request flags
|
||||
### 3 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