TautWeekly for Plex v0.12.3

v0.12.3 keeps older email-based delivery exclusions visible and truthful in
the Windows Manager while tightening the synchronization and styling completed
in v0.12.2.

Preserve legacy exclusions without exposing addresses

Older Windows configurations can contain ExcludedEmails even when
ExcludedUserIds is empty. TautWeekly still enforces those email rules, but
the guided Tautulli choices previously showed only ID-based exclusions.

The Manager now matches legacy email rules to the saved Tautulli roster on the
server. A matching user appears checked and labelled Legacy email
exclusion. That row is protected from ID-only editing because unchecking it
would not remove the underlying email rule. The header also reports matched
and total legacy-rule counts, making a stale or unmatched rule visible.

Raw email addresses never cross the Manager API and are never written to its
discovery cache. The browser receives only a match flag for the applicable
user and bounded aggregate counts. Existing ExcludedEmails values remain
unchanged in config.json.

Keep validation evidence synchronized

Dashboard's Integrations card and the Verify page now use the retained safe
setup result whenever a more detailed manual diagnostic result is not
available. Validate, save, and verify therefore remains the primary setup
and revalidation action. Manual Verify controls remain targeted reruns for
diagnosing an individual failure.

The production Manual Welcome user selector now uses the same height, border,
type, focus, menu containment, and responsive behavior as the preview and
TestEmail user selectors.

Let Windows Setup finish cleanly

Setup previously started the local Manager and browser before displaying its
final confirmation. On some Windows 10 desktops the browser could cover that
ownerless confirmation, leaving TautWeekly-Setup.exe waiting invisibly and
therefore locked against deletion or another update.

The completion dialog is now explicitly foregrounded. The Manager/browser
handoff occurs only after that dialog is dismissed, after which Setup exits
normally. A failed installation still retains the existing best-effort Manager
restart behavior, and --no-launch installations remain non-launching.

Update from v0.12.2 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 and confirm Update for the preselected installer-owned folder.
4. Open TautWeekly Manager and run Validate, save, and verify once.

For an older portable/BAT installation, select that exact installation folder
in Setup and confirm Migrate. Configuration, credentials, legacy email and
ID exclusions, history, previews, diagnostics, backups, password-lock state,
and an owned Windows Scheduled Task remain private and are preserved.

Validation and limitations

Release gates cover Manager and installer unit tests and vetting, JavaScript
and accessibility checks, eight maintained Manager cross-builds, repository
and privacy validation, reproducible archives, package contracts, and Windows
fresh-install/update/portable-migration/uninstall lifecycle testing. Desktop
and mobile browser QA used only fictional local fixtures. The real email values
shown in the user report were not copied into source, tests, logs, or release
artifacts.

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