TautWeekly for Plex v0.17.1

TautWeekly for Plex v0.17.1

v0.17.1 corrects the Manager's update-available presentation. After a verified
stable comparison finds a newer release, the status chip inside Settings >
Updates now uses the agreed violet/purple color and a subtle purple pulse.
The existing purple update icon beside the Manager lock remains the direct link
to the same status card.

An active Checking state remains blue. This keeps a check that is still in
progress visually distinct from a completed, validated update result.

The pulse respects reduced-motion preferences, and the status retains a
high-contrast system-color treatment in forced-colors mode. The correction is
shared by every Manager package and the static GUI preview. It does not change
update discovery, package ownership, installation permissions, authentication,
or the Windows password-lock behavior.

Update existing installations

Back up private data, then use the documented update path for the installed
package. No configuration migration is required. Existing credentials,
schedules, generated newsletters, backups, history, Tailscale settings, and
Manager access settings remain unchanged.

Validation

The hotfix passed the dedicated update-indicator package, routing, motion,
mobile, preview, reduced-motion, and forced-colors contracts; production and
preview JavaScript syntax; Manager accessibility validation; repository,
branding, platform, documentation, link, reproducible-package, Windows
installer, and amd64/arm64 container checks. A local rendered-browser audit
confirmed the purple color, 2.9-second animation, and changing purple shadow.

TautWeekly for Plex v0.17.0

TautWeekly for Plex v0.17.0

v0.17.0 adds optional private Tailscale remote access to the TautWeekly Manager
across every supported package. Authorized devices can open the Manager through
an HTTPS .ts.net address without exposing a router port or enabling Tailscale
Funnel. The shared Settings card shows setup, status, recovery, and the private
address; while an integrated route is active, the entire card has a gentle green
pulse with a static reduced-motion alternative.

For optional mobile use, install and sign in to Tailscale on the phone or
tablet, then open the private address shown by Manager. This remains a private
tailnet flow, not a clientless public URL.

Remote access remains opt-in. TautWeekly does not install Tailscale, create a
Tailscale account, enroll devices, weaken Manager authentication, or silently
publish the service. Access through the tailnet grants full Manager
administration because v0.17.0 has no read-only remote role.

Package integration

• Windows: Enable, Disable, and Verify use a narrowly scoped UAC helper that
  can inspect or change only the exact TautWeekly HTTPS Serve route. Ordinary
  Manager operation remains unelevated. The existing Windows Manager password
  lock remains optional and unchanged.
• Native Linux: a host administrator runs
  sudo tautweekly remote-access-authorize once. This enables a root-owned,
  socket-activated adapter restricted to the tautweekly service account, the
  fixed loopback Manager target, trusted Tailscale CLI paths, bounded output,
  and Inspect, Enable, or Disable actions only. The Manager remains unprivileged.
• macOS Docker Desktop, FreeBSD Podman, generic Docker/NAS, Unraid, and QNAP:
  create private Serve with the host's supported Tailscale client, then paste
  the exact HTTPS .ts.net address into the authenticated Manager and confirm
  that Funnel is off. Manager stores only the hostname and never receives a
  Tailscale credential or host-control permission.
• Compatible Docker hosts without a supported native client: optional
  Compose sidecars provide userspace Tailscale with a fixed private Serve
  configuration, persistent node state, and a file-backed one-off enrollment
  key. They do not use the Docker socket, host networking, a TUN device, added
  Linux capabilities, privileged mode, or Funnel.

The Tailscale provider consent page can preselect Funnel when HTTPS certificates
are first approved. Enable HTTPS certificates only and turn Funnel off before
continuing. TautWeekly never requires public Funnel access.

Update existing installations

Back up private data, then use the documented update path for your package.
No configuration migration is required. Existing credentials, schedules,
generated newsletters, backups, history, and Manager access settings remain
unchanged. Private remote access starts disabled after update.

