a corpus build queue starts before L0, not at L0

The frozen inventory supplied identities and mapper candidates but still did not say which images could enter the expensive build/run loop. Treating every recognized size as L0 would violate the project ladder: L0 requires a complete lift, C emission and native compile, while L1 requires at least 1,800 headless frames.

Raw traces, ROM material, local paths, and personal data are not part of this public record.