wtrenderlib 0.1.0

Dependency-free terminal rendering primitives for RGB and RGBA frames
Documentation
# Terminal compatibility

The library emits protocol bytes to a caller-provided `Write`. It does not
assume that stdout is a terminal and does not perform terminal queries during
rendering.

| Terminal/protocol | Backend | Status | Notes |
| --- | --- | --- | --- |
| Any ANSI terminal | Unicode half-block/quadrant | Supported | Requires truecolor for best output; fallback color policy is the caller's responsibility. |
| Kitty | Kitty graphics | Supported | Uses raw RGB/RGBA payloads and image ids. |
| Ghostty | Kitty graphics | Expected | Uses Kitty-compatible graphics sequences; verify against the target version. |
| iTerm2 | iTerm2 inline | Supported | Caller supplies encoded PNG/JPEG bytes. |
| WezTerm | iTerm2 inline | Expected | Enable the terminal's inline image support. |
| Sixel terminals | Sixel | Supported with `sixel` feature | Uses the pure-Rust `icy_sixel` encoder; disabled in the default build. |
| tmux | DCS passthrough | Supported | Use `Multiplexer::Tmux`; tmux must allow passthrough where required. |
| screen | DCS passthrough | Supported | Use `Multiplexer::Screen`. |

## Reproducible checks

The protocol tests validate escape sequence structure and payload encoding.
For a manual terminal check, run:

```text
cargo run --example render_raw
cargo run --example benchmark_render
```

`render_raw` exercises the dependency-free Unicode path. The benchmark prints
elapsed time for 100 deterministic 160x90-to-80x24 renders; compare results on
the same machine and terminal rather than treating it as a cross-machine
performance claim.

The GitHub Actions matrix runs these checks on Linux, macOS, and Windows. It
validates protocol generation and feature builds, but visual terminal behavior
still requires a manual check in the target emulator.