Align prompts and strengthen validation context

docs/internal/prompts.md

@@ -1,6 +1,6 @@
 # Audita Prompt Registry
 
-`internal/prompts` embeds nine PromptKit YAML definitions under
+`internal/prompts` embeds seven PromptKit YAML definitions under
 `assets/prompts`. The IDs and selected version remain:
 
 - `modules.glossary.proposal` (`v1`)
@@ -10,17 +10,15 @@
 - `validators.spoken_form_plausibility` (`v1`)
 - `validators.meaning_reversal_review` (`v1`)
 - `validators.editorial_review` (`v1`)
-- `validators.grammar_review` (`v1`)
-- `validators.spoken_word_review` (`v1`)
 
 PromptKit reads the embedded definitions and renders their system and user
-messages from named string variables. The role-bound adapter will supply
+messages from named string variables. The role-bound adapter supplies
 `HardeningPolicy` from the single embedded `assets/shared/prompt_hardening.md`
 fragment after caller variables, so callers cannot replace that policy. Proposal prompts receive the
 section JSON, glossary JSON where used, and transcript description block.
 Validator prompts receive the correction payload and description block.
 The prompt assets retain the prior task instructions and output-schema
-association. The role-bound runtime will supply the complete JSON Schema output contract
+association. 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
@@ -41,3 +39,13 @@ 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
 [configuration](../config.md) for operator-selected profiles.
+
+Proposal instructions describe literal matching, each module's replacement policy,
+source-based proposal identity, and confidence in whether an edit is warranted.
+Validator instructions distinguish correction indices from segment IDs and confidence
+in the verdict from the verdict itself. The grammar article exception and glossary
+mishearing exception apply consistently across their instructions.
+
+Only the three active validator definitions are retained. The unused internal
+`grammar_review` and `spoken_word_review` definitions and type selections were
+removed; built-in chains and operator configuration are unchanged.

docs/internal/validators.md

@@ -107,3 +107,34 @@ is covered by [report assembly](diagnostics-reporting.md).
 - `internal/framework/validators/*_test.go`
 - `internal/framework/processreport/correction_ledger_test.go`
 - `internal/cli/run_test.go`
+
+## Supplemental Validation Context
+
+Each candidate includes the immediately preceding and following source segments
+available within its fixed chunk, plus glossary entries whose names, aliases, or
+recognized plurals appear in its original/resulting text or those neighbors.
+Glossary matching reuses the protected vocabulary; entries retain glossary order.
+This supplies evidence such as a troupe definition for a proposed `Jesters`
+correction or an adjacent speaker turn explaining deliberate repetition. A correction
+already clear from its own segment does not require such evidence. No audio,
+out-of-chunk context, or complete transcript is implied.
+
+Context is serialized inside the validation item and included in the existing
+payload token estimate. If one enriched item exceeds the configured limit, optional
+neighbors are removed from the end first, then glossary entries from the end,
+until it fits or only required candidate data remains. Required before/after text
+is never truncated. Existing oversized-candidate handling still applies if that
+required data does not fit. Context is supplemental, not a promise that every
+relevant definition or neighboring utterance always fits. This uses the existing
+payload estimator, not a new guarantee about the provider's full context window.
+
+## Protected-Name Repetition
+
+Spoken-word cleanup may reduce repeated protected-name occurrences when every
+original protected identity still appears in the resulting segment and surviving
+spellings satisfy existing capitalization checks. Full-segment preview supports
+both a replacement of the repeated phrase and deletion of a redundant span. This
+exception only relaxes the deterministic count guard; editorial and meaning-reversal
+validation still decide whether the repetition was accidental and the edit preserves
+meaning. Intentional emphasis and substantive references remain protected by those
+reviews. Other modules retain their existing protection rules.