v0.5.0 — Experimental external recovery

Experimental external recovery

v0.5.0 publishes advanced-user recovery research and operational guides. It does not turn on automatic recovery through the standard installer or update command.

Included

• Authenticated HTTPS observation delivery, subscription/delivery health checks and bounded network operations.
• Durable one-claim-per-incident execution, explicit eligibility/retry information, preflight reports and bounded reminders after observed policy limits clear.
• A separately deployed broker with dedicated-account/Unix-socket isolation, resource limits and protected OAuth admission. Interactive requests and public token requests have separate capacity; public requests have bounded per-IP concurrency/rates using a proxy-overwritten identity header.
• English/Korean operating guides, all-language README scope notes, lifecycle evidence, stop/rollback instructions and monitor restart guidance after Python upgrades.

Scope and evidence

The four installed executable sources are unchanged from v0.4.0; package metadata advances to 0.5.0. Tailscale remains 1.102.4. The broker, external observer, OAuth/SSO setup and Dots task are separate, explicit operator setup. The default claim policy is 3 per rolling day with a one-hour interval; the maintainer trial explicitly uses 12 with the same interval.

External logs confirm three recoveries after changed boot IDs, bounded at 7m35s, 9m45s and 7m34s. This does not distinguish VM replacement from reboot, independently prove exact execution counts, or guarantee immediate recovery. Other-account fresh setup and wider lifecycle/maintenance coverage remain open under v0.6.0. Support remains experimental.

Validation and files

Release checks cover core tests (256 on Python 3.11/3.13), research tests (179 on Python 3.12/3.13), lifecycle tests (11 on Python 3.12/3.13), shell checks and secret scanning. Code/security review and exact final commit verification are recorded in PR #46.

Eight attached assets: complete ZIP and tar.gz source archives, tailscale-setup.sh, shim.py, dots-ts, dots_proxy.py, source-manifest.json, and SHA256SUMS. Keep the four source files and matching manifest together. Research code is included in the complete archives but is not installed by the standard five-file installation bundle. Checksums establish consistency, not independent publisher identity.

Publishing does not modify existing installations. See the operator guide, 한국어 안내, and release notes.