fix: add channel() method to BroadcastPoolProxy

[binaryfire]

The Broadcast::channel() method was not exposed in the Broadcaster contract, causing static analysis tools to report it as undefined when using the Broadcast facade.

• Add channel() to Broadcaster contract interface
• Add channel() implementation to BroadcastPoolProxy
• Regenerate Broadcast facade annotations using facade documenter

[albertcht]

Hi @binaryfire, do we just need to simply change the class reference from \Hypervel\Broadcasting\Contracts\Broadcaster to \Hypervel\Broadcasting\Broadcasters\Broadcasters instead of adding channel implementation in the interface like in Laravel?

[binaryfire]

Hi @albertcht. You're right - I've updated the PR to follow Laravel's pattern. I've changed the @mixin and @see annotations to reference Broadcasters\Broadcaster instead of the contract, and reverted the interface change. The facade documenter now picks up channel(), getChannels(), flushChannels() etc. from the concrete class.

I kept the explicit channel() on BroadcastPoolProxy though - I think it's needed for pool safety? Without it, __call() would return the underlying broadcaster (which gets immediately released back to the pool), breaking method chaining. The explicit method returns $this (the proxy) instead.

[albertcht]

Hi @albertcht. You're right - I've updated the PR to follow Laravel's pattern. I've changed the @mixin and @see annotations to reference Broadcasters\Broadcaster instead of the contract, and reverted the interface change. The facade documenter now picks up channel(), getChannels(), flushChannels() etc. from the concrete class.

I kept the explicit channel() on BroadcastPoolProxy though - I think it's needed for pool safety? Without it, __call() would return the underlying broadcaster (which gets immediately released back to the pool), breaking method chaining. The explicit method returns $this (the proxy) instead.

Thank you so much! Yes, I think we should keep channel() on BroadcastPoolProxy.