Windows and native Linux users install or update the official Tailscale client,
sign the host into their tailnet, then use the new Settings card. Container and
NAS users should prefer the vendor-supported host client or plugin; the optional
sidecar is a fallback and requires an administrator-created one-off enrollment
key stored only in the ignored local secret file. Empty that key file after the
node has enrolled and retained its state.

Security and recovery

Integrated adapters accept only one exact HTTPS Serve layout and refuse to
replace or reset an unrelated Tailscale configuration. TautWeekly validates the
.ts.net hostname, adds it to the Manager host allowlist only while enabled,
requires HTTPS origins for remote mutations, uses Secure and SameSite session
cookies, sends HSTS on the private hostname, and retains the existing
authenticated CSRF boundary and login throttling.

Disabling first removes the hostname from Manager's accepted hosts, then removes
only the verified route it owns. If Tailscale is offline or route cleanup cannot
be verified, local Manager access remains the recovery path and the UI reports
the incomplete cleanup. Linux authorization can be revoked only after private
access is disabled. Protect every enrolled device and review tailnet grants;
the Manager password is a second login boundary on non-Windows packages and
when the optional Windows lock is enabled.

Validation

The release passed Manager tests and Go static analysis on Windows and Linux,
Linux helper protocol and route-ownership tests, Linux amd64 and macOS arm64
cross-builds, PowerShell and shell parsing, repository privacy/secret scans,
JSON and Compose validation, accessibility checks, reproducible archive builds,
multi-architecture container builds, and the Windows installer lifecycle.

Live Windows acceptance covered enable and disable, mobile private reachability,
Manager restart, host Tailscale disconnect and reconnect, and Windows reboot
persistence. Automated tests use local or synthetic services and do not contact
real Plex, Tautulli, SMTP, private infrastructure, or provider resources.

TautWeekly for Plex v0.16.0

TautWeekly for Plex v0.16.0

v0.16.0 adds a passive update notification to the authenticated Manager. When
TautWeekly has validated that a newer stable application release is available,
a purple update icon appears beside the access lock. Its accessible label names
the available version, and activating it opens Settings > Application and
package status for package-specific status and guidance.

The indicator is shared by Windows, native Linux, macOS Docker Desktop,
FreeBSD Podman, NAS/Compose, QNAP Container Station, Unraid, and compatible
Docker hosts. It does not change update ownership: Windows retains its existing
verified updater, while host-managed packages continue to use their documented
package or image workflow.

Update existing installations

Back up private data, then use the documented update path for your package.
After v0.16.0 is running, the Manager can render a validated cached update state
on authenticated entry and refresh an absent or stale result once in the
background when retry backoff permits. The notification is guidance, not an
automatic installation control.

No configuration migration is required. Existing credentials, schedules,
generated newsletters, private state, backups, and package lifecycle boundaries
remain unchanged.

Privacy, offline behavior, and validation

The background refresh reuses the authenticated, CSRF-protected update endpoint
and its bounded timeout, metadata validation, persistent cache, concurrency
suppression, and sanitized retry backoff. It is not called from the login page,
health checks, every API request, or ordinary navigation. Dashboard rendering
and offline operation do not wait for a release check.

The icon stays absent for current, checking without a validated result, unknown,
offline/error-only, invalid metadata, rollback/downgrade, mismatched-only,
unsupported, and legacy-wrapper-only states. A package or image mismatch alone
does not produce an application-update notification.

Release gates test and vet the Manager and installer, validate JavaScript and
accessibility behavior, exercise cached/stale/fresh checks and package/version
matrices, cross-build every maintained Manager target, boot-test the shared
container and native Linux package, exercise the Windows installer lifecycle,
and build reproducible release archives. Browser QA covered desktop and narrow
mobile layouts, asynchronous appearance and disappearance, focus routing,
history navigation, reduced-motion/forced-colors contracts, and console health.
Automated tests use synthetic metadata and do not contact real Plex, Tautulli,
SMTP, user configuration, or updater services.

TautWeekly for Plex v0.15.2

TautWeekly for Plex v0.15.2

