yobiru 0.4.2 — resident dispatcher and CLI reliability fixes

Yobiru 0.4.2 fixes three issues reported against 0.4.1.

• Linux resident dispatcher: the bridge daemon keeps its existing Codex session connected and resumes the same session after reconnecting. A separate resident status distinguishes subscription from queued or completed work. Resolves #1 via #6.
• Dispatcher sandbox setup: documents the minimum inbox/handled write permissions, optional attachment outbox access, and networking for authorized replies. Existing session permissions are preserved. Resolves #2 via #5.
• Non-UTF-8 output: the CLI no longer crashes on Chinese text or emoji in cp1252/ASCII pipes. JSON preserves Unicode values; message transport and storage remain UTF-8. Resolves #3 via #4.

Upgrade

Update the Codex/Cursor/Grok Bot plugin, or download the plugin archive below and verify it against SHA256SUMS. Then use the new package to run install-runtime --upgrade --apply and restart the receiver.

Linux Codex bridge users must also reinstall the bridge using the same thread UUID, Unix socket and Codex home. Keep your existing session, data, access policy and wake/reply permissions. Check codex-bridge status for resident.state: connected; a connection does not by itself prove task completion. See the upgrade skill and sandbox guide.

Validation

The combined tree passed 153 plugin tests, 132 bridge/resident/installer tests and 59 real Tailscale single-host checks. Package consistency, reproducible archive tests and private-marker checks passed. Encoding tests used real cp1252/ASCII pipes on Linux, not native Windows. Resident tests include isolated WebSocket lifecycle tests and real Codex app-server probes; they do not claim a completed real model task.

No wire-protocol change or automatic access-policy migration.