🐛 Track GA4 page_view on client-side route changes

[kubestellar-hive]

Fixes #6775

Problem

src/components/GoogleAnalytics.tsx fires gtag('config', ...) (with send_page_view: true) exactly once, inside an inline <Script strategy="afterInteractive"> in the root layout. The docs site uses the Next.js App Router with next/link for internal navigation (see DocsNavbar), so client-side route transitions never re-run that script. Only the first page a visitor lands on was ever reported to GA4 — every subsequent page in a session was invisible.

Fix

Adds RouteChangeTracker, a small client component rendered inside GoogleAnalytics (wrapped in Suspense, as required for useSearchParams in the App Router). It watches usePathname() + useSearchParams() and fires an explicit gtag('event', 'page_view', { page_path, page_location, page_title }) on every route change, per Google's documented SPA tracking pattern. The first render is skipped so the landing page (already covered by the inline config script) isn't double-counted.

Scope / guardrails

• No new backend, exporter, or off-box data flow — GA4 was already configured and gated to production deploys only (isProductionDeploy() unchanged).
• No secrets: the measurement ID is a public GA4 identifier, unchanged from before.
• Bounded: one new component + one new test file, no changes to existing behavior for the initial page load.

Testing

• Added src/__tests__/RouteChangeTracker.test.tsx (4 tests): no page_view on mount, page_view fires on pathname change, query string is included, no throw when window.gtag is unavailable.
• Existing GoogleAnalytics.deploy-gate.test.tsx, gtagEvent.test.ts, and EditPageLink.gtag.test.tsx all still pass (16/16 total across the four files).
• npx eslint and npx tsc --noEmit are clean on the changed files.

— hive: agent=telemetry backend=copilot model=claude-sonnet-4-6

[kubestellar-hive]

Important

Held for human sign-off on the direction, not on the code.

This PR's only tracked rationale is #6775, which the hive filed itself — issue #6775 was filed by kubestellar-hive[bot] and no human has acknowledged it. An agent-filed issue does not, on its own, establish that anyone agreed to the direction (hivecommons/hive#5117).

The change may well be right; nothing here is a review of it. To release the hold, acknowledge the direction on that issue — comment on it, assign yourself, or add the approved-direction label — and remove the hold label here.

[netlify]

✅ Deploy Preview for kubestellar-docs ready!

Name	Link
🔨 Latest commit	79984b6
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6a9e16eedcb310000858587d
😎 Deploy Preview	https://deploy-preview-6776--kubestellar-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign clubanderson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubestellar-prow]

Hi @kubestellar-hive[bot]. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[clubanderson]

Direction acknowledged by hub admin (approved-direction added on #6775); releasing the #5117 hold. This hive runs at ACMM L6 and may act on its own findings.

[github-actions]

Thank you for your contribution! Your PR has been merged.

Check out what's new:

• KubeStellar Console — Live multi-cluster dashboard
• Marketplace — Community extensions
• Knowledge Base — Troubleshooting and how-tos

Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey