Accept span deletions in structured responses
This commit is contained in:
@@ -2,7 +2,7 @@
|
||||
|
||||
**Last updated:** 2026-09-25
|
||||
|
||||
**Status:** In progress; Stage 1 complete.
|
||||
**Status:** In progress; Stages 1–2 complete.
|
||||
**Source baseline:** `a83a518` (feature roadmap); application baseline `0b6cd98`.
|
||||
**Audience:** gpt-5.6-terra coding agent.
|
||||
|
||||
@@ -239,6 +239,11 @@ but schema-valid proposals still reach ordinary filtering without an outer retry
|
||||
**End state:** A literal empty replacement can cross the real library/schema
|
||||
boundary, and the model instructions and validator inputs describe its meaning.
|
||||
|
||||
**Completed 2026-09-25.** Relaxed only the replacement length constraint,
|
||||
clarified the relevant proposal and active validation prompts, and verified
|
||||
rendering, real-adapter acceptance/rejection, repair counts, and serialized
|
||||
before/after validator payloads. The specified focused package tests passed.
|
||||
|
||||
## Stage 3 — Preserve Empty Replacements in Debug Evidence
|
||||
|
||||
**Work**
|
||||
|
||||
Reference in New Issue
Block a user