TautWeekly for Plex v0.22.0

This feature release adds the first supported registry-first macOS / Docker
Desktop deployment requested in issue #157.
It is a dedicated Mac image rather than a premature reuse of the distinct NAS
runtime profile.

Registry-first Mac deployment

• Public image: ghcr.io/sparkmoxie/tautweekly-mac:0.22.0
• Architectures: Linux amd64 and arm64 for Intel and Apple-silicon Docker Desktop
• Standalone release asset: TautWeekly-mac-compose.yaml
• Persistence: Docker named volume mounted at /data by default, with a
  documented UID/GID-aware bind-mount alternative
• Access: authenticated Manager at http://localhost:8787/ on loopback by default

The standalone Compose file needs no repository clone, source checkout, local
compiler, or local application build. It retains the established Mac Manager,
embedded scheduler, production health check, 30-minute graceful delivery
shutdown, read-only root filesystem, bounded no-exec temporary storage,
non-root runtime identity, dropped capabilities, and no-new-privileges setting.

Docker Desktop users can continue reaching Mac-hosted Plex and Tautulli through
host.docker.internal. Deliberate LAN or reverse-proxy exposure remains opt-in
through the documented bind, exact allowed host, and secure-cookie settings.

Tags, updates, and release gating

Use full semver for a readable deployment pin or the same tag plus its manifest
digest for an immutable CI/CD pin. latest, 0.22, and edge are mutable and
are not recommended automation pins.

Manager now identifies a standalone Mac registry deployment separately from the
archive package. Settings > Updates reports the running image and Compose
package version, validates that the stable release contains the standalone Mac
Compose asset, and keeps pull/recreate/rollback authority on the Mac host. The
container receives no Docker socket or privileged update helper.

The release workflow calls the same dual-image workflow used for ongoing image
validation. GitHub release publication waits for both NAS and Mac amd64/arm64
manifests, so a published release cannot silently omit its advertised registry
image. The Compose asset is included in SHA256SUMS.txt with the archives and
Windows installer.

Persistence, rollback, and compatibility

Pull/recreate preserves the named or bind-mounted /data, including
configuration, credentials, Manager authentication, schedules, output, and
delivery history. An interrupted pull or recreate can be rerun. Rollback restores
the previous exact semver/digest reference and recreates against the same data.
The documented flow never uses docker compose down -v.

The existing verified Mac archive/local-build path remains supported as a
temporary fallback and for existing installations. Its .env, data/,
architecture-aware local build, operation lock, health/version acceptance, and
coordinated package/image rollback are unchanged. No registry migration is
forced. Windows packaging, native Linux, and FreeBSD/Podman deployment models
are unchanged.

Validation and limitations

Automated checks cover repository and workflow contracts, Compose parsing,
release/checksum/reproducibility rules, Manager package/capability/update tests,
amd64 runtime boot and health, explicit access bootstrap without log exposure,
bind-mount ownership, named-volume ownership and recreation, persisted Manager
bootstrap state, same-bundle restart, read-only operation, and root-identity
refusal. The publication workflow builds the final multi-platform amd64/arm64
manifest with provenance and an SBOM.

A physical Intel Mac and Apple-silicon Mac running Docker Desktop were not
available in CI and remain explicit hardware acceptance gaps. No claim of
physical macOS validation is made. No real Plex, Tautulli, SMTP, or newsletter
recipient data is used by the automated release checks.

Source baseline: macOS 1.5.0. Other maintained platform source baselines are
unchanged from v0.21.4.