Product Decisions This Supports

Build vs. buy: v0.7.0 strengthens the case for using this Laravel/Prooph integration instead of maintaining custom glue for message detection, handler registration, and async routing. The release reduces boilerplate for teams adopting CQRS/event-sourcing patterns in Laravel.
Feature and roadmap choices: Support for private message handlers and private constructors lets product/engineering keep domain messages and handlers encapsulated rather than exposing them publicly just to satisfy framework integration. This is useful for bounded contexts with strict domain boundaries.
Architecture bets: The async_switch router fix and relaxed message detection via HasMessageName make the package more viable for message-driven workflows where commands/events are routed to async transports.
Use cases: Laravel applications exploring command/query buses, domain events, event sourcing, or Prooph-based messaging; internal domain models that should not be forced into public DTOs; teams already comfortable with Prooph concepts.
Risk management: Treat v0.7.0 as pre-1.0 infrastructure. Use it behind a bounded context or pilot, not as a platform-wide dependency without an exit plan.

When to Consider This Package

Consider it when the product needs Prooph-style messaging/CQRS/event-sourcing inside Laravel, and the team values container-integrated handlers, message routing, and async switch configuration.
Consider it when domain messages/handlers are internal implementation details and you want to avoid making constructors or handlers public solely for detection/registration.
Consider it when the team can tolerate pre-1.0 API churn and has enough Prooph/Laravel expertise to debug routing, message detection, and async transport configuration.
Look elsewhere for simple CRUD apps, teams without CQRS/event-sourcing needs, or products requiring a stable v1 API and broad community support.
Look elsewhere if the roadmap depends on extensive first-party documentation, long-term compatibility guarantees, or a large ecosystem of Laravel-native packages. v0.7.0 improves docs, but the package remains niche and pre-1.0.

Executive summary: This package is a targeted integration layer between Laravel and Prooph messaging patterns. v0.7.0 improves flexibility for encapsulated domain code and fixes async router configuration, making it safer for a focused CQRS/event-sourcing initiative. It is not a general-purpose platform bet and should be piloted within one bounded context.
Engineering summary: v0.7.0 allows private message handlers, supports message detection with private constructors, relaxes detection to require only Prooph\Common\Messaging\HasMessageName, and fixes async_switch router configuration. These changes reduce boilerplate and coupling for domain-driven message flows.
Key trade-off: Adopt for teams already investing in Prooph/Laravel CQRS patterns where the package removes custom integration work. Avoid if the product needs stable APIs, simple CRUD delivery, or minimal operational complexity.