Enable prompt preview validation and smoke commands

docs/internal/prompts.md

@@ -1,37 +1,29 @@
 # Audita Prompt Registry
 
-`internal/prompts` embeds seven PromptKit YAML definitions under
-`assets/prompts`. The IDs and selected version remain:
+`internal/prompts` embeds seven PromptKit definitions in the `audita`
+collection. The four proposal IDs are `audita/modules.glossary.proposal`,
+`audita/modules.homophones.proposal`, `audita/modules.spoken_word.proposal`,
+and `audita/modules.grammar.proposal`; the three validator IDs are
+`audita/validators.spoken_form_plausibility`,
+`audita/validators.meaning_reversal_review`, and
+`audita/validators.editorial_review`.
 
-- `modules.glossary.proposal` (`v1`)
-- `modules.homophones.proposal` (`v1`)
-- `modules.spoken_word.proposal` (`v1`)
-- `modules.grammar.proposal` (`v1`)
-- `validators.spoken_form_plausibility` (`v1`)
-- `validators.meaning_reversal_review` (`v1`)
-- `validators.editorial_review` (`v1`)
+PromptKit composes embedded defaults with operator prompt sources. Shared
+instructions come from the embedded fragments in `assets/shared`; the request
+adapter fills absent `HardeningPolicy`, `ProposalContract`, and
+`ValidationContract` variables without replacing values explicitly supplied by
+the caller. Processing supplies Audita's response-schema contract separately.
+The operator's prompt definition controls which variables its template uses.
+
+For a standard request preview or validation, select a native PromptKit profile
+and supply the template variables used by the selected prompt. The shipped
+proposal definitions use `TranscriptDescriptionBlock`, `GlossaryJSON`, and
+`SectionJSON`; the validator definitions use `TranscriptDescriptionBlock` and
+`PayloadJSON`. The latter is supplied candidate JSON and does not require a
+proposal inference call. An operator replacement may use different variables.
+See the [upstream CLI reference](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/f369d6a78253b6e6fcb1e023fb2e9c3af1d20ff0/docs/cli.md)
+for the standard preview, validation, and smoke commands.
 
-PromptKit reads the embedded definitions as shipped defaults and renders their
-messages from named string variables. Operator documents in `profiles_dir` may
-contribute native keyed prompt definitions and override an embedded
-prompt/version, including its messages and definition-level output settings.
-The effective operator text is captured when the runtime is constructed; the
-embedded assets remain the source of Audita's shipped task instructions. The
-role-bound adapter supplies
-`HardeningPolicy` alongside `ProposalContract` and `ValidationContract` from
-embedded fragments under `assets/shared`, after caller variables so callers
-cannot replace those instructions. Common literal-span and identity guidance
-lives in the proposal fragment; shared candidate-reference, context, and
-confidence guidance lives in the validation fragment. Module-specific policies
-and examples remain in YAML. Proposal prompts receive the section JSON, glossary
-JSON where used, and transcript description block. Validator prompts receive
-the correction payload and description block.
-The embedded prompt assets retain the shipped task instructions and
-output-schema association. An operator override controls which template
-variables its messages reference: supplying a shared variable does not append
-its text when the effective message omits that reference. The role-bound runtime
-supplies the complete JSON Schema output contract and repair count; the
-definition does not own an operator-facing repair default.
 The correction-set schema requires a string replacement and accepts an empty
 string. Proposal guidance uses it for eligible span deletion and permits literal
 spacing edits; validator guidance evaluates the full before/after segment under
@@ -43,10 +35,9 @@ rejection, not a structural schema error.
 filesystem to PromptKit and retains Audita's schema-key lookup. PromptKit's
 prepared execution supplies definition and rendered hashes; Audita does not
 recompute or promise equality with hashes from the removed template renderer.
-The small Audita registry records only prompt ID, version, source, and embedded
-path. Prepared runtime metadata belongs in diagnostics rather than the registry.
+The small Audita registry records only prompt ID, source, and embedded path. Prepared runtime metadata belongs in diagnostics rather than the registry.
 
-The structured-call contract carries prompt ID/version, string variables,
+The structured-call contract carries prompt ID, string variables,
 response-schema key, and logical-call attribution. Module and validator callers
 pass these values through the role-bound adapter. See the
 [LLM runtime](llm-runtime.md) for runtime assembly and

docs/roadmap/implementation.md

@@ -275,6 +275,11 @@ for inspection or overriding native grammar or status behavior.
 
 ## Stage 6: Enable standard PromptKit request and smoke commands
 
+**Completed.** Native preview, validation, and the complete smoke surface are
+installed through the shared loader. Controlled transport checks cover operator
+replacement, validator input, explicit smoke, and aggregate smoke. The processing
+handler and maintained example projects are assigned below.
+
 Own the remaining `internal/cli` adapters. Use
 [the resolved command scope](commandkit.md#request-preview-validation-and-smoke-commands--resolved)
 and `WithRequestPreparation`, `WithRequestValidation`, and `WithSmokeTesting`