v0.15.2 fixes Manager update and configuration interactions across every
maintained package. Windows verified updates now reconnect to the restarted
Manager automatically, generated configuration switches respond across their
full visible surface, and build/package identity is presented once in the
application and package status card.

Update existing installations

Back up private data, then use the documented update path for your package.
On Windows, open Manager > Settings > Updates, run Check now, confirm
the verified stable update, and approve the Windows administrator prompt.

An already-open pre-v0.15.2 Windows tab still contains the older browser code,
so it may need one final refresh while moving to this release. Once v0.15.2 is
loaded, later verified updates reconnect and advance the page automatically.

No configuration migration is required. The Manager continues to preserve
existing credentials, schedules, generated newsletters, private state, and
package-owned lifecycle boundaries.

Scope and validation

The click defect came from shared Manager markup, not Windows configuration
storage: a non-label visual wrapper surrounded a checkbox whose pointer events
were disabled. The API already preserved explicit boolean false values.
Regression coverage now exercises the authenticated save path for Windows,
macOS Docker Desktop, NAS/Compose, QNAP, Unraid, compatible Docker, native
Linux, and FreeBSD package identities.

Release gates test and vet the Manager and installer, validate accessibility
and JavaScript, cross-build Windows/Linux/macOS/FreeBSD Manager binaries for
amd64 and arm64, build and boot-test the shared container image, exercise the
verified Windows updater with fixtures, and build reproducible release
archives. Automated tests do not contact real Plex, Tautulli, SMTP, or user
configuration.

TautWeekly for Plex v0.15.1

TautWeekly for Plex v0.15.1

v0.15.1 restores Manager previews, TestEmail delivery, and manual delivery in
the macOS Docker Desktop package. The Mac runtime now accepts the Manager's
private operation snapshot and emits the same sanitized structured result used
by the maintained NAS/Linux runtime.

Update existing Mac installations

Back up private data, then run this from the extracted Mac package:

./tautweekly.sh update

Sign back in to the Manager and retry Previews and the controlled
TestEmail check. No Docker Desktop or .NET reinstall, Plex/Tautulli
metadata refresh, configuration replacement, or manual file patch is needed.

Scope and validation

The defect was limited to the Mac package's operation wrapper and renderer.
Windows, NAS/Compose, QNAP, Unraid, compatible Docker, native Linux, and
FreeBSD packages already carried the required Manager operation contract.

Release gates exercise the exact Manager command with mock paths against both
Mac and NAS wrappers, boot-test the Mac image, validate PowerShell and shell
source, build reproducible ZIP/TAR archives, and require the structured-result
contract in every packaged renderer. Automated tests do not contact real Plex,
Tautulli, SMTP, or user configuration.

TautWeekly for Plex v0.15.0

TautWeekly for Plex v0.15.0

v0.15.0 makes Manager Settings > Updates the truthful update-status source
for every supported package. It separately identifies the running Manager and
application, host package, container image, and host-adapter contract; compares
them with the latest verified stable release only on request; and gives each
platform its exact safe next step without transferring host privileges to the
web process.

Update existing installations

Back up private data, sign in to the Manager, and open Settings > Updates.
Choose Check now to perform one bounded stable-release check, review the
reported application/package/image state and release notes, then follow the
owner named by the card:

Package	Update owner and action
Windows Manager	Confirm Install update after a fresh successful check. The Manager starts the existing verified updater; Windows still requests administrator approval.
Native Linux	Run sudo tautweekly update on the host.
macOS Docker Desktop	Run ./tautweekly.sh update from the extracted Mac package.
FreeBSD Podman	Run sudo tautweekly update on the FreeBSD host.
NAS / Docker Compose	Run ./tautweekly.sh update from the extracted NAS package.
QNAP Container Station	Run ./tautweekly.sh update over trusted SSH, confirm the recreated application in Container Station, then return to Settings.
Unraid Community Apps	Use Docker > Check for Updates or the Apps flow and compare the saved template when Settings reports a legacy host adapter.
Other compatible Compose hosts	Run docker compose pull tautweekly, then docker compose up -d --no-build --force-recreate tautweekly from the original stack.

