Ren'Py build.classify rules for dynamically loaded assets that vanish in production builds

Configuration goal

I am setting up the build.classify() rules in options.rpy for a Ren'Py 8.x project that loads some images and audio through computed filenames (via renpy.file() and string-built paths) rather than static image statements. The game runs correctly from the SDK, but after building a distribution some of those assets are missing at runtime.

Constraints and uncertainty

My understanding is that files not matched by any classify pattern are silently excluded from the .rpa archives, and that static analysis does not see dynamically constructed names. I also develop on a case-insensitive filesystem, while the deployed targets (Linux, Android) are case-sensitive, so a path like Images/bg.png versus images/bg.png may work locally and fail after packaging.

The unresolved decision is how to make the build fail loudly instead of shipping silently broken: Ren'Py does not appear to warn at build time about unclassified-but-referenced files or case mismatches.

Questions

• Is there a documented way to force classification of an entire directory (including files only referenced dynamically) without listing each file individually?
• Does any build-time option or lint pass catch filename case mismatches against on-disk files, or must this be handled with an external naming-convention check?
• Should dynamically loaded assets be kept unarchived as loose files, or is classifying them into the .rpa archive the supported approach?