chore(git): main 변경 사항을 dev로 백머지

[minbros]

배경

PR #120이 dev가 아닌 main에 직접 병합되어 두 브랜치의 이력을 다시 맞춥니다.

변경 내용

• main에 병합된 GA4 동의 제어 및 이벤트 측정 개선 사항을 dev에 반영
• 후속 개발이 최신 main 기준에서 이어지도록 브랜치 동기화

검증

• GitHub 비교 기준: main이 dev보다 10커밋 앞서고, dev의 별도 커밋은 없음 (ahead 10 / behind 0)
• PR feat(analytics): GA4 동의 제어와 이벤트 측정 개선 #120 검증 결과 재사용: npm test, npx tsc --noEmit, 변경 파일 ESLint, npm run build, git diff --check 통과

Summary by CodeRabbit

• 새로운 기능

  • 분석 쿠키의 허용·거부 상태를 확인하고 변경할 수 있는 개인정보 설정 페이지를 추가했습니다.
  • 페이지 조회, 검색 결과, 일정, 장소, 공유 및 튜토리얼 활동의 분석 측정을 강화했습니다.
  • 검색어 원문과 민감한 URL 정보가 분석 데이터에 포함되지 않도록 보호합니다.
  • 분석 동의 전송과 철회 시 식별자 및 관련 쿠키 처리를 개선했습니다.

• 문서

  • GA4 운영 기준, 개인정보 보호 정책 및 배포 전 검증 절차를 문서화했습니다.

• 테스트

  • 동의 처리, 페이지 조회 중복 방지, 데이터 정제 및 분석 이벤트 검증을 보강했습니다.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
frontend-server	Ready	Preview, Comment	Jul 21, 2026 2:28pm

[coderabbitai]

📝 Walkthrough

Walkthrough

GA4 측정 런타임, 동의 저장소와 Consent Mode 전송 게이트, 세션 기반 페이지뷰, 이벤트별 파라미터 스키마, 제품 이벤트 계측, 개인정보 설정 화면 및 운영 문서가 추가·정비되었습니다.

Changes

GA4 측정 및 동의

