* fix(router): support experimental gesture push
Vinext did not expose useRouter().experimental_gesturePush when Next.js apps enabled experimental.gestureTransition. Upstream gesture-transition fixtures call the method inside a held async transition, so the target route never became visible before the canonical router.push completed.
The fix resolves the config flag into the same __NEXT_GESTURE_TRANSITION define used by Next.js, exposes the optional router method only under that flag, and lets gesture navigation use the existing RSC navigation pipeline with an immediate approved visible commit. The ported e2e fixture preserves the upstream held-transition flow and target/static/dynamic assertions.
* test(router): update navigate mock assertions to expect default transition commit mode
* fix(router): address ask-bonk review comments on gesture push
- track scheduled app router navigation in experimental_gesturePush for
parity with push/replace, so a refresh() issued in the same task skips
its redundant re-fetch
- document the synchronous visible-commit mode's null pendingRouterState
invariant in the browser navigation controller
- add a unit test asserting experimental_gesturePush is only attached
when the __NEXT_GESTURE_TRANSITION define is set
* style(tests): fix formatting in shims.test.ts
* docs(router): clarify gesture push normalization and flushSync commit paths
* test(router): fix unbound-method lint in shims test and document gesture spec coverage
* docs(router): clarify gesture define boolean form and spec held-state rationale
* docs(test): note gestureTransition is fixture-wide for the gesture spec only
* fix(router): no-op experimental_gesturePush before the navigation runtime is ready
Upstream gesturePush early-returns when getCurrentAppRouterState() is null,
so a gesture dispatched before hydration is a no-op. Previously vinext fell
through navigateClientSide's non-runtime branch and performed a real history
push. Guard on the runtime's navigate function (the same readiness check
navigateClientSide uses) and document that the un-awaited
void navigateClientSide(...) deliberately matches push/replace's
fire-and-forget rejection shape.
* docs(router): note gesturePush guard/dispatch runtime reads have no TOCTOU window
* docs(test): document gesture fixture's double-navigation divergence from upstream
---------
Co-authored-by: James <james@eli.cx>
Nathan Nguyen
fd1023321b