yobiru 0.4.0 — tailnet access policy and upgrade recovery

Yobiru 0.4.0

• New installations accept authenticated Tailscale peers by default, subject to Tailscale network access and local deny rules. Restricted allowlist mode remains available.
• Existing allowlists remain active until a backed-up, explicit policy set --mode tailnet --apply migration. Access policy changes take effect on the next receiver or bridge authorization check.
• Deny rules cover messages, discovery, attachment access and pending wake attempts. Wake caps, session bindings, reply permissions and recipient-bound file tokens remain independent.
• update maintain --apply records release reminders and recovers previously queued upgrade notices after restart or offline periods. reminder-template --retry-notices prints an opt-in 15-minute/startup schedule.
• Notification retries retain their original identity and recipient. Unknown outcomes, damaged saved routes and revoked access do not cause blind resends.
• English, Chinese and Japanese documentation includes the 0.4 migration procedure.

No wire-protocol change, automatic remote installation, general offline message queue or centralized storage service is introduced. Existing receivers and Codex bridges must be upgraded before policy migration. Install the printed maintenance schedule explicitly and regenerate it after plugin upgrades.

Validation: packaged/loopback tests, Codex bridge and installer tests, package consistency/privacy checks, and 59 real Tailscale checks on one host. Multi-device rollout and operating-system timer installation are not part of this release preparation.