Module manager

## Purpose The module manager separates optional capabilities from the CMS core. It lets an operator enable only the services they sell and keeps unavailable areas out of customer and administrator navigation. Module changes are restricted to privileged administrators, protected by CSRF checks and recorded in the audit trail. ## Downloads and Licensing Downloads enables signed product delivery, customer download navigation and release access. Licensing depends on Downloads and controls licence key delivery, activation, validation and the administration workspace. The manager prevents invalid dependency changes, so Licensing must be disabled before Downloads can be disabled. ## Provider modules Game hosting, web hosting and VPS modules can be connected to their provider integrations from the same area. A provider is not considered ready merely because it is enabled: configure credentials, test the connection and review readiness before allowing automatic provisioning. ## Safe changes 1. Review affected products and active customers. 2. Disable dependent modules first. 3. Change the module state. 4. Refresh the affected dashboard or administration area and verify the navigation and API response match the new state. 5. Use the audit log if a setting did not change as expected. Disabling a module pauses its application surface; it is not a deletion tool. Product data, orders and private releases are retained so an authorised operator can restore the capability safely.