Template reuse does not provide reactive rendering

Reusing template markup creates component structure, but applications still need explicit logic for subsequent state changes.

A copied subtree is an instance, not a live subscription that follows changes to application data automatically.

MDN describes cloning as duplication, excluding listeners registered through JavaScript from the copied internal data.

Developers must therefore decide which nodes change, which events trigger updates, and where each instance stores state.

If cloning preserves structure, public contracts must still define how consumers change that structure.

Slots provide composition points for consumer content, rather than a general mechanism for reactive application state management.

Choose native templates for reusable markup, and select an explicit update strategy for behavior beyond initial construction.