feat: re-render bookings page after feature opt-in without full refresh

[eunjae-lee]

What does this PR do?

After a user opts into a feature via the useFeatureOptInBanner() banner on /bookings, the page now re-renders to apply the feature immediately — without a full browser reload.

Problem: bookingsV3Enabled is computed server-side in the page component and passed as a prop. When a user opts in via the banner, only the banner's local state updates (hiding it), but the server-computed prop remains stale until a manual page refresh.

Solution: Adds a required onOptInSuccess callback to useFeatureOptInBanner(). In the bookings view, this callback calls router.refresh() — the idiomatic Next.js App Router method that re-runs the server component and streams updated props to the client without losing client-side state.

This pattern is already established in the codebase (e.g., PbacOptInModal, RoleSheet).

Updates since last revision

• Changed onOptInSuccess from optional to required per reviewer feedback, ensuring every consumer explicitly handles the post-opt-in behavior.
• Updated all existing tests to pass onOptInSuccess.

Demo

Screenshot.2026-02-11.at.16.12.48.mp4

Mandatory Tasks (DO NOT REMOVE)

• I have self-reviewed the code (A decent size PR without self-review might be rejected).
• I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. N/A — no docs changes needed.
• I confirm automated tests are in place that prove my fix is effective or that my feature works.

How should this be tested?

1. Navigate to /bookings as a user eligible for the bookings-v3 feature opt-in banner.
2. Click the banner and complete the opt-in flow.
3. After opt-in succeeds, the page should re-render and reflect the bookings-v3 feature (e.g., calendar view toggle becomes available) without a full browser reload.
4. Verify client-side state (scroll position, active filters) is preserved after the refresh.

Unit test: TZ=UTC yarn test apps/web/modules/feature-opt-in/hooks/useFeatureOptInBanner.test.ts

Human Review Checklist

• Confirm that making onOptInSuccess required (rather than optional) is the desired contract — every future consumer of useFeatureOptInBanner must provide this callback
• Consider whether other pages consuming useFeatureOptInBanner should also wire up onOptInSuccess with router.refresh()

---

Link to Devin run: https://app.devin.ai/sessions/8ab178f5789541b2ba241659860a09b0
Requested by: @eunjae-lee

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR that start with 'DevinAI' or '@devin'.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[cubic-dev-ai]

No issues found across 3 files