에어리언vs프레데터[5]

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

, total 1800-3000 chars). No markdown, no extra explanation. Must include fields: recommendedMapType, mapTypeReason, recommendedTitle, titleReason, recommendedPlayerCount, recommendedTeamCount, recommendedPlayTime, recommendedDifficulty, recommendedVersionName, recommendedTags, metadataReason, detailCategory, detailCategoryReason.

We have map data: site title "에어리언vs프레데터[5]". filename includes [] etc. internal title same. internal description: "에어리언vs프레데터 new[5][최신판][진짜잼씀][더욱강화된 유닛들][전보단 강한 인간들][에이리언,프레데터 방어탑!!][그외에 달라진점이 진짜 많습니다 .]"

Current classification: MELEE (밀리). Players: 8. Team count: -. So recommendedTeamCount maybe null? We need to output something; maybe null allowed? It expects number? The schema didn't say nullable but we can maybe set null if uncertain. But we can infer team count? Not given; maybe it's Free-for-all (each player vs each other). So team count 1 (solo).

recommendedTeamCount: 1. Play time unknown; we can estimate maybe 20-30 mins? Not given, so we should set null if uncertain. But the instruction: "플레이 인원/팀 수/예상 플레이 시간은 제목, 내부 설명, 이미지에서 근거가 있을 때만 숫자로 작성한다. 확실하지 않으면 null 또는 생략한다." So we can set null. Difficulty unknown: null. Version unknown: null.

Tags unknown: we can infer from description: 에어리언vs프레데터, 방어탑, 강화된 유닛 etc. So tags: ["에일리언", "프레데터", "방어", "강화"] maybe. But need Korean tags. Provide up to 8. MetadataReason: based on map size etc. Now recommendedMapType: The current classification is MELEE (밀리) but description suggests it's a UMS map with alien vs predator defense towers etc.

It likely is a UMS (User Map Scenario) not standard melee. So recommendedMapType should be UMS. mapTypeReason: "내부 설명에 방어탑, 강화된 유닛 등 특수 트리거 및 사용자 정의 요소가 있어 표준 밀리 맵이 아닌 유즈맵으로 판단."

Title: The site title has Korean with brackets and maybe weird characters? It's "에어리언vs프레데터[5]". That seems fine. No garbled. recommendedTitle can be same as site title: "에어리언vs프레데터[5]". But we might want to add

? The rule: recommendedTitle must be "한글 제목 (English Title)" format if site title not already that format. Site title is Korean only, no English. So we need to add