fix: resume Ollama chat jobs across sessions

README.md

@@ -18,7 +18,7 @@ Native-like Hermes dashboard plugin for local Ollama model management and chat.
 - Streamed Ollama responses with a real Stop action that cancels the active request
 - Minimized-by-default expandable thinking/progress details with live stage, elapsed time, event, and character counters
 - Validation harness mode: choose one primary model and one or more independent validator models; validators review the primary draft and the primary model compiles one final answer
-- Server-owned chat jobs continue after the browser closes and persist final answers for later resume
+- Server-owned chat jobs continue after the browser closes and persist final answers for later resume. A newly opened dashboard discovers queued/running jobs from the shared server store and resumes observing them automatically.
 - SQLite is the default chat store for new users
 - Optional native PostgreSQL storage can be installed and linked explicitly from the plugin
 
@@ -26,7 +26,7 @@ The chat supports two modes. With one selected model, it sends a normal direct r
 
 ## Chat storage and durability
 
-Chat jobs are persisted before model execution. The browser observes job status through `/chat/status/{request_id}` but does not own generation. Closing the browser no longer cancels a queued or running job, and the dashboard recovers queued/running jobs after restart. Each conversation records immutable message versions, job attempts, stage timing, model metrics, and append-only operational events.
+Chat jobs are persisted before model execution. The browser observes job status through `/chat/status/{request_id}` and discovers active jobs through `/chat/jobs`, but does not own generation. Closing the browser no longer cancels a queued or running job, and a fresh browser session automatically reconnects to the latest active job. The server worker supervisor continuously re-queues jobs whose worker disappeared and persists a heartbeat while Ollama is thinking, including during idle streaming periods. Stop requests remain responsive because the Ollama stream is checked on a short read interval. The dashboard service is configured with `Restart=always`, and queued/running jobs are recovered after a service restart. Each conversation records immutable message versions, job attempts, stage timing, model metrics, and append-only operational events.
 
 SQLite remains the default and requires no service installation. The Chat storage panel can detect native PostgreSQL, install it only after explicit confirmation, and link it as the active backend. PostgreSQL storage uses the local service environment and remains disabled until the user explicitly selects **Link PostgreSQL**.