[theatrus]

The desktop app can run a worker for another PSF Guard server on macOS or Windows. Open Settings › Workers › Worker on this computer, enter the server address and worker token, then click Save worker settings and Start worker. The worker continues running in the menu bar or system tray after the app window closes.

The worker computer runs processing tasks; the server stores the catalog and results. Workers for this server lists connections, creates worker tokens and controls where tasks run. The desktop form configures this computer’s connection to a server.

Changes include:

• Explicit labels for Worker token, Worker name, Task types, Concurrent tasks, Task files, and Temporary task folder. Help text explains blank fields and defaults. Both sides of each shared-folder mapping have visible labels.
• Pause worker lets running tasks finish; a pending request may still return one task. Stop worker returns unfinished tasks to the server’s queue. The tray distinguishes waiting for a connection, waiting for tasks and a stopped worker.
• Task files transfer through the server by default. Shared storage is optional. The server settings correctly describe the live previews already supported for worker stack builds.
• Optional login startup, separate worker logs, and a local control port protected by a random secret. The app does not return saved tokens to the frontend. Unix settings files use mode 0600.
• Single-instance handling brings the existing app window forward. Published Seiza 0.44.2 / seiza-stacking 0.51.2 prevents RC-Astro console windows on Windows; stacking output version remains 0.51.0, retaining valid cached stacks.

The Workers guide, design record, release notes, accessible labels and tests use the same terminology.

Screenshots

Browser fixtures simulate Tauri commands. These screenshots verify the rendered form; they do not demonstrate native tray or login behavior.

Phone: labeled shared-folder mappings

Validation

• cargo fmt --all -- --check.
• Focused Rust tests with all features: tray menu 1 passed; worker settings 2 passed.
• npm run lint, npm run build; focused desktop/server worker Vitest files: 11 passed.
• scripts/e2e-local.mjs e2e/desktop-worker-settings.spec.ts e2e/worker-settings.spec.ts: 4 passed, Chromium and WebKit, including phone-width mapping fields, saved-token behavior, worker startup and token revocation. The desktop/phone screenshot cases were also rerun successfully after correcting the captures.
• On the updated stacked Run the worker as a Windows service #1004 branch, workspace/all-targets/all-features Clippy passed; worker Rust tests: 74 passed, 2 ignored. Its additional service-status browser cases also passed.
• git diff --check; screenshots visually inspected.

Native Windows tray/login behavior and bundled-app single-instance behavior were not exercised in this language pass. The original branch reported manual macOS tray connection, pause/resume, shutdown and duplicate-start checks at 7b9ffba; those checks were not repeated here.

Known limits

• Pause cannot cancel a task request already waiting at the server.
• Windows app updates stop the tray worker without disconnecting it from the server first. It starts again at the next login. Uninstalling the app leaves its login entry.
• The macOS menu bar uses the full-color app icon.