## Problem `drush/drush` is required with a **different dependency type** on each platform. ### macOS (`install-macos.sh`) ```bash ddev exec composer require --dev drush/drush ``` Drush is added as a **dev** dependency (`require-dev`). ### Linux (`install-linux.sh`) ```bash ddev exec bash -c 'cd web && composer require drush/drush --no-interaction' ``` Drush is added as a **production** dependency (`require`). ## Impact - The generated `composer.json` differs between platforms for the same installer, so a site created on macOS vs Linux is not reproducible. - If the site is later deployed with `composer install --no-dev`, Drush is present on Linux-generated sites but **missing** on macOS-generated sites — a real functional difference that can break deploy/CI scripts relying on `vendor/bin/drush`. ## Proposed direction Standardize on one dependency type across both installers. Drush is typically a tooling/CLI dependency and is commonly placed in `require-dev`, but the choice should be deliberate and identical on both platforms. Whichever is chosen, update both scripts to match. Note: `drupal/ai_best_practices` is already required as `--dev` on both platforms, so this issue is specifically about the `drush/drush` line. ## Steps to reproduce 1. Run the installer on macOS → inspect `composer.json`: `drush/drush` is under `require-dev`. 2. Run the installer on Linux → inspect `web/composer.json`: `drush/drush` is under `require`. --- *Reported after a code read of branch `1.0.x`. Issue drafted with AI (Claude) assistance.*