feat(solid): allow passing custom CliRenderer to render()

[remorses]

Adds support for passing a custom CliRenderer instance to the render() function as the second parameter, while maintaining backwards compatibility with the existing config-based API.

This enables use cases like rendering OpenTUI in a web browser via WebSocket, where you need a custom renderer implementation instead of the default CLI renderer.

import { createCliRenderer } from "@opentui/core"
import { render } from "@opentui/solid"

const renderer = await createCliRenderer({ /* custom options */ })
const { dispose } = await render(() => <App />, renderer)

// Later
dispose()

• render() now accepts either CliRendererConfig (existing) or CliRenderer instance (new)
• render() now returns { dispose } for cleanup when using custom renderer

This PR was written by Opus 4.5 under the strict supervision of @remorses

[Copilot]

Pull request overview

This PR adds support for passing a custom CliRenderer instance to the render() function as an alternative to the existing configuration-based approach. The change enables advanced use cases like rendering OpenTUI in non-standard environments (e.g., web browsers via WebSocket) where a custom renderer implementation is required.

Key Changes:

• The render() function now accepts either a CliRendererConfig object or a CliRenderer instance as its second parameter
• The function now returns { dispose } to enable manual cleanup of the component tree
• Type checking uses instanceof CliRenderer to distinguish between the two parameter types

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[kommander]

Oh I thought we did that already? Or was that just React and not solid @msmps ?

[msmps]

Oh I thought we did that already? Or was that just React and not solid @msmps ?

it never made it into main for solid! so this needs doing 👍