claude-in-chrome: Back navigation reports wrong URL and browser history is unreliable

Bug Description

When using the navigate tool with url: "back" in the claude-in-chrome extension, the tool response reports an incorrect URL that does not match the actual page loaded in the tab.

Steps to Reproduce

1. Navigate to site A (e.g. nasa.gov) and perform some navigation within that site
2. 2. Navigate to site B (e.g. car.gr)
3. 3. Navigate to site C (e.g. mobile.de)
4. 4. Call navigate with url: "back"
5. 5. Tool reports navigating back to a different URL (e.g. nasa.gov) and the tab actually shows site A (nasa.gov) and not site B (car.gr)

Expected Behavior

The tool response should accurately report the URL of the page that was actually loaded after the back navigation, and that page should be site B (car.gr) — the previously visited site before site C.

Actual Behavior

The reported URL in the tool response does not match the expected previous page. The browser history appears to skip entries — site B is missing from the back navigation stack entirely, jumping directly back to site A.

Additional Context

• Discovered during a Claude Code session using the claude-in-chrome extension
• - The tabs_context_mcp tool correctly reports the actual current URL, while the navigate tool's response does not always match
• - - Affects reliability of back/forward navigation when automating multi-step browsing tasks