Seshat fills the bleed, names the original size and refuses unknown order keys
Scaling a print file to fill its order now covers the bleed as well, the answer names the size the file came from, an order with a misspelt key is refused, and each picture is listed once.
Four improvements to Seshat, Rekhu's print-file knower, for every app that uses it.
Fill covers the bleed
When a file has another shape than the order, fill used to cover only the trimmed size. It now covers the trim plus the order's bleed in one step. The page's own bleed is used when it reaches far enough; otherwise the artwork is enlarged just enough. A separate bleed fix is no longer needed, and the cropping no longer has to happen in your own app.
The size it came from
Every resize names the size each page had before (from_mm), measured from the file itself. There is no more working it back from the scale factor, which gave rounding errors such as 148.5 mm for a 148 mm page.
Unknown order keys are refused
An order with a key Seshat does not know, for example color next to colour, is refused before anything runs, and nothing is charged. The answer names the nearest known key. codes() now also lists every order key (code list 1.1).
Each picture once
After a mirrored bleed, the mirrored copies of a picture are no longer listed as extra pictures. The same picture placed twice at the same size is one entry with its count.
Nothing changes in your code: rekhu/core 0.3 for Laravel and Node uses all of this as it is.