Bohan-J a683a58134 fix(web): answer canGoBack from the browser alone, never from push counts ...

Review found the counter still lied, one level deeper: it counted
`router.push` calls, and a call is not a committed history entry. Next
drops a push to `replaceState` when the canonical URL is unchanged
(app-router.js, the `pendingPush && href !== canonicalUrl` branch), so
clicking a self-link — the breadcrumb on an issue detail page, a pin to
the issue you are on — incremented depth with no entry behind it, and a
delete from there could still step off the app.

Fixing the count needs per-entry markers, which means depending on both
React effect ordering (our provider's effect runs before app-router's
history commit) and Next's own preserveCustomHistoryState behaviour.
Two rounds of review have now found holes in hand-rolled history
tracking; a third layer of it is not the way to buy this guarantee.

So stop deriving. `canGoBack` is the Navigation API's answer or `false`.
Browsers without it take the fallback path, which is exactly what they
did before any of this existed — nobody regresses, and the "wrong true
walks the user out of the app" failure is now unreachable by
construction.

Drops the tracker, the popstate wiring and the push wrapper: the
`multica:navigate` bridge returns to its original shape.

Co-authored-by: multica-agent <github@multica.ai>

2026-07-27 18:33:05 +08:00

..

desktop

fix(web): track history position, not push count, for canGoBack

2026-07-27 18:07:36 +08:00

docs

docs(chat): correct the chat sandbox description (MUL-5287) (#5956)

2026-07-27 01:24:00 +08:00

mobile

fix(server): surface real reason for failed quick-create (MUL-5268) (#5898)

2026-07-27 15:35:09 +08:00

web

fix(web): answer canGoBack from the browser alone, never from push counts

2026-07-27 18:33:05 +08:00