Return to Settings > Updates after installation to confirm that the
application, package/image, and host-adapter layers agree. Then run the normal
Manager verification, PreviewAll, and controlled TestEmail acceptance flow.
Routine TautWeekly updates do not require a Plex or Tautulli full-library
metadata refresh when current output is already correct.

Truthful status and failure handling

The card reports the stable channel, latest stable version, last successful
check, last sanitized failure, release notes, and one of the following states:

• Current when the reported application and package layers match stable.
• Update available when stable is newer.
• Legacy wrapper when a maintained container package reports an older or
  missing host-adapter contract.
• Version mismatch when the running application/image and host package do
  not agree.
• Newer than stable without offering a rollback or downgrade.
• Unknown when no verified comparison is available, the package cannot
  identify a version, or the configured channel is unsupported.

Normal Manager refresh, dashboard health, scheduling, newsletter delivery,
first-run setup, backup/recovery, and graceful shutdown remain local. They do
not contact GitHub and continue to work when the Internet or release service is
unavailable.

Security boundary

Check now uses a fixed GitHub stable-release endpoint, an eight-second
deadline, bounded response and private-cache sizes, rejected redirects, exact
stable tag/release/asset URLs, required checksum-manifest metadata, sanitized
errors, and bounded exponential backoff. Cached metadata is validated again
before it reaches the API or UI.

The update endpoints inherit the Manager's authentication, authorization,
session, CSRF, same-origin, allowed-Host, reverse-proxy, secure-cookie,
security-header, and throttling boundaries. Browser input cannot supply a URL,
path, version, command, executable, script, or updater argument.

Windows is the only package with an in-GUI install action. It requires a fresh
successful stable check and separate confirmation, then invokes the existing
fixed Check-Update.ps1 path with fixed arguments. Its UAC approval, archive
checksum, internal manifest, backup, health verification, and rollback remain
authoritative.

Docker and NAS Managers remain non-root and cannot mutate the host. This
release does not mount the Docker socket, add privileged mode, introduce a
helper daemon, invoke sudo or a container engine from the web process, or claim
unattended/one-click installation on a host-managed package.

Host-adapter compatibility

Maintained container packages now report host-adapter API 3 and embed their
release package version in staged Compose manifests. Updating only a container
image may therefore produce a truthful Legacy wrapper state on an older
Compose file, QNAP application, Mac package, FreeBSD rc.d adapter, or saved
Unraid template.

Use the platform owner and migration steps shown in Settings to advance the
host package or saved template. Do not weaken container isolation to hide the
mismatch. Private .env, /data, configuration, credentials, schedules,
history, previews, and backups remain outside release-owned package files.

Validation and limitations

The release gates cover Manager unit, contract, security, accessibility, and
cache-tampering tests; offline, timeout, malformed/oversized metadata,
redirect, prerelease/channel, rollback/downgrade, legacy wrapper, mismatch,
authentication, CSRF, Origin, Host, reverse-proxy, and Windows installer
cases; Windows, Linux, macOS, and FreeBSD cross-builds for amd64 and arm64;
ShellCheck, PowerShell, Compose, Unraid, documentation, link, and repository
contracts; mocked newsletter and SMTP integration; multi-architecture container
build and boot tests; reproducible release archives; and the isolated Windows
installer lifecycle. No real Plex, Tautulli, SMTP, or user configuration is
contacted by automated tests.

Physical QNAP, Unraid, macOS, and FreeBSD host behavior, NAS-vendor reverse
proxies and storage ACLs, Community Applications moderation, and real mail
providers remain environment-specific acceptance checks. No QPKG or app-store
submission is included.

TautWeekly for Plex v0.14.1

TautWeekly for Plex v0.14.1

v0.14.1 completes the GUI-first host experience introduced in v0.14.0. It
ships verified package-aware updates for NAS/QNAP Compose, macOS Docker Desktop,
native Linux, and FreeBSD Podman; adds the tailored authenticated Manager to the
Mac and FreeBSD packages; repairs older v0.14 host wrappers; and lets an
administrator permanently delete individual configuration backups from the
Manager.

