Document PromptKit catalogs and smoke testing
This commit is contained in:
@@ -47,10 +47,12 @@ initialized input, while one suite-owned state value is shared by an invocation'
|
||||
acquisitions or comparison callback.
|
||||
|
||||
`integrations/ckprompt` owns PromptKit engine loading, configuration-scope
|
||||
adaptation and native comparison, plus optional prompt/profile catalogs, named
|
||||
inspection, native requirements discovery, and concrete request validation.
|
||||
Validation delegates request preparation to PromptKit and is independently
|
||||
opted into a suite. It uses public core and ckconfig contracts plus PromptKit's
|
||||
adaptation and native comparison, plus optional prompt/profile/backend/namespace/
|
||||
collection catalogs, named inspection, native requirements discovery,
|
||||
concrete request validation, and native smoke testing. Validation and smoke
|
||||
testing delegate to PromptKit and are independently opted into a suite. Smoke
|
||||
operations use the application's native engine and its configured client or
|
||||
probes. The integration uses public core and ckconfig contracts plus PromptKit's
|
||||
public APIs. It does not add a configuration family when its declaration is
|
||||
installed; callers compose `ckprompt.ConfigScope` with `ckconfig.Command`
|
||||
separately when they want configuration operations alongside PromptKit
|
||||
@@ -70,8 +72,10 @@ graph isolation.
|
||||
ConfigKit owns configuration decoding, validation, source history, and path
|
||||
explanations. PromptKit owns its captured engine configuration, prompt
|
||||
definitions, profile inheritance, named inspection, requirements discovery,
|
||||
and concrete request validation semantics. CommandKit adapts those public
|
||||
contracts without maintaining parallel schemas or invoking model generation.
|
||||
and concrete request validation, and native smoke-test semantics. CommandKit
|
||||
adapts those public contracts without maintaining parallel schemas. Explicit
|
||||
native smoke operations may use the configured client or probes; other
|
||||
inspection, catalog, and request-validation paths do not make model calls.
|
||||
Native request validation may load resources and artifacts, render messages,
|
||||
and perform applicable configuration or credential checks through PromptKit.
|
||||
Application loaders and domain behavior remain application owned.
|
||||
|
||||
Reference in New Issue
Block a user