Destruction scheduling is now fully traceable at the package level.
Previously, users had to cross-reference the Submissions table or monitor status changes to determine when a package was scheduled for destruction and by whom. That context now lives directly where it belongs: in the Package Activity History.
