When a light module supplies a module descriptor, a node is added in the config workspace at /modules/[module name]. This node remains even if the the directory of the light module is removed.
This should not be the case because:

• Where possible, a light module should be gone if the directory is removed.
• If the module is removed and added again, the install does not occur again as one would expect. (I'm not sure if this has any impact in how the dependencies are evaluated.)

To be decided
How to handle this.
Some options:

• The node should not be added to the config workspace. (This would rule out any kind of version handling, which is probably ok for now.)
• At startup, or on file observation: If the module is removed, the node from the config workspace should also be automatically removed.