package-compatibility.yml needs the declared min/current PHP x Laravel matrix

MODULES.md §24.1 fixes a module repository at exactly three workflows, one of which is compatibility.yml — evidence that the package works against its declared minimum and current PHP, Laravel, database and Filament/Livewire versions.

package-compatibility.yml does not currently run that matrix.

Ask

A matrix over:

• PHP — the package's declared minimum and the current release
• Laravel — same
• Optionally the database and Filament/Livewire versions where the package declares them

Driven from the package's own composer.json constraints rather than hard-coded here, so a package that widens or narrows its support states that in one place.

Why it matters

A compatibility workflow that tests one version combination is a tests.yml with a second name. The fleet already spans a wide range — ecommerce-laravel is on spatie/laravel-permission ^8.3 while boilerplate-laravel is on ^7.0, and no module is verified against v8. That skew is exactly what this workflow exists to surface, and it currently cannot.

Found while planning module CI for ecommerce-laravel.

Start with package-compatibility.yml and compare it with the package's composer.json constraints. Read MODULES.md §24.1 and inspect the existing workflow to understand the expected compatibility checks. Done means the workflow derives the declared minimum and current PHP and Laravel versions, with optional database or Filament/Livewire coverage, and runs the resulting matrix.