Remove temporary symfony/console ^7 pin once Infection supports Symfony Console 8

[Goosterhof]

Context

PR #29 pinned symfony/console: ^7.2 in require-dev as a temporary fix for a repo-wide CI breakage.

symfony/console v8.1.0 (released 2026-05-29) crashes Infection 0.33.x's mutation runner:

In Container.php line 194:
  Unknown service "Symfony\Component\Console\Helper\QuestionHelper"

Infection's DI container registers QuestionHelper as a service in a way Symfony Console 8 no longer supports, so composer mutation:ci aborts with exit 1 and fails the check job. Because composer.lock is gitignored, CI resolves dependencies fresh on every run; illuminate/* v13 permits Symfony 8, so the resolver began pulling v8.1.0 — turning green PRs red overnight with no source change.

Confirmed on both Infection 0.33.1 and 0.33.2.

Why this needs tracking

The pin silently holds the package's dev toolchain a full Symfony major behind. Left unattended it becomes invisible debt and will eventually fight illuminate/* once a future Laravel requires Symfony 8.

Done-when

• Infection releases a version compatible with symfony/console ^8 (watch infection/infection releases / a tracking issue there for the QuestionHelper service change).
• Bump infection/infection to that version.
• Widen or remove the symfony/console: ^7.2 constraint in require-dev.
• Verify composer mutation:ci green on a fresh resolve (Symfony 8 present).

References

• PR ci: pin symfony/console to ^7 — Infection mutation gate broken by Symfony Console 8 #29 (the pin)
• The crash reproduces locally with rm -f composer.lock && rm -rf vendor && composer install && composer mutation:ci.

🤖 Generated with Claude Code