Use explicit Tailwind source globs for app PHP, Blade, and JS

[kukac7]

Summary

This updates Tailwind @source entries to use explicit recursive globs for Sage’s project structure, while preserving PHP scanning in app/.

Why

Some classes were intermittently missing from generated CSS.
Using explicit file globs makes scan targets clearer and aligns with Tailwind/Laravel guidance, without relying on generated cache files.

Changes

• Keep scanning PHP sources in app/:
  • @source "../../app/**/*.php";
• Scan all Blade templates:
  • @source "../**/*.blade.php";
• Scan JS sources:
  • @source "../**/*.js";
• Remove cache-based source path:
  • @source "../../../../cache/acorn/framework/views/*.php"; (removed)

Result

Tailwind scans stable source files (app, Blade, JS) and avoids environment-dependent cached view paths.

[retlehs]

@kukac7 What is this fixing?

[kukac7]

@retlehs it has happened to me several times that certain class were not generated, even though they were in the code.

what's more, this is also the case in the tailwind doc.

[retlehs]

Pushed a small fix to your branch:

• Removed the cache source path (../../../../cache/acorn/framework/views/*.php) — those files may not exist in CI or clean builds
• Restored app/ PHP scanning (../../app/**/*.php) — without this, Tailwind classes in Composers/Components won't be detected
• Kept your explicit Blade/JS globs and switched quotes to double for consistency

Also updated the PR title and description to better reflect the final change.

[retlehs]

Thank you!