Fix Chrome history-navigation success detection for query/hash URL changes

[Copilot]

The reviewed issue was a false negative in go_back/go_forward: success detection compared normalized URLs that drop query/hash, so valid history moves like ?page=2 -> ?page=1 or #/inbox -> #/sent could be reported as “no earlier/later entry”.

• Behavior fix (Chrome agent)

  • Updated go_back/go_forward post-navigation verification to compare full URLs instead of _normalizeUrl(...).
  • This preserves query-string and fragment differences when determining whether history navigation actually changed page state.

• Focused regression coverage

  • Added a Chrome unit test for query/hash-only back navigation transitions to ensure these cases are treated as successful.

// Before
if (this._normalizeUrl(afterUrl) === this._normalizeUrl(probe.before)) { ... }

// After
if (afterUrl === probe.before) { ... }

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
webbrain	Ready	Preview, Comment	Jun 27, 2026 4:08pm