Safe Delete and Rename Previews

Destructive changes can affect more than the selected row. Filmstrip uses preview-first workflows when deleting or renaming multiple objects, template-linked content, assets, tags, or other referenced definitions.

A preview may show

• Every selected object that will be removed.
• Template links or dependent instances affected by the change.
• References that block deletion or require repair.
• The destination of a rename or move.
• Name collisions that must be resolved before the operation can continue.

Repeat-to-confirm behavior

High-impact object and template-linked edits require a deliberate second confirmation after the preview. This keeps an accidental first click from immediately destroying a group of authored content.

Rename refusal

Object renames are refused when the requested name collides with an existing object or cannot be represented safely. Referenced project definitions and assets may also refuse rename or deletion until their dependencies are changed.

Undo after accepted changes

When a destructive scene operation succeeds, it enters the shared history with enough serialized information to restore object order and selection. Project-wide file operations use their own atomic rollback boundaries.