Release 1.11.0 - Add deploy:run task selector with improved Windows interactive stdin handling · artisan-toolbox/maintainer

Added

deploy:run task selector: Introduces a new deploy:run task selector/CLI entry point that discovers available Deployer tasks and allows selection (notably for interactive use). It executes the selected task with the appropriate argument construction.
Unlock retry support (interactive): Adds support for re-running deployment after an interactive unlock flow, when the user confirms the retry.

Windows interactive stdin handling: Improves how interactive stdin is preserved and forwarded on Windows by using native IO instead of relying on Symfony Process stdin behavior, which could poll or mishandle input.
Test determinism improvements: Updates tests to derive PM2 numeric collision behavior from the executing Node process.
Test/fixture alignment for Windows: Preserves Windows fixture arguments and verifies the rebuilt CLI appropriately.
More isolated, parallel test execution: Runs Deployer tests in parallel while isolating subprocess environments to reduce cross-test interference.

Prevent Windows interactive deadlocks/blocks: Fixes interactive Deployer behavior on Windows by ensuring interactive input is inherited/forwarded directly to the Deployer subprocess, reducing the chance of deadlocks or failing reads.

Reproduce Windows stdin failures in tests: Adds/adjusts tests to reproduce Windows Deployer stdin failures using live test events.

README badge standardization: Standardizes README badges and keeps release-linked values consistent.

Style/formatting: Formats the Node collision fixture according to the configured Rector rules.
Integration-only merge: Includes integration work by merging the origin/1.x branch into the 1.x line (no additional functional changes are explicitly described beyond the merged commits).

Additive feature: The new deploy:run command is an additive capability intended to complement existing deploy usage.
Windows runtime behavior change: Interactive Deployer flows on Windows should behave more reliably due to the stdin forwarding changes; no public API changes are indicated.
Migration steps: No required migration steps are described. If you want to use the new selector/retry workflow, update your CLI usage/docs/scripts accordingly.