Artifact publish tracks a new set of reserved slugs alongside stranded ones, improving staleness and overwrite checks
What
The artifact publish tool now keeps a reservedMints set alongside the existing strandedMints set. A slug is added to reservedMints when a publish attempt reports a reservedSlug. Both sets are cleared together at the same reset points and on conflict, and reservedMints is also checked when deciding whether an artifact is stale.
A new neverPublished outcome is also handled, letting overwrite checks proceed as if the target slug had no prior page.
Why
This gives the artifact publish flow more accurate bookkeeping about which slugs are reserved versus stranded, improving how staleness and overwrite decisions are made when publishing artifacts.
What a 'mint' is and how an artifact being reserved differs from stranded is not explained.