Hartmut/HartOMat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: execute workflow bridge nodes in graph runtime

Browse Source
This commit is contained in:
Hartmut Nörenberg
2026-04-07 10:42:59 +02:00
parent 6ad34ceed2
commit c17b7d2e8f
7 changed files with 699 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workflows/WORKFLOW_DELIVERY_CHECKLIST.md
+2 -2
View File
@@ -27,10 +27,10 @@
### Phase 4
- [x] Workflow context introduced
- [ ] Node outputs are persisted and reusable
- [x] Node outputs are persisted and reusable
- [ ] Graph runtime supports legacy fallback
- [ ] `legacy`, `graph`, and `shadow` modes exist
- Progress: Phase 4 foundation now persists `WorkflowRun` and initial `WorkflowNodeResult` records for both linked workflow dispatch and `/api/workflows/{id}/dispatch`, while keeping the legacy preset dispatcher as the safe default fallback.
- Progress: Graph dispatch now executes the extracted bridge nodes (`order_line_setup`, `resolve_template`, `material_map_resolve`, `auto_populate_materials`, `glb_bbox`) synchronously, persists per-node outputs/logs/durations onto `WorkflowNodeResult`, and continues to queue render/export nodes through Celery without changing the legacy preset dispatcher.
### Phase 5