TautWeekly for Plex v0.24.0

Released: 2026-08-28

Independent deleted-item cache refresh

Deleted-item cache coverage no longer depends on PreviewAll or on one selected
owner/administrator. When cache coverage changes, Validate, save, and
verify starts a dedicated local refresh for every currently
production-eligible included user. It inspects each user's current DaysBack
newsletter history in the selected movie and TV libraries, deduplicates the
qualifying live items, and applies the existing exact-GUID, metadata, poster,
retention, item-count, and byte-count boundaries.

The cache step changes directly to blue Running. When the refresh ends,
Manager performs and retains the full local storage, bounds, manifest, backup,
writability, and artwork-integrity verification. Failed retains its red
treatment; Warning remains amber and Passed remains green. Shared badge,
button, and card state transitions remain smooth, with the existing reduced-
motion behavior. Verify's SMTP boundary now uses the outlined mail_shield
symbol without changing the check or its security boundary.

Metadata preservation

A sparse later Plex/Tautulli metadata response no longer clears a richer cached
title, year, summary, genres, ratings, or rating key. Valid poster bytes and
their integrity hash can still refresh. Normal preview, test, and delivery
renders can continue to refresh qualifying live entries, but they are no
longer responsible for establishing multi-user cache coverage.

Explicit package commands

Use the package command only when an explicit refresh is useful, such as after
an expert edit outside Manager:

Windows:        20-REFRESH-DELETED-ITEM-CACHE.bat
NAS/Compose:    ./tautweekly.sh cache-refresh
macOS Docker:   ./tautweekly.sh cache-refresh
native Linux:   sudo tautweekly cache-refresh
FreeBSD Podman: sudo tautweekly cache-refresh

The refresh sends no email, does not change access, welcome, or schedule state,
and prints aggregate counts only. It is bounded to current newsletter-window
items; it does not crawl the whole Plex library and cannot recover an item that
was already deleted before any qualifying live capture.

Use the existing cache-status or 19-CACHE-DIAGNOSTICS.bat commands for a
share-safe health summary. Never share cache manifests, cached artwork,
configuration, tokens, GUID input, viewing history, recipient data, raw logs,
generated newsletters, or private paths.

Compatibility

Existing cache data and configuration remain compatible. Disabling the cache
continues to stop reads and writes without deleting retained entries. No manual
manifest migration is required.