Update existing installations

Back up private data first. On current NAS/QNAP Compose and macOS Docker Desktop
packages, run:

./tautweekly.sh update

On native Linux or FreeBSD Podman, run:

sudo tautweekly update

These commands now download the matching stable host archive and
SHA256SUMS.txt, validate its published checksum, reject unsafe archive
entries, verify the internal release-file manifest, preserve private data and
environment settings, update the host adapter and runtime together, and roll
both back when candidate health or version checks fail.

Unraid continues to update the image through Docker > Check for Updates or
Apps > Previous Apps. Administrators upgrading an older saved template
should apply the documented one-time template migration so the current Manager
environment, read-only hardening, stop timeout, and host-adapter compatibility
marker are present.

One-time v0.14 bridge

If an older NAS wrapper does not list manager-bootstrap, use the documented
direct container bootstrap command once, finish pairing in the Manager, then
apply v0.14.1. If an older FreeBSD wrapper omits that command, verify and extract
the current FreeBSD archive and run:

sudo ./install-freebsd.sh --upgrade-and-update

For an older native Linux archive, verify and extract v0.14.1, then run
sudo ./install-linux.sh --upgrade. The platform QuickStarts contain the exact
download, checksum, recovery, and post-update validation steps.

Mac and FreeBSD Manager packages

The macOS Docker Desktop and FreeBSD Podman packages now expose the shared
authenticated Manager with platform-specific setup, schedule, lifecycle,
paths, updates, recovery, and shutdown language. They do not inherit Windows
tray, sign-in startup, Scheduled Task, Start-menu, installer, or automatic
browser-launch behavior.

The Mac image is read-only, supports amd64 and arm64, and runs as the configured
numeric identity. FreeBSD uses a Podman/rc.d adapter. Both preserve the
independent newsletter schedule and allow up to the documented 30-minute host
grace period for an already-running delivery when the Manager listener stops.

Configuration backup deletion

In Recovery > Configuration backups, each regular private backup now has a
separate Delete action. Deletion requires an authenticated session, a valid
CSRF token, and an explicit confirmation naming the backup. It deletes only the
selected backup, does not change the live configuration, refuses symlinks and
invalid identifiers, and does not expose backup contents in diagnostics. The
action is permanent; download or copy any backup that must be retained first.

Validation and limitations

The release gates cover Manager unit, contract, security, and accessibility
tests; Windows, Linux, macOS, and FreeBSD Manager cross-builds for maintained
architectures; shell and PowerShell validation; synthetic updater success,
locking, private-data preservation, retired-file cleanup, staged rollback, and
corrupted-updater recovery; container heartbeat and liveness behavior;
Compose/Unraid contracts; packaged native Linux boot; reproducible ZIP/TAR
archives; and the isolated Windows installer lifecycle. The amd64 and arm64
container image is built and boot-tested without contacting real Plex,
Tautulli, SMTP, or user configuration.

Physical QNAP, Unraid, macOS, and FreeBSD host behavior, NAS-vendor reverse
proxies and storage ACLs, Community Applications moderation, and real mail
providers remain irreducible environment or submission checks. A native QPKG
remains separately scoped because Container Station already provides the
maintained QNAP deployment path and a QPKG would add signing and hardware/store
maintenance obligations.

TautWeekly for Plex v0.14.0

TautWeekly for Plex v0.14.0

v0.14.0 brings the authenticated shared Manager to NAS containers and native
Linux while keeping each host's lifecycle truthful. QNAP Container Station,
Unraid Apps, generic Docker hosts, and systemd Linux installations now use the
GUI for setup, verification, previews, TestEmail, and schedule controls without
inheriting Windows tray, sign-in, Scheduled Task, or installer behavior.

NAS / Docker Manager

The maintained NAS image now serves the same capability-aware Manager core on
amd64 and arm64. First run has no default password: retrieve a random one-time
token with the documented host or container Console command, pair locally, and
create the administrator password. The token is stored only in private
persistent data and is never written to startup logs or a credentialed URL.

