Under the hood
Old legacy code path removed from the internal check that guards stale or handed-over artifact files
What
An internal function that decides whether an artifact file can still be safely read (used when guarding against stale or already-handed-over files) has dropped an old on/off switch and the entire branch of logic it controlled. That removed branch used to return specific reasons like legacy, not_plain_owner, strip_unsettled, control_bytes, interrupt_literal, and over_cap. None of this logic runs anymore.
Why
This is internal cleanup rather than a user-facing feature. It shouldn't change what you see, but if you ever encountered one of those specific stale-file error reasons before, it can no longer occur.