Clarify PromptKit capture and preparation behavior
This commit is contained in:
@@ -72,8 +72,9 @@ An empty request profile lets the prompt select its configured default. Before a
|
||||
run begins, the CLI asks the adapter to inspect every explicit profile on the
|
||||
resolved selected LLM-backed bindings and validators, including inherited
|
||||
pipeline profiles. Inspection resolves the profile and its selected backend and
|
||||
target without loading a prompt, reading credentials, admitting capacity, or
|
||||
contacting a provider, so a missing or invalid explicit profile fails before
|
||||
target without preparing a request, reading credentials, admitting capacity, or
|
||||
contacting a provider. Engine construction validates effective prompt definitions
|
||||
and captures message files and static templates. A missing or invalid profile fails before
|
||||
stage execution while a valid `api_key_env` may remain unset. Calls record the
|
||||
profile actually selected by PromptKit. The recorder trims and deduplicates
|
||||
non-secret profile identity, provider, model, selected backend ID, and
|
||||
@@ -95,8 +96,9 @@ relative resource roots. PromptKit validates final effective definitions at
|
||||
engine construction. It does not run a separate audit that rejects a malformed
|
||||
definition superseded by a later overlay. The D&D registrar contributes its
|
||||
`dnd-extraction` fallback, and maintained D&D prompts select that logical ID
|
||||
by default. A profile selecting `backend: local` requires the optional local
|
||||
registration.
|
||||
by default. A profile selecting `backend: local` can use an operator
|
||||
`backends.local` declaration or the optional Notarius registration; see
|
||||
[native source rules](../config.md#native-promptkit-sources-and-migration).
|
||||
|
||||
This PromptKit integration uses the old-path ConfigKit v0.5.0 types exposed by
|
||||
PromptKit v0.12.0. Application configuration uses the distinct new-path
|
||||
|
||||
Reference in New Issue
Block a user