Repository navigation
v0.4.4
miao v0.4.4
v0.4.4 fixes a real leak in yesterday's merged status row and makes the first run say what to do instead of going quiet.
The merged row no longer stacks
The status strip's clickable ranges were never cleared between paints — the field doc said "cleared on every paint" but no code did, and clicking still worked because the first covering range wins. The merged footer changed that arithmetic: it reports every range to the host, so a session left open overnight reported the same two facts 240 frames over — 480 segments on mtty's status row. Both panes now clear their hits at the top of their paint, and double-paint tests pin the wire to exactly what the current frame laid out (#3262).
The first run names the setup step
On a fresh install with no provider key, /model used to hand the text to a Session — for an engine that cannot start yet — and the provider pickers sat silent waiting for a catalog no engine would serve. Chrome commands (/model, /theme, /sessions, /lang, …) now run where they were typed; Session-bound commands (/goal, /tag, /recall) and unknown slash text stay first prompts. And when the model picker or the provider list has no engine behind it, it states the setup step — the full miao auth login <provider> <key> command — instead of nothing (#3260).
Maintenance and verification
cargo fmt --check, cargo clippy --all-targets -- -D warnings and the full cargo test suite for the TUI crate run in CI; the Rust stable toolchain moved to 1.100 and the chrome is clean under its new lints.