dhpk-laravel-testbench-matrixlisted

# Orchestra Testbench matrix Use this skill when a package supports more than one Laravel major. Testbench boots a Laravel application inside the package suite, but each Testbench major is tied to one Laravel major; each cell needs its own dependency graph. ## Working sequence 1. Load `references/testbench-recipes.md` and confirm the Laravel/Testbench mapping against the cell's package metadata. 2. Build one matrix cell per supported Laravel major and exclude PHP versions below each framework floor. 3. Pin Laravel and Testbench with `composer require --no-update`, resolve a fresh cell graph, and run the suite. 4. Add the lowest-floor cell and a real-consumer package-discovery job. ## Branches - Mapping or Composer install → `testbench-recipes.md` §Mapping and per-cell install. - Shared provider/facade setup → §Abstract TestCase. - SQLite/MySQL choice → §Database choices. - Floor or discovery validation → §Floor and discovery cells. - Failure triage → §Failure map. ## When NOT to Use - A package targets a single Laravel major and needs no matrix. - An application test suite that boots the real application instead of Testbench. - Service-provider, facade, publishing, or discovery design outside Testbench setup; use `dhpk-laravel-package-author`. - Semver or dependency-floor decisions; use `dhpk-composer-package-hygiene`. ## Output Return a CI matrix with one supported Laravel cell, correct Testbench pins and PHP excludes, a shared provider/facade-aware TestC