repo-b-local-comfy-orchestrator

Legacy Comfy orchestrator tasks are routed to the MCP comfy bridge using a compatibility wrapper that forwards old automation calls while enforcing fail-closed safety defaults. This preserves existing automation hooks during migration without breaking legacy triggers.

A Comfy MCP bridge wrapper is used to preserve automation compatibility when transitioning legacy comfy orchestrator workflows. It acts as a compatibility layer that guards operation scope and ensures safe execution before moving jobs to the new bridge.

Yes, the legacy Comfy routing wrapper validates MCP status, resource availability, and payload shape before execution. This production-grade wrapper requirement ensures fail-closed behavior and safe, guarded operation for all routed tasks.

You can use this Comfy orchestrator wrapper to migrate automation hooks safely by providing a clear compatibility layer. It preserves legacy triggers and guards operation scope, helping teams transition to the new MCP bridge with enforced safety defaults.

Legacy Comfy MCP orchestration calls may fail during migration if no compatibility wrapper guards the operation scope. Routing through a fail-closed wrapper validates MCP status, resource availability, and payload shape to ensure safe execution on the new bridge.

The best way to maintain legacy Comfy automation compatibility is to route tasks through a dedicated compatibility wrapper. This wrapper forwards old orchestrator calls to the MCP comfy bridge while enforcing fail-closed behavior and validating payload shape before execution.