When a module in the Forge platform contains both a remote and a resolver, the routing of invocations becomes ambiguous. This ambiguity can lead to errors such as Invalid response from remote indicating that invoke() calls are being incorrectly routed to the remote backend instead of the Forge resolver. The platform currently expects either a remote or a resolver for a given module, but not both, leading to potential defaulting to the remote backend when both are present.

As an app developer, we would like to have comprehensive documentation that clearly outlines the expected behavior when both a remote and a resolver are present in a module. Also, provide an option to use both invoke and invokeRemote in the same module.