Authentication uses salted PBKDF2 password storage, bounded in-memory sessions,
SameSite/HttpOnly cookies, per-session CSRF protection, same-origin mutation
checks, login throttling, and Host-header validation. TLS remains the reverse
proxy's responsibility; exact DNS allowlists and secure-cookie mode are
available without trusting forwarded client headers. Public health output is
limited to liveness.

The image remains read-only and replaceable. Configuration, Manager access,
schedules, output, history, cache, and backups remain under /data. QNAP uses
the supplied Container Station Compose adapter, Unraid uses the maintained
Community Applications template, and other Docker hosts use the generic
Compose package. A native QPKG and app-store submission remain separately
scoped because they require signed hardware/store validation.

Native Linux Manager

The Linux archive now includes self-contained Manager binaries for amd64 and
arm64. install-linux.sh selects the matching architecture, installs it under
/opt/tautweekly, and starts a hardened systemd service whose Manager defaults
to 127.0.0.1:8788. Use the documented SSH tunnel, run
sudo tautweekly manager-bootstrap, and finish setup in the GUI. ImageMagick is
now an explicit prerequisite rather than an implicit verification dependency.

Linux capabilities are distinct from both Windows and containers: no tray,
sign-in startup, browser auto-launch, Windows task controls, or container update
wording is exposed. Paths describe /opt/tautweekly and
/var/lib/tautweekly; scheduling describes the embedded systemd service; access
recovery uses sudo tautweekly manager-reset-access; and the private preview
landing page contains native Linux instructions.

Update, recovery, and shutdown

For Compose/QNAP, back up persistent data, check or pull the stable image, use
the guarded host update, then sign back in and rerun verification, PreviewAll,
and TestEmail. Unraid updates through its Docker/Apps controls. Rollback pins
the prior verified image tag or digest and reuses the same /data volume.

For native Linux, download the new archive with SHA256SUMS.txt, run a private
backup, verify the checksum, and use sudo ./install-linux.sh --upgrade. The
installer records a timestamped /opt program backup, preserves private data
and environment settings, and verifies that a previously active service
returns. Reinstall and authentication recovery preserve private data; uninstall
instructions retain it until deletion is separately and explicitly intended.

Signing out or closing a browser never changes the independent newsletter
schedule. During service/container shutdown, the Manager listener stops first
and the supervisor waits within the documented 30-minute host grace for an
already-running newsletter delivery instead of cancelling it.

Validation and limitations

Release gates cover Manager unit, contract, security, and accessibility tests;
Windows and Linux builds; amd64/arm64 Manager cross-builds; isolated packaged
Linux boot/authentication/token-redaction/shutdown smoke; container health,
ownership, root-refusal, restart, recovery, and update contracts; 33 synthetic
newsletter scenarios; reproducible archives; and the isolated Windows
install/update/icon/uninstall lifecycle. Tests never contact real Tautulli,
Plex, SMTP, or user configuration.

Physical QNAP/Unraid hardware behavior, NAS-vendor reverse proxies and storage
ACLs, Community Applications moderation, real mail providers/clients, and a
native signed QPKG remain irreducible environment or submission checks.

TautWeekly for Plex v0.13.0

TautWeekly for Plex v0.13.0

v0.13.0 gives the interactive Windows Manager a native notification-area
experience, reliable sign-in startup controls, and a customizable newsletter
action button. The independent weekly newsletter schedule remains unchanged.

Keep the Manager available from the notification area

While the interactive Manager is running, the TautWeekly icon remains in the
Windows notification area with the TautWeekly Dashboard tooltip. Left-click
opens the existing Dashboard. The native right-click menu shows a color-coded
Healthy, Needs attention, or Failed status and an explicit Exit
TautWeekly for Plex action; selecting the status also opens or focuses the
Dashboard.

Only one Manager instance runs for an installation and local address. Repeated
Start-menu or launcher use activates the existing Dashboard instead of starting
another server or tray process.

