작전 광기 (Operation Insanity)

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

same content, total 1800-3000 chars), recommendedMapType, mapTypeReason, recommendedTitle, titleReason, recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags, metadataReason, detailCategory, detailCategoryReason.

Given data: site title "Operation Insanity", filename "(2-6)Insanity.scx", internal map title same, description: "Destroy all enemy buildings. Map created by -Tremor- (tremor@iprimus.com.au)". Genre: UMS. Players: 2. Team count: -. Estimated play time: -. Difficulty: -. Version: -. Tags: -. Map size 1024x1024, desert tileset. Thus map is likely a melee style?

"Destroy all enemy buildings" suggests a standard melee objective: destroy enemy base. 2 players, likely versus. So it's a melee map (standard). However classification UMS (user map) but genre is UMS. Since it's a melee style map, recommendedMapType could be MELEE. But we need to decide.

The current classification is UMS (user map) but if it's a melee style (standard), we may change recommendedMapType to MELEE with reason: it's a standard melee map with destroy all buildings objective, 2-player. That seems plausible. We need to produce recommendedTitle: currently site title "Operation Insanity". It's English only? Actually it's English.

The rule: If original title is English only, we should prepend a natural Korean translation and keep English in parentheses. So recommendedTitle should be something like "작전 insanity (Operation Insanity)"? But Korean translation of "Operation Insanity" could be "작전 광기" or "작전 insanity"? Usually "Insanity" as "광기". So Korean: "작전 광기".

Provide format: "작전 광기 (Operation Insanity)". Or "작전 insanity"? Better to translate Insanity to 광기. So recommendedTitle: "작전 광기 (Operation Insanity)". TitleReason: need to state we added Korean translation because original title English only. Now recommendedPlayerCount: given 2. Team count: not given; likely 1 each (free-for-all).

So recommendedTeamCount: 1 (or null). Since we have clear player count 2, we can set team count 1 (each player solo). recommendedPlayTime: not given; we can estimate maybe 20-30 minutes. Since we cannot guess, we should leave null if not sure. But we can estimate based on typical melee map size 1024x1024 desert, 2 players, maybe 15-25 min.

But rule: only write if grounded. No explicit info, so null. recommendedDifficulty: not given; could be 보통? But we cannot guess. Might leave null. However JSON expects fields; we can set null if unknown. The spec: "플레이 인원/팀 수/예상 플레이 시간은 제목, 내부 설명, 이미지에서 근거가 있을 때만 숫자로 작성한다. 확실하지 않으면 null 또는 생략한다." So we can set null for playTime and difficulty.

recommendedVersionName: not given; null. recommendedTags: we can infer tags like ["메리", "2인", "사막"] but need Korean tags. Since no tags given, we can derive from map: "메리", "2인", "사막", "건물 파괴". But better to stick to known tags: maybe ["메리", "2인", "사막"]. But spec: if metadata empty we can fill if we can infer.

We have some info: map size, desert tileset, 2 players, destroy all buildings objective. So we can set tags accordingly. We must ensure content length: Korean review 900-1100 characters (including spaces). Then blank line, then