### Problem/Motivation `SanitizeSubscriberCommands` plugs into `drush sql:sanitize` with the `SanitizePluginInterface` hook API: a `POST_COMMAND_HOOK` to run the sanitize, an `ON_EVENT` hook for the confirmation messages, and an `OPTION_HOOK` for its two options. It's registered through `drush.services.yml`. That API is deprecated as of Drush 13.7.0 and removed in Drush 14: - **Drush 13.7+** still runs the hooks, but logs a notice on every sanitize: "The …SanitizeSubscriberCommands::messages sanitize plugin is using a deprecated API." - **Drush 14** (currently `14.x-dev`) turns `sql:sanitize` into a plain Symfony command that only dispatches events. The hooks are never called, so a sanitize on Drush 14 silently leaves every Simplenews email address in place. For a privacy module, that's the worst way to fail. Drush 13.7.0 added the replacement: Symfony event listeners, discovered from a module's `src/Drush/Listeners/` directory. The same listener class works on both Drush 13.7+ and Drush 14. This was raised in the [security advisory coverage review](https://www.drupal.org/project/projectapplications/issues/3626090#comment-16785779) and deferred from #2, which documents that Drush 14 isn't supported yet. #### Steps to reproduce 1. Install the module on a site running Drush 13.7 or later. 2. Run `drush sql:sanitize`. The deprecated-API notice is logged. 3. On Drush `14.x-dev`, run `drush sql:sanitize`. Simplenews subscriber, subscriber-history and stats-item addresses are not anonymized, and the mail spool is not truncated. ### Proposed resolution Replace the hook-based plugin with a single event listener and support Drush `^13.7 || ^14`. 1. Add `src/Drush/Listeners/SanitizeSimplenewsListener.php` with `#[AsEventListener]` methods for three events, following Drush's own `SanitizeUserTableListener`: - `ConsoleDefinitionsEvent`: add the `--sanitize-simplenews-subscribers` and `--truncate-simplenews-mail-spool` options to `sql:sanitize`. - `SanitizeConfirmsEvent`: add the confirmation messages. - `ConsoleTerminateEvent`: when the command is `sql:sanitize` and it exited successfully, run the sanitize. 2. Move `sanitizeSimplenewsData()`, `anonymizeEmailColumn()`, `buildAnonymizeExpression()` and `isEnabled()` into the listener unchanged, so the SQL and cache-reset behaviour is identical. 3. Delete `src/Commands/SanitizeSubscriberCommands.php` and `drush.services.yml`, and remove `extra.drush.services` from `composer.json`. 4. Add `"conflict": { "drush/drush": "<13.7" }` to `composer.json`, so Composer refuses to install the module alongside a Drush version that can't discover the listener. Without it, an older Drush would silently skip the sanitize. 5. Update the README's requirements to Drush 13.7+ or 14. Supporting both APIs in one codebase was considered. It would mean keeping the hook class with a `drush.services.yml` constraint of `>=11 <13.7` next to the listener. It was rejected because the two copies must never both run on Drush 13.7+, every option would be defined twice, and it would need CI across four Drush majors. Drush 11 and 12 can't run Drupal 11 anyway, and Drupal 10.2+ can run Drush 13. ### Remaining tasks - [ ] Add the listener and move the sanitize logic into it - [ ] Remove the hook class, `drush.services.yml` and `extra.drush.services` - [ ] Add the `drush/drush` `<13.7` conflict to `composer.json` - [ ] Point the unit and kernel tests at the listener class - [ ] Make sure the functional test passes on Drush 13.7+, and on Drush `14.x-dev` if the CI can run it - [ ] Update the README requirements - [ ] Tag a release noting the new minimum Drush version ### User interface changes None. The `sql:sanitize` options, confirmation messages and anonymized address format stay the same. ### API changes - `Drupal\simplenews_sql_sanitize\Commands\SanitizeSubscriberCommands` is removed and replaced by `Drupal\simplenews_sql_sanitize\Drush\Listeners\SanitizeSimplenewsListener`. Neither is meant to be called by other code. - The minimum Drush version rises from 11 to 13.7. ### Data model changes None.