Is MultiControllerScope necessary, or should multiple ControllerScopes be composed manually? #10

Hello, and thank you for maintaining this project.

While reviewing existing issues and discussions related to ControllerScope, I noticed recurring mentions and patterns around using multiple controllers at the same level of the widget tree. Based on those discussions, it seemed that introducing a MultiControllerScope (similar in spirit to MultiProvider) might improve readability and ergonomics.

Before starting the implementation or opening any pull request, I wanted to ask for suggestions and guidance from the project owner/maintainers:

• Is a MultiControllerScope considered necessary or aligned with the intended design of this package?
• Are there any architectural or design reasons to avoid such an abstraction?
• Is manual composition of multiple ControllerScopes the preferred approach?

I wanted to check this in advance to ensure that any work I do would be useful and consistent with the project’s direction.

My urge to contribute to this project is quite strong, which is why I preferred to ask for feedback first rather than submitting an unsolicited implementation.

Thank you for your time and guidance.

PS: After further research and learning more about how MultiProvider works internally, I realized that such abstractions are largely a convenience and not strictly necessary. Apologies if this issue is redundant or premature. I wanted to make sure I fully understand the design intent before proceeding.