hot take: keep theme overrides out of core templates

i think we should keep theme-level overrides away from core templates unless there is no other option.

in my experience, once a pipeline depends on template overrides, every upgrade turns into a compare-and-fix job. that is fine for one-off branding work. it is not fine when the same override has to survive multiple releases. anyone else seen this turn into recurring maintenance?

for me the safer path is smaller extension points, less file copying, and fewer surprises when a core template changes.