Refactor ConsoleAppAdapter termination flow away from stop() #473

Summary

Refactor console execution flow so ordinary command termination no longer depends on stop() and StopExecutionException.

Goals

• preserve ConsoleAppAdapter::start(): ?int
• preserve meaningful non-zero exit codes
• replace exception-driven ordinary console exits with explicit return flow

In scope

• src/App/Adapters/ConsoleAppAdapter.php
• console-related helpers or stages using stop()
• console adapter tests
• command execution flow where exit codes are produced

Why console is separate

Console semantics differ from web:

• web usually just returns 0
• console exit codes are part of the command contract
• scripts, CI, and schedulers depend on non-zero failures

Acceptance criteria

• ordinary command flow is explicit and return-based
• exit codes remain meaningful
• ConsoleAppAdapter no longer depends on StopExecutionException for ordinary exits

Validation

• console adapter tests
• command tests
• manual verification of success and failure exit codes if needed