Frontend state and API integration

Preserve the user’s next edit while the network catches up

Ana saves a bookmark title, then immediately keeps typing. The first response must confirm the submitted title without overwriting her newer draft. The same distinction between user intent and arriving data matters for search, loading, errors, focus, and navigation.

Open the supplied bookmark editor to see a real browser talking to an HTTP API and SQLite. Inspect its visible states, then work through the response ordering and version boundaries. The editor begins with seeded records and supports editing. Adding new bookmarks is a separate feature.

The confirmed title and editable draft are deliberately different. The browser preserves the newer typing after the earlier save completes.