feat(FN-3450): add mesh task create replication across nodes
Implements distributed mesh task creation by adding replicated create primitives to the core store, wiring new API routes (`register-mesh-routes.ts`) that replicate task creation across clustered nodes while preserving remote-targeting metadata, and updating the dashboard's task creation flow accord Fusion-Task-Id: FN-3450
This commit is contained in:
@@ -116,6 +116,8 @@ Within a project runtime, effective task routing resolves as:
|
||||
2. project default (`defaultNodeId`)
|
||||
3. local execution
|
||||
|
||||
Task creation also has a separate **transport node** concept: dashboard/API clients can route the create request through a remote node proxy while still setting `Task.nodeId` for where execution should occur later. Transport-node selection controls which node receives the HTTP write; `Task.nodeId` controls execution routing after the task exists.
|
||||
|
||||
This allows each project to maintain independent routing behavior even when managed from one central registry.
|
||||
|
||||
### Unavailable node policy in multi-project context
|
||||
|
||||
Reference in New Issue
Block a user