zurich_kotak/src
Yashas e32916cad3 Read the extract response correctly, and fail visibly
/ocr-extract answers { extracted: {...}, raw: "..." }. The client checked
`fields` first and `extracted` second, which was right by luck — but an
extraction that returned nothing, or threw, did so silently: the button
went back to idle and the operator had no way to tell a read from a
no-read.

Now an empty or failed extraction says so under the field, and either
way the UPLOAD survives. The file is already stored and referenced; a
failed read only means the fields are not pre-filled, which someone can
recover by typing. Losing the upload because the read failed would not
be recoverable.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-25 15:23:35 +05:30
..
api fix(upload): always send workflow_uuid 2026-08-25 13:46:51 +05:30
assets Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
components Read the extract response correctly, and fail visibly 2026-08-25 15:23:35 +05:30
layout Make the console operable: add a lead, work a lead 2026-08-24 16:11:28 +05:30
pages Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
screens Put dates where the work is decided 2026-08-25 12:52:26 +05:30
App.jsx Make the console operable: add a lead, work a lead 2026-08-24 16:11:28 +05:30
index.css Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
main.jsx Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
runtimeConfig.js Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30