Issue with DurableDeferred in @effect/workflow When Workflow Not Registered
Just stumble upon a massive gatcha when using DurableDeferred from @effect/workflow
When calling Entities and executing Workflows from a process in client only mode, we don't need to include these entities\workflows in this process. However when calling DurableDeferred.succeed or fail, if the workflow which created the deferred token is not registered in current process, I get an error here. This breaks the usual safety provided by Effect. Using deferred should either not require workflow to be registered in current proces, or it should force that it is through Requirements.
When calling Entities and executing Workflows from a process in client only mode, we don't need to include these entities\workflows in this process. However when calling DurableDeferred.succeed or fail, if the workflow which created the deferred token is not registered in current process, I get an error here. This breaks the usual safety provided by Effect. Using deferred should either not require workflow to be registered in current proces, or it should force that it is through Requirements.
