Indexer extension 1.0.10 tightens how favorite metadata moves between the browser extension and the web app.

What changed

• Favorites remain editable from both the extension and the web app.
• Extension push now sends favorite state only when the favorite was changed in the extension.
• Local browser import and reset workflows no longer treat missing favorite metadata as a request to remove a favorite.
• Duplicate cleanup now preserves favorite state when any duplicate copy was marked as a favorite.
• Store packages were rebuilt for Chrome and Firefox with the production Indexer service URL.

Why it matters

Browser bookmarks do not have a native Indexer favorite field. Without a careful merge rule, a reset or import can accidentally turn missing metadata into not favorite.

This release makes favorites behave more like user-owned metadata: the extension can still update them, but sync avoids overwriting server state unless the user actually changed the favorite in that browser.