Stop fatal errors when the SCSS or CSS folder is not readable - #279

Summary

• Done when: with the SCSS or CSS folder set to mode 000, the front end loads without a PHP fatal, and wp-admin shows "The SCSS directory does not exist or is not readable". Checked in Docker (WP 7.1.4, PHP 8.4): master prints Fatal error: Uncaught UnexpectedValueException on both; this branch doesn't.
• Fixes Permission Denied #187: DirectoryIterator and RecursiveDirectoryIterator throw when they can't open a folder, and nothing catches it, so one bad permission took down every page. The existing "directory exists" checks now also check that the folder is readable. The recursive change scan now skips unreadable subfolders (CATCH_GET_CHILD) and passes SKIP_DOTS to the right constructor; before, it was passed as the iterator mode.
• How this could fail: if a subfolder of partials is unreadable, its changes are no longer noticed, so the CSS goes stale without a warning until the main file changes and the import fails with a normal compile error. That's an improvement on a fatal, but it is silent.

🤖 Generated with Claude Code