Parser improvements must be tested through the consuming API validator

Parser improvements must be tested through the consuming API validator, not only replayed at the parser. A service can correctly preserve raw OCR while returning a repaired identifier, yet a consumer that requires strict raw-to-value normalization can reject the repair and silently invoke fallback. Keep raw evidence unchanged, align narrowly permitted corrections at the boundary, and test both acceptance and rejection through the HTTP adapter. This applies to cross-language OCR services; matching rules does not prove deployed accuracy or model correctness.