Add eventStream signature to ResponseFactory contract

[csfh]

Commit description

Adds eventStream to Illuminate\Contracts\Routing\ResponseFactory in order to add type support for this method, aligning this with the same behavior that we have for stream of which eventStream is a convenient wrapper.

Why this change

At this time the ResponseFactory contract does not include a signature for the eventStream method. However, the function does exist on the underlying concrete implementation returned by the response() helper.

Not having this included can cause some false positive warnings and errors when statically analyzing a codebase using the eventStream function, such as when using intellisense in VS Code. Additionally, this can throw off AI agents from using the method, even if directly instructed to (tested using Claude Sonnet 4).

The method is already described on the Response facade–this PR would align the response helper with the facade.

This is a additive feature and does not introduce breaking changes.

Of note:

I do not see any existing tests for eventStream, but here is additionally PRs for context on the function.

• [12.x] Enhance eventStream to Support Custom Events and Start Messages #54776
• [12.x] Only call the ob_flush function if there is active buffer in eventStream #55141

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.