[NishiPhalke]

Summary

Add a saved-session list to the browser's Sessions panel. Clicking a name opens /browser/[sessionId] and restores its saved state. Delete icons remove sessions, while local is protected in both the UI and API. Deleting the current session opens /browser/local.

SessionPanel.tsx owns the list and navigation. The server's routes and SQLite repository list and remove saved snapshots. BrowserServer.tsx and persistence.ts pause autosave, wait for any outstanding save before deletion, and resume saving if deletion fails.

Workspace verification passed with pnpm verify --concurrency=1. React Doctor reports 100/100 with no issues. The session list uses SWR for shared caching, focus refresh, and cache updates after deletion. Render budgets are unchanged:

SessionPanel interaction	Before	After
Region change	0	0
Session names arrive	1	1
Delete another session	2	2

Session selection finishes queued and in-flight autosaves through persistence.flush() before replacing the keyed stores. Edits arriving during a PUT receive their own save acknowledgement before navigation. A failed save keeps the current session open with its edits and an error; selecting the destination again retries. Next Link's onNavigate intercepts same-tab navigation while preserving modified-click behavior.

Four integration scenarios cover queued and delayed writes, edits during writes, failure, retry, and restoration after returning. Existing render budgets remain unchanged. New pending-switch budget:

Interaction	Before	After
Select another session while a save is pending	Uncovered	1 (disable navigation while saving)

Manual verification

1. Run pnpm dev, open /browser/testsession and /browser/niship, and wait for Saved.
2. Select a session in the Sessions panel and check that its URL and saved state are restored.
3. Delete another session and verify that the current session stays open.
4. Delete the current session and verify that /browser/local opens. The local session has no delete icon.

Reopening the mounted Sessions panel revalidates the saved list, including sessions added or removed in another tab. The session list scrolls within its panel so every saved name and delete button stays reachable.

Interaction	Before	After
Reopen Sessions with external list changes	1 (stale list)	2 (reopening + refreshed names)

The regression test toggles the real workspace panel store, verifies no request on closing and one on reopening, checks additions/removals, and confirms the list stays mounted.

Persistence is initialized only after restoration, snapshot capture, and store subscriptions succeed. A regression test covers a schema-valid snapshot with an unregistered track type followed by a failed DELETE: the load error and retries remain active, no PUT overwrites the saved session, and remote commands remain disconnected. Workspace verification passes with this recovery case.

Deletion recovery keeps at most one load in flight and prevents restoration after initialization. Regression coverage reproduces two delayed GET responses with an intervening edit, confirms the redundant GET is prevented and the edit persists, and checks recovery when the first GET finishes during a failed DELETE.

Browser toolbar integration and shared interaction icon presentation are reviewed separately in #340.

Addresses #334

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
genomebrowser	Ready	Preview	Oct 16, 2026 1:50pm UTC

[github-actions]

React Doctor found no new issues. 🎉

_{Reviewed by React Doctor for commit 3cbaca6.}

[JaiiR320]

One blocker from re-checking the latest commits (4a2aec8): deleting a session still doesn't refresh the sessions list. apps/web/.../SessionPanel.tsx:88 calls mutate with revalidate: false, so the list keeps showing stale data, and an in-flight refresh can be dropped. Could this do a real refetch after the delete, and add a test for it?

[NishiPhalke]

One blocker from re-checking the latest commits (4a2aec8): deleting a session still doesn't refresh the sessions list. apps/web/.../SessionPanel.tsx:88 calls mutate with revalidate: false, so the list keeps showing stale data, and an in-flight refresh can be dropped. Could this do a real refetch after the delete, and add a test for it?

Fixed: successful deletion now removes the session from the cache and triggers a fresh GET. Older in-flight responses remain invalidated.