v1.8.4 - Repair interrupted service advertisements

Fixes services becoming unreachable after an interrupted DockTail shutdown (#104, #106). DockTail now restores missing Tailscale service advertisements without rewriting matching Serve configuration. Ignored and conflicting services are preserved, and unreadable preferences do not trigger advertisement changes.

Shutdown cleanup runs once per service name, remains serial, and stops at its deadline. Its budget is now 8 seconds to fit Docker’s default stop timeout; no Compose changes are required.

This release also includes the changes on main since 1.8.3: ARMv7 images and static Linux binaries, version reporting and health checks, monitoring labels, Cloud reliability fixes, and expanded platform documentation.

Validation: all eight CI jobs passed, including 160 real-tailnet e2e assertions and the socket-loss suite. The #104 regression test was confirmed failing before the repair.

What's Changed

• fix(cloud): let slow HTTP checks degrade and classify status mismatches correctly by @marvinvr in #90
• feat(cloud): explain connection rejections and retry recoverable ones slowly by @marvinvr in #92
• refactor(cloud): stop sending the retired tailnet peer-liveness frame by @marvinvr in #97
• docs: platform guides, hardening, cloud compose example, complete env reference by @marvinvr in #95
• fix(cloud): tell Cloud whether an OOM kill actually stopped the container by @marvinvr in #100
• feat: add --version, a health check that tracks DockTail, and an update notice by @marvinvr in #93
• build: armv7 image, release binaries, gosec, exec-form entrypoint by @marvinvr in #94
• cloud: re-sync the proto copy with the cloud's source of truth by @marvinvr in #91
• feat(cloud): docktail.cloud.* labels for monitoring intent by @marvinvr in #96
• fix(cloud): discount shrinkable ZFS ARC from host memory used by @marvinvr in #102
• Fix service advertisement drift after interrupted shutdown by @marvinvr in #106

Full Changelog: 1.8.3...1.8.4