docs: record update-only previous-question fix
This commit is contained in:
@@ -183,6 +183,12 @@ _Created by Experiment 34. Updated by Experiments 38–53, 54A–54Z, 55A–55F,
|
||||
|
||||
---
|
||||
|
||||
### Experiment 57J.81 — Update-Only Previous Question Fix
|
||||
|
||||
**Objective:** Fix the 57J.80 apparatus defect where `FIXTURE_MODE=updateOnly` passes `previousQuestion = null` through to the production Zod validator, which rejects with `"Expected string, received null"` at `request_validation` stage before any model inference.
|
||||
|
||||
**Classification: A — FIX VALIDATED (tooling only).** The pre-anchored fixture already contains the exact question text at `unresolved_question` ("Are the projected office savings from relocation realistic?"). Changed the harness to derive `previousQuestion` from that committed anchor (`fixtureData.unresolved_question ?? savingsNode.label`) instead of sending `null`. Source is the fixture anchor — no independent duplicate hardcoded question added. Zero production code changed. 49 harness tests pass (5 new deterministic regressions). The update-only apparatus can now reach the real production Update path without requiring Start.
|
||||
|
||||
---
|
||||
|
||||
### Experiment 57J.53 — Structured Fidelity Multi-Turn Progress
|
||||
|
||||
Reference in New Issue
Block a user