List Stock Allocations

Which projects are standing on these lots, and how much each one holds.

THE LEDGER IS SIGNED AND APPEND-ONLY. A claim is a positive row and a return writes a negative one rather than editing or deleting the original, so "what is allocated right now" is a SUM per allocation, never a row count and never the newest row. A part claimed 6, returned 2 and claimed 3 again is three rows netting 7, and any of the three read alone is wrong.

Rows are grouped by the mirrored BOM row, because that is the unit the release endpoint takes and the unit a person sees on the project's own materials table. An allocation whose mirror has already gone is netted to zero by its own reversal and drops out here with it.

The caller passes the lots it is showing - a SKU drawer holds several - so this answers for a whole part without the endpoint needing to re-derive which lots fold together. Every id is still checked against the caller's shop: the list arrives from the client and a bare id is not a permission.

catalogPartId also includes every lot of that identity so a project buy written at QC is found even when the drawer only named sibling lots.