shadowdao
f3c175436a
treeToState had no resolvedName allowlist, so an AI `replace` response (scope site/page/header/footer, reaches this function via actions.deserialize with no further validation downstream) containing an unknown component could produce a state that throws at deserialize/render. Extract the core transform into standalone treeToCraftState (directly unit-testable without mounting a Craft.js Editor), route it through sanitizeAiTree for the same resolvedName allowlist + id/ROOT repair buildNodeTree already had, and fall back to the empty canvas if the tree's own root is invalid. Delegate the structural walk to the shared flattenTreeForCraft extracted in the previous commit. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
