v2.17.0-dev.4

Fixed

• A stray pre-rename custom_components/lightener/ folder is now surfaced as a Repair issue. HACS caches the integration domain it first derived for a repository and keeps extracting zip_release updates into that folder (hacs/integration#931), so installs added before the lightener → lightener_studio rename can fail updates with No manifest.json file found 'custom_components/lightener/manifest.json' and end up with two integration folders that both claim the lightener_studio domain — Home Assistant then loads one of them unpredictably. The integration now checks for the stray folder at startup and raises a Repair issue (Settings → System → Repairs) with the cleanup steps: critical when both folders claim the domain, a warning for a dormant pre-rename leftover. The check only flags folders attributable to this project — an unrelated integration legitimately installed at custom_components/lightener (such as upstream Lightener) is never flagged, and the collision issue is only raised when both folders exist. The full diagnosis and fix sequence is documented in docs/TROUBLESHOOTING.md.