d11listed

# Drupal 10 → 11 Upgrade Orchestrator (Dockerized / Makefile project) This skill **orchestrates** the upgrade: it owns the correct order, the Git cascade, and the D11-specific steps, and it **delegates** the three independently-reusable pieces to dedicated sub-skills: | Delegated to | Covers | Step | |---|---|---| | **`php-docker-upgrade`** | PHP 8.4 in Docker | 2 | | **`php-deprecations-audit`** | upgrade_status + rector + phpstan on custom code | 4 | | **`jquery-4-migration`** | jQuery 3 → 4 in the theme | 5 | Those sub-skills are usable on their own; here they run in sequence, wrapped in the Git/MR protocol below. When you reach steps 2, 4 and 5, **invoke the named sub-skill** and come back for the step's "Close" (MR) part. ## Golden rule: everything goes through the Makefile This project is **Dockerized and driven by a Makefile**. All Drupal commands run inside containers via `make`. **Never call `drush`, `composer`, `npm` or `php` directly** on the host — always use a `make` target. | Need | Make target | |---|---| | Generic Drush command | `make drush c='<cmd>'` | | Clear cache | `make cr` | | Generic Composer | `make composer c='<args>'` | | Add a dependency | `make composer-require <pkg>` | | Remove a dependency | `make composer-remove <pkg>` | | Run DB updates | `make updb` | | Export / import config | `make cex` / `make cim` | | Enable / uninstall module | `make en <m>` / `make pmu <m>` | | DB dump / import | `make db-export` / `make db-import <f>` | | Static