Exiting the Manager closes only the tray icon and local Dashboard server. It
does not disable or remove the separate Windows Scheduled Task, and it does not
cancel a newsletter delivery that is already running.

Choose Windows sign-in behavior

Manager Settings now includes Start Manager when I sign in. It creates a
current-user, non-elevated startup entry and starts the Manager silently in the
notification area. The dependent Open Dashboard after sign-in toggle opens
the default browser once after that background Manager is ready.

Both toggles save immediately. Setup reconciles the owned startup entry after
updates, portable migrations, reinstalls, and application-path changes;
uninstall removes it so no stale sign-in command remains.

Link the newsletter button to Plex, Seer, or another service

The Manager's Identity settings now pair Open Plex button URL or custom
link with a new Button label field. Existing configurations continue to
use https://app.plex.tv/desktop/ and Open Plex automatically. A custom
HTTP/HTTPS URL and label can instead direct recipients to Seer or another web
service.

The label is single-line, bounded, and safely encoded in HTML and plain-text
mail. Manually edited legacy configurations also reject non-HTTP(S) newsletter
links at render time. Poster and deleted-item-cache fingerprinting now uses a
portable built-in implementation rather than depending on an optional
PowerShell hashing command.

Update from v0.12.7 or an older 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 the Manager and review Settings for sign-in behavior.
5. Under Config > Identity, keep the Plex defaults or set the desired
   custom button URL and label, then validate and save.

Configuration, credentials, exclusions, history, previews, diagnostics,
backups, optional password-lock state, and the independent Scheduled Task are
preserved during update or portable migration.

Validation and limitations

Release gates cover Manager and installer unit tests and vetting, eight
maintained Manager cross-build targets, native single-instance and graceful
shutdown contracts, embedded JavaScript and accessibility checks, 33 isolated
newsletter scenarios across Windows and both maintained container renderers,
reproducible archives, packaged-runtime contracts, and a real isolated Windows
install/update/migration/uninstall lifecycle. Live Windows QA also verified the
tray menu, tooltip, Dashboard activation, immediate startup toggles, sign-in
launch, and preservation of existing local Manager data.

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

TautWeekly for Plex v0.12.7

TautWeekly for Plex v0.12.7

v0.12.7 is a focused Windows Setup hotfix for profiles where Windows returns an
empty or invalid per-user Programs shell-folder path. In affected v0.12.5
and v0.12.6 updates, Setup stopped before creating Start-menu shortcuts while
preserving the existing installation, configuration, and history.

Finish updates on affected Windows profiles

Setup now resolves the current user's Start-menu Programs folder through the
native Windows Shell API instead of a PowerShell COM lookup. If Windows still
does not provide a usable path, Setup uses a bounded fallback derived from the
current user's absolute APPDATA or USERPROFILE path.

The fallback is limited to the current user's standard Start-menu hierarchy.
It does not inspect another account, use a public Desktop, or change the
selected application and private-data directories.

Setup also preselects an existing installer-owned application folder more
reliably. If the primary InstallLocation registry value is missing or stale,
it can recover the same validated folder from the registered uninstaller or
application icon. Arbitrary folders are never accepted from registry data: the
candidate must contain TautWeekly installer metadata or a verified portable
release manifest. Legacy BAT-only folders that have never been migrated still
require one explicit selection.

Update from v0.12.6 or the interrupted update

1. Download TautWeekly-Setup.exe and SHA256SUMS.txt from this release.
2. Verify the EXE against SHA256SUMS.txt.
3. Run Setup again and confirm Update for the preselected installation.
4. Open the Manager and confirm the existing configuration, history, and
   schedule state are present.

No manual cleanup or reconfiguration is required after the reported
resolve Windows Start menu failure. The failed attempt stopped safely before
removing private state.

Validation and limitations

Release validation covers the native and fallback shell-folder paths, Manager
and installer unit tests and vetting, an isolated Windows install/update/icon/
uninstall lifecycle, release archive reproducibility, and maintained Manager
cross-builds for Windows, Linux, macOS, and FreeBSD on amd64 and arm64.

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