Accept span deletions in structured responses

internal/prompts/assets/prompts/modules.grammar.proposal.yaml

@@ -24,6 +24,8 @@ messages:
       - For returned corrections, original_text must be only the exact text span that needs replacement, not the full segment text unless the whole segment is the replacement span.
       - Choose an original_text span that appears exactly once in the current segment text.
       - corrected_text must be only the replacement text for that span, not the full corrected segment text unless the whole segment is the replacement span.
+      - A whitespace-only original_text can identify a spacing change: replacing the two spaces in "hello  world" with one space yields "hello world". An empty corrected_text deletes its identified span when punctuation or spacing should be removed.
+      - Omit a correction that would leave the segment blank; do not invent padding or content to keep it nonblank.
       - Each returned correction must contain only id, original_text, corrected_text, and confidence.
       - Do not return corrections where original_text and corrected_text are identical.
       - Do not return speaker, start, or end fields.

internal/prompts/assets/prompts/modules.spoken_word.proposal.yaml

@@ -26,6 +26,8 @@ messages:
       - For returned corrections, original_text must be only the exact text span that needs replacement, not the full segment text unless the whole segment is the replacement span.
       - Choose an original_text span that appears exactly once in the current segment text.
       - corrected_text must be only the replacement text for that span, not the full corrected segment text unless the whole segment is the replacement span.
+      - An empty corrected_text deletes the identified span. For example, removing "uh " from "uh hello" leaves "hello"; include adjacent whitespace or punctuation in the span when needed for the intended literal result.
+      - Omit a correction that would leave the segment blank; do not invent padding or content to keep it nonblank.
       - Each returned correction must contain only id, original_text, corrected_text, and confidence.
       - Do not return corrections where original_text and corrected_text are identical.
       - Do not return speaker, start, or end fields.

internal/prompts/assets/prompts/validators.editorial_review.yaml

@@ -20,6 +20,7 @@ messages:
       - Approve repetition cleanup only when local context supports it as accidental repetition, hesitation, or verbal restart.
       - Reject broad paraphrase, substantive semantic changes, substantive meaning changes, and revisions that materially change, obscure, distort, or reverse the segment's meaning.
       - Evaluate the full original_segment_text and corrected_segment_text, not only the replacement span.
+      - An empty corrected_text deletes the identified span; judge the actual before/after segment, including adjacent spacing and punctuation. Do not approve or reject solely because the replacement is empty.
       - If a correction includes categories, treat them as additional segment context.
       - Each returned validation must contain only correction_index, approved, confidence, and reason.
       - confidence must be between 0.0 and 1.0.

internal/prompts/assets/prompts/validators.meaning_reversal_review.yaml

@@ -13,6 +13,7 @@ messages:
       - Reject corrections that introduce antonyms or otherwise reverse the meaning of the original segment.
       - Reject examples like changing "visible" to "invisible" or "up" to "down" when that reverses the segment meaning.
       - Evaluate the full original_segment_text and corrected_segment_text, not only the replacement span.
+      - An empty corrected_text deletes the identified span; decide from the full before/after segment whether that deletion reverses meaning, not from the empty string alone.
       - Do not reject a correction merely because the literal written word changes.
       - Do not act as a general semantic-style reviewer; this validator is only a guard against antonyms and meaning reversals.
       - If a correction includes categories, treat them as additional segment context.

internal/prompts/assets/prompts/validators.spoken_form_plausibility.yaml

@@ -14,6 +14,7 @@ messages:
       - Examples that may be approved when context supports them: changing "gestures" to "Jesters", "rank" to "Hrank", or "dam" to "damn".
       - Reject unrelated substitutions like changing "Lyra" to "Jesters".
       - Judge spoken-form plausibility, not whether the correction is cleaner, more formal, or more grammatical.
+      - Use the full original_segment_text and corrected_segment_text when a span is deleted; an empty corrected_text alone does not establish or rule out a spoken-form mistranscription.
       - Do not approve paraphrases, stylistic rewrites, or arbitrary semantic substitutions.
       - If a correction includes categories, treat them as additional segment context.
       - Each returned validation must contain only correction_index, approved, confidence, and reason.