Localization & Visual Aliasing

The custom-item path supports owner-scoped localization and template-based visual aliasing.

The runtime tests have independently resolved a custom item's name and description through the API's English localization path. Visual aliases are tracked as owned custom-ID → template relationships so a custom identity can reuse a proven native presentation source without rewriting the source template.

Practical rule

Treat a visual alias as presentation reuse, not ownership of the native template. A custom item should keep its own namespaced identity while borrowing only the presentation data the API explicitly aliases.

Full equipment-render and every live character/equip path should remain version-specific documentation because those paths depend on FTK2 consumer behavior.