base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Complete documentation reconciliation and final review

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 18:32:44 +00:00
parent eaf0c8f004
commit 3871d83748
5 changed files with 73 additions and 43 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
docs/cli.md
View File

@@ -149,9 +149,10 @@ order, with a `# scope: NAME` comment at each document boundary. For ordinary
block documents the comment follows the marker. When a native opening marker
contains inline content, the comment precedes that marker so it does not
interrupt the native value. Existing native markers and leading comments are
retained; documents without a marker receive one. Scope labels containing line control characters are quoted to keep them on
one comment line. A provider failure leaves the output stream empty. A rendering
or output failure may leave an aggregate prefix, and the outcome reports
retained; documents without a marker receive one. Scope labels containing line
control characters are quoted to keep them on one comment line. A provider
failure leaves the output stream empty. A rendering or output failure may leave
an aggregate prefix, and the outcome reports
incomplete report delivery.
### List configuration sources
@@ -230,12 +231,12 @@ serialized as `[]`.
## PromptKit definition inspection
Applications can install prompt and profile inspection independently with
`RegisterPromptKit`. Each installed handler invokes its registered inspection
callback once with the caller's selection and context. The bundled
`NewPromptKitSuite` helper acquires an engine through the application loader and
asks PromptKit to inspect its captured named definition. The loader can construct
or reuse an engine; direct suite callbacks retain their own implementation and
lifecycle.
`RegisterPromptKit`. When acquisition is reached, the handler invokes its
registered inspection callback once with the caller's selection and context.
The bundled `NewPromptKitSuite` helper acquires an engine through the application
loader and asks PromptKit to inspect its captured named definition. The loader
can construct or reuse an engine; direct suite callbacks retain their own
implementation and lifecycle.
CommandKit's inspection path does not execute prompts, contact model providers,
or resolve provider credential values. Application acquisition and direct