Test a JPG Name Collision Policy With Executable Examples
Two successful results can end up with the same output name. If a ZIP builder stores entries under those names as object keys, a later entry can replace an earlier one before the archive is written. Resolving the names first makes the collision visible and gives both results distinct names within that allocation. The allocator below is an educational policy, not the implementation of a product. Its input is an array of JPG leaf candidates after conversion, such as scan.jpg, not arbitrary source…