The embedded module has logic that creates either a ServerEnvironment or HostControllerEnvironment that silently ignores if one isn't created.

The methods to create these return wrapper objects around the environment objects that have methods to indicate whether not making the environment object available is a problem or is ok. The embedding code should use those and fail if not returning an environment is a problem.

The 'not a problem' reasons for not providing an environment are things like the launch args including "help", "version" etc. These are unlikely to be relevant to an embedded process, but they can be detected, and thus the error cases can be detected as well.