TSK-012-05 KTO tourism map layer and InfoSheet

[ClarusIubar]

메타데이터

• Scope-ID: TSK-012-05-KTO-TOURISM-MAP-LAYER-INFOSHEET
• Status: open
• Parent Issue: TSK-012-00 Epic: 2차 UI/UX 서브내비 헤더 통합 및 KTO 지도 통합 #404
• Branch: kto-tourism-map-layer-infosheet
• PR: TBD-TSK-012-05

목표

지도 화면에 OFF 기본값의 KTO 관광정보 토글, 보조 마커, InfoSheet를 추가한다.

고정 결정

• KTO 관광정보 표시 토글 기본값은 OFF다.
• 기존 src/api/tourismClient.ts와 src/tourismTypes.ts contract가 main에 있으면 우선 사용하고, 없으면 중복 client를 만들지 않고 해당 gap을 audit evidence로 기록한다.
• API path, response shape, DB schema, OAuth 성공 경로는 변경하지 않는다.
• KTO/OpenAPI, Supabase, admin import/sync를 브라우저에서 직접 호출하지 않는다.
• 사용자-facing copy는 이 child 목표 달성에 필요한 범위에서만 변경한다.

체크리스트

• 현재 코드 기준 변경 전 동작 또는 구조를 테스트/근거로 고정
• child scope 외 파일/행동 변경 없음
• public interface 변경 시 타입과 테스트 갱신
• Architecture Boundary Gate 근거 기록
• PR URL 기록
• merge SHA 기록
• CI URL 기록

검증 체크리스트

• npm.cmd run check:numeric-literals
• npm.cmd run lint
• npm.cmd run typecheck
• npm.cmd run test:unit
• 변경 범위에 따라 npm.cmd run test:integration
• 변경 범위에 따라 npm.cmd run test:regression
• UI 변경 범위에 따라 npm.cmd run test:e2e
• npm.cmd run build
• git diff --check
• UTF-8 integrity check

Core Classification

• Core: TSK-012-00
• Parent Issue: TSK-012-00 Epic: 2차 UI/UX 서브내비 헤더 통합 및 KTO 지도 통합 #404
• Rationale: 2차 UI/UX 구현 명세에서 KTO 관광정보를 지도 레이어로 통합하는 executable child issue다.
• Misroute blocked: EventTab festival-only 정리는 TSK-012-04 Event tab festival-only cleanup #408, CSS offset cleanup은 #410으로 분리한다.

Verification Contract

Required commands

• npm.cmd run check:numeric-literals
• npm.cmd run lint
• npm.cmd run typecheck
• npm.cmd run test:unit
• npm.cmd run test:integration
• npm.cmd run test:regression
• npm.cmd run test:e2e
• npm.cmd run build
• git diff --check
• UTF-8 integrity check

Source-of-truth readback

• GitHub child issue TSK-012-05 KTO tourism map layer and InfoSheet #409 body and checklist
• GitHub parent issue TSK-012-00 Epic: 2차 UI/UX 서브내비 헤더 통합 및 KTO 지도 통합 #404 checklist linkage
• GitHub Wiki 2차 구현 명세 page
• PR checks and merge SHA after implementation

Required evidence

• PR URL
• main merge SHA
• CI URL
• local validation command output summary
• completion report path

Fail-closed failure modes

• Browser direct KTO/OpenAPI, Supabase, or admin import/sync call required
• API path, response shape, DB schema, or OAuth success path change required
• KTO tourism layer cannot stay default OFF

Architecture Boundary Gate

• Responsibility map: tourism API client owns Worker consumer request, map domain owns toggle/selection state, Naver map owner folder owns SDK marker mutation, InfoSheet owns read-only tourism presentation.
• Dependency direction: App shell -> map stage -> Naver map / InfoSheet. UI calls only /api/tourism/places through the Worker client.
• Test seam: tourism client unit tests and browser e2e tests verify default OFF and opt-in fetch behavior.
• Scope map: TSK-012-05 KTO tourism map layer and InfoSheet #409 may add tourism DTO/client, map state, marker hook, InfoSheet, tests, and completion evidence.
• Architecture risk: visual marker click behavior is SDK-dependent; e2e without a Naver client validates opt-in fetch while marker instance behavior remains unit/type guarded.

[ClarusIubar]

완료 근거

• PR: Add KTO tourism map layer #416
• main merge SHA: b89b7fcbbfa4ff5d2f59a2362b98ad445f220031
• completion report: reports/completion/TSK-012-05-kto-tourism-map-layer-infosheet.md

Local validation

• npm.cmd run check:numeric-literals: 통과
• npm.cmd run lint: 통과
• npm.cmd run typecheck: 통과
• npm.cmd run test:unit: 통과
• npm.cmd run test:integration: 통과
• npm.cmd run test:regression: 통과
• npm.cmd run test:e2e: 통과
• npm.cmd run build: 통과
• git diff --check: 통과
• staged UTF-8/BOM 검사: 통과

Remote validation

• PR checks: https://github.com/STH-1-Class-One-Group/JamIssue/pull/416/checks
• main CI: https://github.com/STH-1-Class-One-Group/JamIssue/actions/runs/27453318324
• main production-smoke: https://github.com/STH-1-Class-One-Group/JamIssue/actions/runs/27453318315
• main CodeQL / Code Quality: https://github.com/STH-1-Class-One-Group/JamIssue/actions/runs/27453318036

Architecture Boundary Gate

• Responsibility map: tourism client/DTO, tourism UI state, Naver tourism marker hook, read-only InfoSheet로 분리.
• Dependency direction: App coordinator -> Web Front tourism consumer contract -> map stage -> naver-map SDK boundary.
• Test seam: tourism client unit, audit baseline, MapTabStage integration fixture, Playwright route interception.
• Scope map: Web Front KTO 지도 표시만 포함. Provider/backend schema/OAuth/review/stamp 흐름 변경 없음.
• Architecture risk: 기본 E2E 환경에서는 Naver SDK marker click 자동화가 제한되므로 SDK mutation은 src/components/naver-map 내부에 격리.