Applies rule 32's migration exception: each header still says what the
schema was, what changes and what it prevents, but task, milestone,
decision and rule ids are replaced by the practice they stood for, the
operator quotes by the decision, single-install counts are dropped, and
pointers to a deleted package and an external design doc are gone.
golang-migrate keeps no checksum, so editing applied migrations'
comments is safe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Black Keys' Ohio Players was grabbed 40 times in a day. FabledExchange
already held the torrent under another category from before Minstrel took
the downloads over: the add answered "duplicate", which counted as added,
and Exchange's listing, filtered to Minstrel's category, never showed it.
Half an hour later the grab ended gone, and the next pass took it again.
- A duplicate add that the client does not list for Minstrel is not a
grab: the release is held back for a day with the client's own reason
(already downloading X (category)), and the search moves on. Forced,
it is refused with that reason.
- A release that ends gone a second time within a week is held back for
a day, whatever the cause.
- release_blocks gains the reason 'gone' (migration 0098), shown as
"Held back: its download client lost track of it".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>