yobiru 0.2.1 — Preserve existing agent workflows on upgrade

Existing Tailmsg deployments can migrate without sending specialized message types into the general Codex dispatcher or losing locally customized settings.

• Adds optional message-kind exclusions and a trusted local handler, shared by macOS and Linux. Inbox validation happens before routing; scans and queued retries honor the same exclusions.
• Bounds handler execution beneath the receiver timeout and cleans up the handler process group. A started handler is not automatically replayed after an uncertain failure; the inbox stays pending and the receiver log records the outcome.
• Preserves installed dispatcher instruction contents, authorized replies, CLI paths, timing, and routing settings during upgrades. Dry runs validate the merged configuration; rollback retains original instruction bytes.
• Updates English, Chinese, and Japanese documentation and plugin bundles.

Validation: 108 bridge/client/installer tests and 55 plugin tests passed. Private-information checks and deterministic archive builds passed. Release tests use isolated homes, fake services, and temporary sockets; live host migrations are separate operational acceptance, not a claim of universal platform compatibility.

The receiver protocol remains tailmsg v1, and existing data homes and fixed Codex sessions remain compatible. The plugin and marketplace archives below include SHA-256 checksums.