Share prompt instructions and simplify validation helpers

docs/internal/prompts.md

@@ -13,9 +13,12 @@
 
 PromptKit reads the embedded definitions and renders their system and user
 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.
+`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 prompt assets retain the prior task instructions and output-schema
 association. The role-bound runtime supplies the complete JSON Schema output contract

docs/internal/validators.md

@@ -77,8 +77,10 @@ unavailable; production schema validation still rejects out-of-range confidence
 before reconciliation. A partially unavailable batch records one failed
 operation with only those requested indices, while a successful batch with
 ignored extras records a decision-filtering recovery. Fatal errors stop the
-chain without returning unchecked candidates as approved. Reconciliation makes
-no semantic retry or extra model call; guided recovery remains
+chain without returning unchecked candidates as approved. A local result builder
+retains already-collected decisions and operations on early returns; full
+cardinality checks and final sorting remain explicit on completed paths.
+Reconciliation makes no semantic retry or extra model call; guided recovery remains
 [deferred](../roadmap/future.md#domain-aware-response-recovery).
 
 Debug request metadata records `proposal_indices` in local-reference order
@@ -118,6 +120,10 @@ is covered by [report assembly](diagnostics-reporting.md).
 
 ## Supplemental Validation Context
 
+Request construction prepares one segment-position lookup and protected vocabulary
+for all candidates. Glossary selection remains candidate-specific, including the
+proposed replacement text.
+
 Each candidate includes the immediately preceding and following source segments
 available within its fixed chunk, labeled `preceding` or `following` with speaker,
 text, and categories, plus glossary entries whose names, aliases, or

docs/roadmap/remediation.md

@@ -3,7 +3,7 @@
 **Reviewed:** 2026-09-25, source commit `011b021`.
 **Scope:** Recent partial-decision reconciliation, validation context, prompt
 alignment, and request-local reference changes, including related existing code.
-**Status:** R27–R30 open. Previous findings and resolution records remain in Git
+**Status:** R27–R30 addressed; see the resolution record below. Previous findings and resolution records remain in Git
 history through `011b021`.
 
 ## Architecture Assessment
@@ -133,10 +133,29 @@ material gap exposed by the refactor.
 
 - This is a source-level maintainability audit, not a finding of demonstrated
   production failures or a measured performance assessment.
-- No application tests were rerun for the read-only audit. This roadmap update
-  requires documentation link and whitespace checks only.
+- No application tests were rerun for the original read-only audit; its roadmap
+  update used documentation link and whitespace checks. Implementation validation
+  is recorded below.
 - Future remediation should run focused behavioral tests and the broader suite
   appropriate to the actual change, following the testing policy. No live-provider
   evaluation or new evaluation framework is required by these recommendations.
-- This document records recommendations only; no implementation, prompt, or
-  release changes are included in this update.
+- The findings above describe the audited baseline. Implementation and validation
+  are recorded below; no release publication is included.
+
+## Resolution Record
+
+Implemented as focused changes within the existing packages. Proposal and validator
+reference mapping and distinct protected-term policies remain separate.
+
+| Finding | Resolution and evidence |
+| --- | --- |
+| R27 | Common proposal and validation instructions live in two embedded shared fragments, supplied through the existing role-bound PromptKit adapter. Individual YAML definitions retain policy differences and examples. Rendering tests check fragment inclusion once per applicable prompt and representative module-specific guidance. |
+| R28 | Validation request construction builds one segment-position lookup and protected vocabulary, reused by context selection for every candidate. A new test verifies that two replacements of the same source span receive their own relevant glossary entries. Existing neighbor, glossary-order, chunk-boundary, and budget tests pass. |
+| R29 | Both proposal generation and validation use `outcomes.ExecutionRecoveries`. Call sites still control success and domain-specific recovery reasons. Existing tests cover combined recoveries and failed validation with repair counts but no recovery record. |
+| R30 | A local result builder combines collected decisions and operation outcomes for partial returns and completed validation. Sorting and full cardinality checks remain outside it. Existing fatal-batch, partial-progress, runner, and reporting tests pass. |
+
+Validation: `go test ./...` passed, including PromptKit preparation, partial-decision
+reconciliation, subprocess reports, and fatal-progress coverage. Documentation
+links and whitespace checks passed. No live model evaluation or performance
+measurement was performed; the changes make no new model-quality or latency
+promise.