Layer / File(s)	Summary
분석 계약과 페이지뷰 컨텍스트 src/lib/analytics/context.ts, src/lib/analytics/runtime.ts, src/lib/analytics/track.ts	페이지 경로·리퍼러 정규화, 카운트 버킷, GA4 런타임 검증, 이벤트별 파라미터 타입과 튜토리얼 이벤트 생성 로직을 추가했습니다.
동의 저장소와 GA 전송 src/lib/analytics/client.ts, src/lib/analytics/consent-*, src/components/analytics/ConsentGatedAnalytics.tsx	버전 호환 동의 쿠키, 공유 동의 스토어, 허용·거부 액션, GA 초기화·FIFO 게이트·철회 처리를 추가했습니다.
세션 기반 페이지뷰 src/lib/analytics/page-view-session.ts, src/components/analytics/AnalyticsRouteTracker.tsx, src/lib/auth-session.ts	세션과 사용자 조회 상태에 따라 User-ID를 먼저 설정하고, 동일 경로 중복을 억제한 수동 page_view를 전송하도록 변경했습니다.
제품 이벤트 계측 src/app/(main)/*, src/components/*, src/hooks/*, src/lib/google-login-client.ts	검색·장소·일정·초대·채팅·튜토리얼·로그인 흐름에 버킷, 역할, 소스 기반 이벤트 파라미터를 연결했습니다.
개인정보 설정과 운영 문서 src/app/privacy-settings/page.tsx, src/components/analytics/PrivacySettingsLink.tsx, docs/analytics/*, docs/superpowers/*	개인정보 설정 페이지와 홈·사이드바 진입점을 추가하고 GA4 운영 기준 및 구현 설계 문서를 작성했습니다.

Estimated code review effort: 5 (Critical) | ~120 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Browser
  participant ConsentStore
  participant ConsentGatedAnalytics
  participant GoogleAnalyticsScript
  participant AnalyticsRouteTracker
  participant GA4
  Browser->>ConsentStore: grant consent
  ConsentStore->>ConsentGatedAnalytics: update snapshot
  ConsentGatedAnalytics->>GoogleAnalyticsScript: load and initialize
  AnalyticsRouteTracker->>GA4: set user_id
  AnalyticsRouteTracker->>GA4: send one page_view

Loading

Possibly related issues

• feat(analytics): GA 분석 동의 변경·철회 지원 #119 — 동의 스토어, 설정 UI, 철회 액션, 쿠키 정리 및 Consent Mode 변경이 이슈 목표와 직접 연결됩니다.

Possibly related PRs

• uttae/frontend-server#115 — 초대 링크 공유 이벤트와 AddMemberPanel의 분석 페이로드 변경이 직접 연결됩니다.
• uttae/frontend-server#120 — GA4 동의 게이트, 수동 페이지뷰, User-ID 철회, 검색어·리퍼러 정규화 경로가 직접 연결됩니다.

Suggested reviewers: song9252

Poem

토끼가 깡충, 동의를 눌러요
GA 쿠키는 살금살금 지워요
한 번의 페이지뷰, 길은 반듯해
검색어 원문은 당근 뒤에 숨겨요
버킷과 이벤트, 귀를 쫑긋
안전한 측정 완료! 🐇

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목이 main의 변경 사항을 dev로 백머지한다는 핵심 목적을 정확히 요약합니다.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint install timed out. The project may have too many dependencies for the sandbox.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/components/layout/SidebarTutorial.tsx (1)

197-223: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win

분석 이벤트 생성이 튜토리얼 완료 API 호출을 막을 수 있습니다.

buildTutorialExitAnalyticsEvent(reason, stepIndex)가 completeTutorial() 호출보다 먼저 실행됩니다. 이 함수는 skip_step이 범위를 벗어나면 RangeError를 던지도록 설계되어 있어(track.ts buildTutorialExitAnalyticsEvent), 만약 향후 TUTORIAL_STEPS 배열 크기가 변경되거나 stepIndex 계산에 회귀가 생기면 completeTutorial()이 전혀 호출되지 않고 사용자에게는 "완료 상태를 저장하지 못했어요"라는 오해성 메시지만 표시됩니다.

분석 이벤트 빌드/전송을 completeTutorial() 성공 이후로 옮기거나 별도의 try/catch로 감싸, 분석 이벤트 실패가 실제 완료 처리를 막지 않도록 하는 것을 권장합니다.

🛡️ 제안 수정

   try {
-      const analyticsEvent = buildTutorialExitAnalyticsEvent(reason, stepIndex);
       await completeTutorial();
+      let analyticsEvent: TutorialExitAnalyticsEvent | null = null;
+      try {
+        analyticsEvent = buildTutorialExitAnalyticsEvent(reason, stepIndex);
+      } catch {
+        analyticsEvent = null;
+      }

       queryClient.setQueryData<SessionUser | null>(
         sessionUserQueryKey,
         (current) =>
           current ? { ...current, tutorialCompleted: true } : current,
       );
-      if (analyticsEvent.eventName === AnalyticsEvents.tutorialSkip) {
-        trackAnalyticsEvent(analyticsEvent.eventName, analyticsEvent.params);
-      } else {
-        trackAnalyticsEvent(
-          analyticsEvent.eventName,
-          analyticsEvent.params,
-        );
-      }
+      if (analyticsEvent?.eventName === AnalyticsEvents.tutorialSkip) {
+        trackAnalyticsEvent(analyticsEvent.eventName, analyticsEvent.params);
+      } else if (analyticsEvent) {
+        trackAnalyticsEvent(analyticsEvent.eventName, analyticsEvent.params);
+      }

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/components/layout/SidebarTutorial.tsx` around lines 197 - 223, Update
finishTutorial so completeTutorial() executes before
buildTutorialExitAnalyticsEvent, or isolate analytics construction and tracking
in a separate failure-safe path after completion succeeds. Ensure analytics
errors cannot prevent the completion API call or trigger the completion-save
error message, while preserving the existing query-cache update and completion
state behavior.

🧹 Nitpick comments (2)

src/lib/join-room-workflow.ts (1)

50-59: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

WaitingApprovalDependencies 타입이 export되지 않아 테스트에서 재정의됨.

join-room-workflow.ts에 정의된 WaitingApprovalDependencies가 export되지 않아, 테스트 파일이 동일한 구조를 손으로 복제하고 있습니다. 소스 타입이 필드를 추가/변경해도 테스트의 로컬 복제본은 컴파일 타임에 이를 감지하지 못해 타입 안전성이 깨질 수 있습니다.

• src/lib/join-room-workflow.ts#L50-L59: type WaitingApprovalDependencies에 export 키워드를 추가한다.
• src/lib/join-room-completion.test.ts#L13-L22: 로컬 타입 재정의를 제거하고 @/lib/join-room-workflow에서 WaitingApprovalDependencies를 import해 사용한다.

♻️ 제안 diff

--- a/src/lib/join-room-workflow.ts
-type WaitingApprovalDependencies = {
+export type WaitingApprovalDependencies = {
   cacheRoomDetail: (roomId: string, detail: RoomDetail) => void;
   getRoomDetail: (roomId: string) => Promise<RoomDetail>;
   navigateToPlan: (path: string) => void;
   setCurrentRoomId: (roomId: string) => void;
   trackAnalyticsEvent: (
     eventName: typeof AnalyticsEvents.joinPlan,
     params: JoinPlanAnalyticsParams,
   ) => void;
 };

--- a/src/lib/join-room-completion.test.ts
-type WaitingApprovalDependencies = {
-  cacheRoomDetail: (roomId: string, detail: RoomDetail) => void;
-  getRoomDetail: (roomId: string) => Promise<RoomDetail>;
-  navigateToPlan: (path: string) => void;
-  setCurrentRoomId: (roomId: string) => void;
-  trackAnalyticsEvent: (
-    eventName: typeof AnalyticsEvents.joinPlan,
-    params: JoinPlanParams,
-  ) => void;
-};
+import { completeWaitingJoinApproval } from "`@/lib/join-room-workflow`";
+import type { WaitingApprovalDependencies } from "`@/lib/join-room-workflow`";

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/lib/join-room-workflow.ts` around lines 50 - 59, Export the
WaitingApprovalDependencies type from src/lib/join-room-workflow.ts (lines
50-59), then remove the duplicated local type definition in
src/lib/join-room-completion.test.ts (lines 13-22) and import
WaitingApprovalDependencies from `@/lib/join-room-workflow` for the test.

src/app/join/[inviteCode]/page.tsx (1)

59-70: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

입장 성공/대기 승인 완료 흐름을 공통 헬퍼로 묶어주세요.
getRoomDetail 조회 → 캐시 반영 → joinPlan 트래킹 → 이동 순서가 src/lib/join-room-workflow.ts의 completeWaitingJoinApproval과 거의 같습니다. 지금처럼 두 곳에 나뉘어 있으면 재시도/에러 처리 정책이 바뀔 때 드리프트가 생기기 쉬우니, 이 흐름을 공통 헬퍼로 합치는 편이 좋습니다.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/join/`[inviteCode]/page.tsx around lines 59 - 70, 입장 성공 처리와 대기 승인 완료
처리의 중복 흐름을 공통 헬퍼로 통합하세요. src/lib/join-room-workflow.ts의
completeWaitingJoinApproval을 기준으로 getRoomDetail 조회, roomDetailQueryKey 캐시 반영,
joinPlan 트래킹, 이동 순서를 하나의 헬퍼에서 처리하도록 정리하고, page.tsx에서는 해당 헬퍼를 호출해 기존 성공 및 메타 조회
실패 시 입장 진행 정책을 유지하세요.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/app/`(main)/search/page.tsx:
- Around line 174-192: Update the search analytics effect around
trackAnalyticsEvent so result_count_bucket is calculated from the total search
result count rather than items.length, which only reflects the current page.
Expose or reuse the existing total-count value from the search response, include
it in the effect dependencies, and pass it to bucketResultCount while preserving
the existing tracking guards.

---

Outside diff comments:
In `@src/components/layout/SidebarTutorial.tsx`:
- Around line 197-223: Update finishTutorial so completeTutorial() executes
before buildTutorialExitAnalyticsEvent, or isolate analytics construction and
tracking in a separate failure-safe path after completion succeeds. Ensure
analytics errors cannot prevent the completion API call or trigger the
completion-save error message, while preserving the existing query-cache update
and completion state behavior.

---

Nitpick comments:
In `@src/app/join/`[inviteCode]/page.tsx:
- Around line 59-70: 입장 성공 처리와 대기 승인 완료 처리의 중복 흐름을 공통 헬퍼로 통합하세요.
src/lib/join-room-workflow.ts의 completeWaitingJoinApproval을 기준으로 getRoomDetail
조회, roomDetailQueryKey 캐시 반영, joinPlan 트래킹, 이동 순서를 하나의 헬퍼에서 처리하도록 정리하고,
page.tsx에서는 해당 헬퍼를 호출해 기존 성공 및 메타 조회 실패 시 입장 진행 정책을 유지하세요.

In `@src/lib/join-room-workflow.ts`:
- Around line 50-59: Export the WaitingApprovalDependencies type from
src/lib/join-room-workflow.ts (lines 50-59), then remove the duplicated local
type definition in src/lib/join-room-completion.test.ts (lines 13-22) and import
WaitingApprovalDependencies from `@/lib/join-room-workflow` for the test.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 290f9bb1-7f1c-4f28-a4bb-f5dd231e5073

📥 Commits

Reviewing files that changed from the base of the PR and between 4cd0bd2 and 188aed9.

📒 Files selected for processing (68)

• docs/analytics/ga4-operations.md
• docs/superpowers/plans/2026-07-20-ga4-measurement-hardening.md
• docs/superpowers/plans/2026-07-21-ga4-consent-settings.md
• docs/superpowers/plans/2026-07-21-ga4-page-view-user-id-sync.md
• docs/superpowers/plans/2026-07-21-ga4-search-privacy.md
• docs/superpowers/plans/2026-07-21-ga4-transport-referrer-hardening.md
• docs/superpowers/specs/2026-07-21-ga4-consent-settings-design.md
• docs/superpowers/specs/2026-07-21-ga4-page-view-user-id-sync-design.md
• docs/superpowers/specs/2026-07-21-ga4-search-privacy-design.md
• docs/superpowers/specs/2026-07-21-ga4-transport-referrer-hardening-design.md
• src/app/(main)/member-settings/_components/AddMemberPanel.tsx
• src/app/(main)/member-settings/_components/RoomMembersSection.tsx
• src/app/(main)/plan/_components/itinerary/AddFromBookmarkModal.tsx
• src/app/(main)/plan/_components/itinerary/PlanItinerary.tsx
• src/app/(main)/plan/_components/itinerary/PlanPageView.tsx
• src/app/(main)/plan/_components/itinerary/PlanPlaceCard.tsx
• src/app/(main)/search/page.tsx
• src/app/home/_components/HomeHeader.tsx
• src/app/home/new/page.tsx
• src/app/join/[inviteCode]/page.tsx
• src/app/privacy-settings/page.tsx
• src/app/waiting/page.tsx
• src/components/analytics/AnalyticsConsentSettings.test.tsx
• src/components/analytics/AnalyticsConsentSettings.tsx
• src/components/analytics/AnalyticsRouteTracker.tsx
• src/components/analytics/ConsentGatedAnalytics.tsx
• src/components/analytics/GoogleAnalyticsScript.tsx
• src/components/analytics/PrivacySettingsLink.test.tsx
• src/components/analytics/PrivacySettingsLink.tsx
• src/components/chat/messages/AiRecommendedPlacesList.tsx
• src/components/chat/messages/PlaceShareCard.tsx
• src/components/layout/SideBar.tsx
• src/components/layout/SidebarTutorial.tsx
• src/components/map/Map.tsx
• src/components/map/MapBookmarkPins.tsx
• src/components/map/MapDiscoverPlaces.tsx
• src/components/map/PlanItineraryMapRoutes.tsx
• src/components/place/AddToBookmarkModal.tsx
• src/components/place/AddToScheduleModal.tsx
• src/components/place/PlaceDetailPanel.tsx
• src/contexts/SelectedPlaceContext.tsx
• src/hooks/useChatActions.ts
• src/hooks/usePlanItineraryReorder.ts
• src/lib/analytics/client.test.ts
• src/lib/analytics/client.ts
• src/lib/analytics/consent-actions.test.ts
• src/lib/analytics/consent-actions.ts
• src/lib/analytics/consent-cookie.test.ts
• src/lib/analytics/consent-cookie.ts
• src/lib/analytics/consent-store.test.ts
• src/lib/analytics/consent-store.ts
• src/lib/analytics/context.test.ts
• src/lib/analytics/context.ts
• src/lib/analytics/page-view-session.test.ts
• src/lib/analytics/page-view-session.ts
• src/lib/analytics/paths.ts
• src/lib/analytics/runtime.test.ts
• src/lib/analytics/runtime.ts
• src/lib/analytics/track.test.ts
• src/lib/analytics/track.ts
• src/lib/auth-session.test.ts
• src/lib/auth-session.ts
• src/lib/auth.ts
• src/lib/client-storage.ts
• src/lib/google-login-client.ts
• src/lib/join-room-completion.test.ts
• src/lib/join-room-workflow.ts
• src/providers/root-providers.tsx

[coderabbitai]

🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# usePlacesSearch가 페이지 단위 items만 반환하는지, 전체 결과 수를 별도로 노출하는지 확인
fd usePlacesSearch
rg -n "totalCount|total_count|resultCount|hasNextPage|items" src/hooks/usePlacesSearch.ts -A 3 -B 3

Repository: uttae/frontend-server

Length of output: 2070

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- search page relevant lines ---'
rg -n "PLACES_SEARCH_PAGE_SIZE|bucketResultCount|trackAnalyticsEvent|searchGeneration|items.length" src/app/(main)/search/page.tsx -A 3 -B 3

echo
echo '--- bucketResultCount definition ---'
rg -n "function bucketResultCount|const bucketResultCount" src -A 6 -B 2

echo
echo '--- places search page size ---'
rg -n "PLACES_SEARCH_PAGE_SIZE" src -A 2 -B 2

Repository: uttae/frontend-server

Length of output: 247

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- search page relevant lines ---'
rg -n "PLACES_SEARCH_PAGE_SIZE|bucketResultCount|trackAnalyticsEvent|searchGeneration|items.length" 'src/app/(main)/search/page.tsx' -A 4 -B 4

echo
echo '--- bucketResultCount definition ---'
rg -n "function bucketResultCount|const bucketResultCount" src -A 6 -B 2

echo
echo '--- places search page size ---'
rg -n "PLACES_SEARCH_PAGE_SIZE" src -A 2 -B 2

Repository: uttae/frontend-server

Length of output: 5563

---

result_count_bucket에는 전체 검색 결과 수를 사용하세요. items는 현재 페이지 결과만 담고 있어 bucketResultCount(items.length)는 0~10 범위에 묶입니다. 전체 결과 수를 함께 노출해 그 값으로 버킷을 계산해야 합니다.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/app/`(main)/search/page.tsx around lines 174 - 192, Update the search
analytics effect around trackAnalyticsEvent so result_count_bucket is calculated
from the total search result count rather than items.length, which only reflects
the current page. Expose or reuse the existing total-count value from the search
response, include it in the effect dependencies, and pass it to
bucketResultCount while preserving the existing tracking guards.