꿈을 꾸는 자들 F06 (Dreamers F06)

We need to produce JSON with content: Korean review 900-1100 chars (including spaces). Then a blank line, then

same content, no heading. total content 1800-3000 chars. We must not use markdown code block, just raw JSON. We must ensure we don't exceed 4500 chars total JSON. We need to infer map details from provided data. Title: Dreamers F06, internal title same. It's a UMS map.

Description: "꿈을 꾸는 자들과 추격자들의 추격전이 시작된다Made by Raillin - Fish ServerOp DayDream- / http://ryua.wo.tchttp://cafe.naver.com/daydream6". So likely a chase / pursuit map maybe something like a "tracking" or "hide and seek"? Not enough info. We can say it's a chase map where players are divided into dreamers and pursuers.

Player count 7 suggests maybe 1 pursuer and 6 dreamers? Team count unspecified. Could be free-for-all? Might be a "유즈맵" type like "추격전". So recommendedMapType likely UMS (already). detailCategory maybe "추격전" or "숨바꼭질".

But from allowed subcategories list: we have categories like 컴까기, 디펜스, 랜덤 디펜스, RPG, 키우기, 피하기, 탈출, 서바이벌, 아레나, 미니게임, 퍼즐, 캠페인, 디플로메시, 블러드, 입구막기, 넥서스 부수기, 밀리. "추격전" not listed. Could map to "피하기" (evade) or "입구막기"? Not exactly. Maybe "피하기" (avoid). Since dreamers are chased, they need to avoid pursuers. So detailCategory: 피하기. That seems plausible.

We need to fill recommendedPlayerCount: 7 (provided). recommendedTeamCount: maybe null? But we can infer maybe 2 teams? Not given. Safer to set null? However JSON expects integer? The spec says recommendedTeamCount is a number, but can be null if uncertain? It says "확실하지 않으면 null 또는 생략한다". So we can omit or set null. We'll omit.

recommendedPlayTime: unknown, we can omit or null. Better omit. recommendedDifficulty: unknown, we can omit or null. We'll omit. recommendedVersionName: unknown, omit. recommendedTags: we can include ["꿈", "추격", "피하기", "유즈맵", "사막"] but must be Korean tags, up to 8. We'll include maybe 5. metadataReason: we can state based on provided player count and title.

detailCategoryReason: based on description of chase and evasion. titleReason: title appears normal Korean+English? It's just "Dreamers F06". No Korean. So we need to add Korean translation? The rule: if 원본 제목이 영어만 있으면 자연스러운 한글 표기를 앞에 쓰고 원문 영어 제목을 괄호 안에 보존한다. So recommendedTitle should be something like "드림러스 F06 (Dreamers F06)".

However they said if 사이트 표시 제목이 이미 "한글 제목 (English Title)" 형식이 아니면 recommendedTitle을 반드시 작성한다. Site title is "Dreamers F06" (English only). So we need to produce recommendedTitle: "드림러스 F06 (Dreamers F06)". But need natural Korean transliteration: "드림러스". Could also be "꿈꾸는 자들 F06"? But better transliteration. We'll use "드림러스 F06 (Dreamers F06)".

titleReason: "원본 영어 제목에 자연스러운 한글 표기 추가". Now need to ensure content length Korean 900-1100 chars including spaces. Let's craft roughly 1000 chars. We'll write Korean review paragraphs covering map structure, genre, progression, play experience, recommendation, points to check before playing. Then blank line, then