Local Seerr test harness

This standalone harness runs a selected Seerr checkout against the isolated local runtime.

Layout

• run-local-seerr.ps1: shared launcher; accepts -Repo, optional -Port (5056), -Config, -Install, and -AllowDirty.
• run-queue-test.ps1 / run-fresh-test.ps1: queue checkout on 5056 / Fresh checkout on 5057.
• status-local-seerr.ps1 / stop-local-seerr.ps1: inspect or stop only the recorded harness process.
• backup-config.ps1: timestamped, complete config backup in backups/.
• config/: isolated live test database, settings, cache, and logs; backups/ and .runtime/ are ignored local state.

From PowerShell in this directory:

.\backup-config.ps1
.\run-queue-test.ps1
.\run-fresh-test.ps1
.\status-local-seerr.ps1
.\stop-local-seerr.ps1

Queue is expected at http://localhost:5056; Fresh at http://localhost:5057. Only one harness instance may use this shared config at a time. Stop it before backing up the SQLite database. To install dependencies in the selected checkout, pass -Install to either wrapper or the shared launcher; it runs pnpm install --frozen-lockfile. The launcher requires a clean worktree unless -AllowDirty is explicitly passed.

On Windows, the launcher uses pnpm exec nodemon with the same watches, extensions, and repo-local pnpm exec ts-node command as upstream pnpm dev. This avoids the POSIX single quotes in upstream's dev script, which Windows cmd.exe cannot interpret. On other platforms it still runs pnpm dev.

config/ contains real Jellyfin/Sonarr/Radarr credentials. Keep it, backups, logs, and runtime state private. Never point -Config at the production NAS path (/volume2/docker/containers/jellyseerr/config); the launcher only accepts config directories inside this harness. Do not commit this harness directory into upstream Seerr.