Document validation defaults and cleanup roadmap

docs/internal/llm.md

@@ -19,9 +19,10 @@ structured output. The response also carries the raw structured output bytes
 returned by the runtime so modules can preserve raw payloads in pipeline stage
 outputs.
 
-Modules that call the LLM own their prompts, schemas, prompt IDs, validators,
-and domain-specific interpretation. Provider adapters should not contain
-domain-specific prompt logic.
+Modules that call the LLM own their prompts, schemas, prompt IDs, and
+domain-specific interpretation. Validator packages own approve/reject policy,
+and central catalog mappings decide which validators run by default. Provider
+adapters should not contain domain-specific prompt logic.
 
 Prompt input materials carry source or reference bytes with optional origin
 metadata. The Scriptorium-backed runtime receives them as named artifacts rather
@@ -43,9 +44,11 @@ The runtime records the actual selected Scriptorium profile, provider, and model
 used during execution. Manifest population does not rely on a precomputed
 profile ID before pipeline execution.
 
-Explicit profile validation and `--llm-profile` overrides apply to LLM-capable
-pipeline stages: chunk, extract, merge, and normalize. Input, output, and
-validator bindings are not part of the current production LLM profile scope.
+Explicit profile validation applies to LLM-capable pipeline stages: chunk,
+extract, merge, normalize, and LLM-backed validators with explicit
+`llm_profile` values. Input, output, and deterministic validators do not call
+the LLM. The `--llm-profile` run flag overrides effective chunk, extract, merge,
+and normalize bindings; it does not override validator-specific profiles.
 
 ## Scriptorium Adapter