Lossless Template Archive
Archiving a template now hides its instances everywhere without rewriting them, so unarchive restores the structure you had.
Templates now archive like a visibility change, not a destructive cascade. That makes cleanup faster, keeps instance state intact, and makes unarchive behave like a restore instead of a repair job.
Hide Instances Without Rewriting Them
Archiving a template now hides its instances at read time across search, collectors, and list views. The platform no longer needs to rewrite every child record just to make a template disappear from the visible workspace.
Unarchive Preserves Instance State
Because child instances are not rewritten on the way down, unarchiving is lossless on the way back up. Per-instance state stays intact, relationship edges come back correctly, and you avoid the old class of "template is back, but some of its structure is gone" cleanup bugs.
Shared Template Instances Respect Access
Template-instance access checks now work across categories instead of only one narrow artifact path. If a shared template produces PDFs, canvases, or other instance types, teammates with access to the template can reach those instances consistently even when the local index has not warmed yet.
Open Views Refresh After Bulk Archive
Bulk archive and unarchive now send explicit invalidation signals so open artifact views re-read their lists instead of showing stale children. If you archive a template while someone is already in the workspace, the UI should catch up immediately instead of hanging onto ghost rows.
What to Expect
Archive a template and its instances should disappear together. Unarchive it and only the items that should be visible return, with their previous state preserved.