feat: add workflow node registry phase 2

docs/workflows/WORKFLOW_DELIVERY_CHECKLIST.md

@@ -4,18 +4,18 @@
 
 ### Phase 1
 
-- [ ] Canonical workflow schema finalized
-- [ ] Frontend and backend workflow types aligned
-- [ ] Preset workflow migration helpers added
-- [ ] Tests added for legacy preset conversion
-- [ ] Legacy dispatch remains default
+- [x] Canonical workflow schema finalized
+- [x] Frontend and backend workflow types aligned
+- [x] Preset workflow migration helpers added
+- [x] Tests added for legacy preset conversion
+- [x] Legacy dispatch remains default
 
 ### Phase 2
 
-- [ ] Node registry implemented
-- [ ] Node definitions API available
-- [ ] All required nodes have settings schemas
-- [ ] Editor consumes node definitions from backend
+- [x] Node registry implemented
+- [x] Node definitions API available
+- [x] All required nodes have settings schemas
+- [x] Editor consumes node definitions from backend
 
 ### Phase 3
 

docs/workflows/WORKFLOW_MIGRATION_PLAN.md

@@ -4,6 +4,12 @@
 
 Bring `/workflows` to full production parity with the existing legacy render pipeline without breaking the current legacy path at any time.
 
+## Current Status
+
+- Phase 1 completed on canonical config storage, preset migration, and legacy-safe runtime extraction.
+- Phase 2 completed on backend node registry, node definitions API, and schema-driven editor palette/settings.
+- Next execution target: Phase 3 legacy step extraction for runtime parity.
+
 ## Non-Negotiables
 
 - The legacy render path remains operational throughout the migration.