TautWeekly for Plex v0.12.1

v0.12.1 completes the Windows Manager's one-user Manual Welcome flow and makes
legacy direct-Plex configuration omissions recoverable without weakening the
Manager's local privacy boundary.

Choose one Manual Welcome or the full production send

Open Previews and use the guarded production-delivery card. Its newsletter
selector now offers:

• Manual Welcome · selected user — choose a Tautulli user, confirm the
  one-message production action, and run the renderer's existing
  SendWelcome mode.
• All eligible recipients — confirm and run the same SendAll production
  delivery used by the Windows schedule.

Both actions are non-cancellable once delivery starts. The Manual Welcome user
ID exists only for that operation, is cleared from the form after start, and is
not written to Manager history or returned by the API. Retained evidence is
limited to aggregate SMTP acceptance and sanitized operation status; SMTP
acceptance is not presented as inbox delivery.

The numbered 07-SEND-WELCOME-NOW.bat and 11-SEND-ALL-NOW.bat launchers
remain packaged as expert break/fix fallbacks. The Manager is the normal manual
delivery interface.

Recover older direct-Plex configuration safely

Some installations created before direct Plex support do not contain
PlexServerUrl or PlexToken. Setup preserved those configurations correctly;
the missing keys are a schema-era omission, not evidence that Setup deleted a
saved value.

The Config page now identifies that state and links directly to Connections.
For same-computer Windows Plex installations, the Manager can use the current
Windows account's Plex registry token without copying it into config.json.
It can also use a process-provided PLEX_TOKEN and the Plex URL reported by the
saved Tautulli connection. Public and link-local destinations remain rejected.

Runtime-recovered tokens are never returned to the browser, logged, or silently
persisted. An explicit Validate, save, and verify normalizes absent schema
keys, creates the normal timestamped configuration backup, and reruns the safe
checks. When no trusted recovery source exists, the Manager explains exactly
which URL or token must be supplied.

Shared package migration contract

The implementation guide now requires every future Manager package to preserve
existing private configuration, detect old-schema omissions, recover only from
trusted platform-specific sources, keep recovered secrets process-local, and
show a precise manual fallback. This contract applies to Windows, NAS and macOS
containers, native Linux, and FreeBSD/Podman work.

Update from v0.12.0 or an older verified installation

1. Download TautWeekly-Setup.exe and SHA256SUMS.txt from this release.
2. Verify the EXE against SHA256SUMS.txt.
3. Run Setup. Keep the preselected installer-owned folder and confirm
   Update.
4. For an older verified portable/BAT installation, select that exact folder
   and confirm Migrate. Setup does not scan drives or guess its location.
5. Open TautWeekly Manager, review Config's direct-Plex guidance, then run
   Validate, save, and verify before the next production delivery.

Configuration, credentials, choices, history, previews, logs, backups,
password-lock state, and an owned Windows Scheduled Task remain private and are
preserved by the verified update or migration process.

Validation and limitations

The release gates cover Manager unit tests and vetting, JavaScript and
accessibility checks, synthetic desktop and mobile browser QA, Windows renderer
fixtures, eight Windows/Linux/macOS/FreeBSD cross-builds, repository and privacy
validation, and Windows install/update/migration/uninstall lifecycle testing.
Automated browser and renderer tests use fictional data and do not contact Plex,
Tautulli, SMTP, or real recipients.

The Setup executable remains unsigned. Windows SmartScreen may identify it as
an unknown publisher; verify the downloaded file against SHA256SUMS.txt.