fixes and improvements

docs/REQUIREMENTS.md

@@ -132,12 +132,15 @@ Phase 1: Jellyfin media index, SSH-based remote filesystem inspection, server mo
 - Support OIDC login in the frontend using an OIDC client library, with backend JWT validation for protected API requests.
 - Persist frontend OIDC auth state across tab reloads by storing the OIDC user and request state in browser localStorage.
 - Provide Docker Compose deployment files at the repository root for production and local development.
-- Backend Docker deployment should mount a private SSH key file into the container while the app synthesizes its own managed `known_hosts` file in the backend cache volume.
+- SSH private keys should be managed as reusable saved secrets in Settings, independent of any one machine, and SSH machines should select from that saved-key list.
+- The web UI should allow both importing an existing private key and generating a new SSH keypair for that saved-key list.
+- Saved SSH keys should display their derived public key, fingerprint, and machine usage count so administrators can audit them at a glance.
+- The app should support optional SSH private key passphrases alongside the stored key material.
 - The Settings tab should include a destructive local-database reset action protected by multiple acknowledgements and a typed confirmation phrase.
 - Production compose should also pass the root `.env` into the backend container so runtime auth settings like `OIDC_ISSUER_URL` are available there, not just at compose interpolation time.
 - The backend media index should persist in a Docker volume so a container restart or image rebuild does not force a new full index build.
 - Compose deployment should not require `env_file`; required values should be supplied through environment interpolation or inline shell exports.
-- The SSH key configuration should still support separate directory/name inputs for legacy/manual setups, but Compose should prefer a single mounted key file path instead of a whole SSH directory.
+- The SSH key configuration should move from machine-local text areas to a saved SSH key registry; directory/name inputs remain only as legacy compatibility fields.
 - Show Jellyfin media counts for movies, series, and series episodes on the dashboard.
 - Show dashboard session activity from Jellyfin, including both currently playing sessions and logged-in idle sessions.
 - Activity rows should include user, media title (or `(idle)`), playback state (`playing`/`paused`/`idle`), and whether transcoding is active.
@@ -173,14 +176,16 @@ Phase 1: Jellyfin media index, SSH-based remote filesystem inspection, server mo
 - The Monitoring brush selection should persist across data refreshes and tab reloads instead of resetting whenever new samples arrive, and the zoom buttons should stay in sync with the visible brush range.
 - The Monitoring brush UI should be stable and remain visible after drags or zoom changes; it should be rendered independently from the chart redraw cycle, with usable resize handles for left/right edges.
 
-### Remote Jobs
+### Saved Actions / Remote Jobs
 
-- Support running remote jobs over SSH using explicit templates.
-- Phase 1 jobs should be safe/read-only by default.
-- Avoid arbitrary free-form command execution in the UI.
-- Job templates should be centralized in `jobs.py` for future extension.
-- Command template values must be shell-quoted before execution.
-- Future destructive jobs should require explicit confirmation.
+- Provide an Actions tab for predefined server tasks that users can save and run later.
+- The initial task types should support shell commands and Python scripts, while keeping the design flexible for future task types.
+- Avoid arbitrary free-form command execution for ad-hoc execution; tasks should be stored records with an explicit name, type, content, enabled flag, default machine, and notes.
+- Support running tasks against either the local API host or a configured SSH machine using the same machine registry used by Monitoring.
+- Command/script content should be executed through the existing safe process helpers and shell-quoted where applicable.
+- Future destructive actions should require explicit confirmations or dry-run style safeguards.
+- Job templates should remain centralized in `jobs.py` for future extension.
+- Remote job template values must be shell-quoted before execution.
 
 ## Decision Log
 
@@ -219,5 +224,9 @@ Phase 1: Jellyfin media index, SSH-based remote filesystem inspection, server mo
 - 2026-05-06: The app shell now uses an Applications top-level tab with a Jellyfin subtab for media/library work and a placeholder Nextcloud subtab for future expansion.
 - 2026-05-06: The settings model now treats Jellyfin/Jellyseerr as machine-level configuration instead of global env-only values, so app hosts can be edited alongside other machine services.
 - 2026-05-06: The backend now synthesizes a managed `known_hosts` file from configured SSH machines at startup, avoiding a mounted SSH directory while keeping strict host-key verification enabled.
-- 2026-05-06: Docker Compose was simplified to mount a single SSH private key file when needed instead of a whole `~/.ssh` directory.
+- 2026-05-06: SSH credentials were moved toward reusable saved key records in Settings, so machines can point at a shared SSH key instead of storing their own duplicate private key text.
+- 2026-05-06: The Settings page now includes an SSH key registry UI with create/edit/delete flows and a generate-key action so users can make a reusable key directly in the web interface.
+- 2026-05-06: Saved SSH keys now surface a derived public key, fingerprint, and per-key machine usage count in the Settings UI for easier auditing.
+- 2026-05-06: The dev Compose stack now starts without any SSH key material at all unless a user later configures remote SSH machines.
 - 2026-05-06: The Settings page now exposes a protected local-database reset flow that requires several explicit acknowledgements and a typed confirmation phrase before it can delete the cached app databases.
+- 2026-05-06: Added an Actions tab for saved server tasks, with backend persistence, per-task run history, and support for shell/Python task types on either local or SSH machines.