Development record

Two accepted mint residuals recorded so future hunts do not rediscover them as findings (spc-33 bounds-and-residuals section; surfaced by the pre-PR security review of the itd-114 delivery): (1) recordid's fileID rebuilds an id from the parsed integer, so a timestamp stamp with a leading zero — reachable only from a host clock in 2000-2009 or from 2100 onward — resolves to a different id than its filename claims (the year-2100 horizon the spec accepts); (2) the mint's rejection-sampling loop is uncapped, safe today because entropy is crypto/rand or an injected test reader that EOFs, but if Minter.Entropy ever becomes configurable from env/config/flags the loop needs an iteration cap. Neither has an attack path under the current wiring