yobiru 0.4.3 — current-IP routing after device rebuilds

Yobiru 0.4.3 fixes short-name routing after a Tailscale device is rebuilt or reinstalled.

• Each new send resolves the latest Tailscale status. A short name matches the DNS short name or reported HostName; the unique online match takes precedence over old offline records.
• Ambiguous names now produce an error with exact candidate names instead of routing by list order.
• Sending, device discovery (agents --peer), and explicit upgrade notices share the same lookup rules. Full MagicDNS names and explicit IPs remain exact targets.
• Updated the send skill and English, Chinese, and Japanese documentation.

Use a stable device name rather than a saved IP for routine messages. After rebuilding a cloud computer, restore its chosen Tailscale hostname and start its receiver. This update does not restore a lost login, move old attachment permissions or historical replies to a different identity, or add offline retries for ordinary messages.

Upgrade

Update the Codex/Cursor/Grok Bot plugin, or download the plugin ZIP and verify SHA256SUMS. Then run install-runtime --upgrade --apply from the new package and restart the receiver. If a Codex bridge is installed, reinstall it with the same thread UUID and existing configuration. Preserve data, session identities, access policy, wake adapters, and reply permissions.

Upgrade instructions.

Validation

The release passed 172 plugin tests (including 19 name-resolution regressions), 132 bridge/resident/installer tests, package consistency and private-marker checks. Tests cover IP changes, old offline nodes, name collisions, agent routing and preserved exact identities. The regression suite uses injected Tailscale snapshots and isolated HTTP peers; it does not claim a live Grok Bot rebuild or native Windows/macOS validation. Wire protocol v1 and access policies are unchanged.