aj
d8656cc454
Task 7 extended JobStock.Quantity = -1 (unlimited) to catalog-sourced rows, but the post-pack classification step in CutListPackingService only ever treated a catalog-sourced bin as "in stock" when its tracked quantity was a positive finite number. An unlimited catalog row fell through to "to be purchased" even though IsInStock=true just means the bin is catalog-sourced, not a quantity check. This made the classification effectively unreachable for the most common path users take to stock a job: the "Import from Inventory" modal defaults every candidate's quantity to -1, so every resulting bin was mislabeled "to be purchased" on the Results tab, and the "everything is available in stock" message could never appear for jobs stocked that way. Track unlimited catalog-sourced lengths in a separate set and check it first; finite catalog quantities keep the existing decrementing-counter behavior, and custom-length stock (any quantity) is unaffected.