Support item template route metadata

docs/prompt-architecture-improvement-plan.md

@@ -332,14 +332,17 @@ Keep here:
 - named scene/expression/composition pools;
 - item templates and axes;
 - direct category-specific wording.
+- optional object-style item templates with route metadata such as
+  `action_family`, `action_type`, `position_family`, `family`, `position_key`,
+  and `position_keys`; string templates remain valid and fall back to Python
+  inference.
 
 Improve later:
 
-- introduce optional `family` and `action_type` fields on item templates so
-  Python filters do less keyword guessing;
 - add `formatter_hint` fields only where needed, not globally;
 - keep `tools/prompt_map_audit.py` passing; it now checks referenced
-  expression/composition/scene pools and item-template axes.
+  expression/composition/scene pools and item-template axes for both string and
+  object templates.
 
 ### Node / UI Path