장애물 바운드 (Obstacle BoundObstacle)

We need to produce JSON with content (Korean review 900-1100 chars, then blank line, then

same content, no headings). Also need recommendedMapType, mapTypeReason, recommendedTitle, titleReason, recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags, metadataReason, detailCategory, detailCategoryReason. Given map data: site title: "Obstacle BoundObstacle".

Original filename: Obstacle_Bound_S_edit.scx. Internal map title: Obstacle BoundObstacle. Internal description: "Can u guess?It's a bound and it's named Obstacle.Figure it out!" Current genre: UMS (유즈맵). Players: 6. Team: -. Play time: -. Difficulty: -. Version: -. Tags: -. Map size: 1024x1024. Tileset: 우주 (space).

So it's likely a puzzle or something like "bound"? The description: "Can u guess?It's a bound and it's named Obstacle.Figure it out!" Possibly a puzzle map where you need to figure something about obstacles? Could be a "컴까기" (computer AI) but likely it's a puzzle/minigame.

We need to infer detailCategory based on title and description: "Obstacle BoundObstacle" maybe a "bound" map like "bound" is a type where you must avoid obstacles? Might be a "피하기" (dodge) or "미로" (maze). Not enough info. But we can estimate it's a puzzle/minigame. Since classification currently UMS, we could keep recommendedMapType = UMS (since it's a u즈맵).

If we think it's more specific like PUZZLE or MINI_GAME, we could change recommendedMapType to PUZZLE or MINI_GAME with reason. However allowed values include PUZZLE and MINI_GAME. The description hints at guessing, figure it out -> puzzle. So recommendedMapType could be PUZZLE. Provide mapTypeReason: "제목과 설명에서 추론할 수 있는 퍼즐 요소 및猜谜 플레이".

Since current classification is UMS but we change to PUZZLE, we need mapTypeReason. Title: site title is "Obstacle BoundObstacle". There's no Korean/English mix, it's English words but maybe garbled? It seems fine: "Obstacle BoundObstacle". Could be considered proper title; it's English only.

According to rules: If original title is English only, we should put natural Korean translation before and keep English in parentheses. So recommendedTitle should be something like "장애물 바운드オブ스택클"? Wait need Korean translation that is natural. The title "Obstacle BoundObstacle": Could translate to "장애물 바운드オブ스택클"?

Actually "BoundObstacle" maybe a compound: "Bound" + "Obstacle". Could translate as "장애물 바운드"? Not sure. But we need a natural Korean title: maybe "장애물 바운드" (Obstacle Bound) but the original repeats? Actually "Obstacle BoundObstacle" maybe meaning "Obstacle Bound Obstacle"? Might be a typo.

Safer to keep as is but add Korean translation: "장애물 바운드オブ스택클 (Obstacle BoundObstacle)". However Korean translation of "Obstacle BoundObstacle" could be "장애물 바운드オブ스택클" but that's weird. Maybe better: Since it's ambiguous, we keep recommendedTitle same as original? But rule: If site title is not in format "한글 제목 (English Title)" we must write recommendedTitle.

The site title is "Obstacle BoundObstacle" (English only). So we must produce recommendedTitle in Korean + English format. We'll create a Korean translation that seems natural: "장애물 바운드" (Obstacle Bound). But we need to keep original English title in parentheses. So recommendedTitle: "장애물 바운드 (Obstacle BoundObstacle)".

However that changes the English part; we should keep original English title inside parentheses. The rule: "원본 제목이 영어만 있으면 자연스러운 한글 표기를 앞에 쓰고 원문 영어 제목을 괄호 안에 보존한다." So we put Korean natural translation, then space, then original English title in parentheses. So Korean translation could be "장애물 바운드". So recommendedTitle: "장애물 바운드 (Obstacle BoundObstacle)".

That seems fine. TitleReason: "원본 제목이 영어만 있어 자연스러운 한국어 번역을 앞에 추가하고 원문 보존". Now recommendedPlayerCount: given players: 6. Team count: -. Could infer team count = 1 (free-for-all). So recommendedTeamCount = 1. Play time: unknown; we can guess maybe 10-20 minutes? Since it's a puzzle maybe short. But we need to only set if we have evidence. Not given.

Safer to leave null or omit? The schema expects fields; we can set null. But the JSON expects values; we can set null. However recommendedPlayTime expects integer; null is allowed? Not explicitly prohibited. Probably we can set null. Difficulty: unknown; set null. Version: unknown; set null or maybe "v1.0"? No evidence. Better null.

Tags: we can recommend tags based on inference: ["퍼즐", "유즈맵", "장애물", "추리"] maybe up to 8. metadataReason: we can note that we inferred player count from provided data, etc. detailCategory: we need a subcategory Korean. Since we think puzzle, detailCategory could be "퍼즐". detailCategoryReason: "제목과 설명에서猜谜 및 장애물 추론 요소 발견".

Now content: Korean review 900-1100 characters (including spaces). Need to write about map structure, genre, progression, player experience, target audience, pre-play checkpoints. Must not mention site stats etc. We need to count characters roughly. Let's craft about 1000 characters. We'll write Korean review, then a blank line, then