mirror of
https://github.com/Tria-plc/edr-platform.git
synced 2026-09-07 14:15:44 +00:00
cb150e46b7
Marking a received item inspected advanced only the rows the operator ticked. A booking's cargo spans one inventory row per container, and a multi-truck arrival files a GRN batch per truck, so a six-container booking stayed half-inspected and never reached Ready To Load. Widen the selection to every still-inspectable row of the same booking before inspecting. Each row is then passed and advanced exactly as before — EXPORT to READY_FOR_LOADING, IMPORT to READY_FOR_PICKUP — so the whole booking moves together. The rows the operator actually ticked lead the response, and are kept even when ineligible so their skip reason still surfaces rather than being dropped silently. Rows already PASSED, rows in a status that cannot be inspected, and rows belonging to another booking are left alone. Ad-hoc inventory with no booking expands to itself. Also show yards by name in the receive and received queues. They selected yards.code, so the route column read KALITY, the internal code for the yard everyone calls GMP / Gelan Multipurpose Port. Verified: freight-api type-check passes; both new SQL statements EXPLAIN-validated against the dev database; 14 warehouse suites pass (78 tests, 5 of them new). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>