{"version":"2.1.299","anchor":"ui-node-validation-engine-nodes-accept-only-type-and-ref-s","canonical_anchor":"ui-node-validation-engine-nodes-accept-only-type-and-ref-s","heading":"Stricter checks on engine elements in Claude-built interface layouts","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/ui-node-validation-engine-nodes-accept-only-type-and-ref-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Stricter checks on engine elements in Claude-built interface layouts\n\nEngine elements in interface layouts Claude builds may now have only a type and a ref, and scaled spacing counts toward the layout limit\n\n**Unclear.** Which feature these layouts belong to, and so who sees this change, is not stated.\n\n**What**\n\nWhen Claude builds an interface layout, an \"engine\" element may now carry only a type and a ref. Any other property is rejected with a message saying the engine node takes only type and ref. Before, only the ref was checked.\n\nValues taken from a named scale, such as spacing sizes, now count toward the layout's size limit.\n\n**Why**\n\nLayouts that Claude builds are checked more strictly, so some it produced before may now be rejected.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}