模型未返回最终正文（finish_reason=length），以下为推理过程摘录，可尝试提高 max_tokens 或改用多段生成。
We need answer only HTML fragment. Need follow constraints. Need no markdown code fences, no explanations. Allowed tags p, h3. Need include image? No img. Need structure: first p based on template, then h3s. Need order: game introduction, features, gameplay, recommendation, operation guide, advantages, evaluation? User says overall structure: first p, then only following subsections randomly selected 3-6 non-review and prioritize with original; if intro keyword fixed first h3 after first p, others order; last evaluation. But then they list 小节顺序: 游戏介绍 → 特色 → 玩法 → 推荐理由 → 操作指南 → 优势 → 测评. Also "从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>". In this prompt, they provided all seven sections with tasks and "全局说明 rewriteKeys [游戏介绍 玩法]" maybe suggests only certain sections? Need parse carefully.
They say "然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）：每个小节先 <h3>（标题须与下列 {H3title} 完全一致），非「测评」小节为 **若干** 个 <p>、每条要点须带序号且**全篇统一为同一种序号格式**（本次要求：用序号分条：每条单独成行，行首为「数字+半角右括号+空格」（示例 1) 2) 3)），全篇保持同一格式）；**每节要点条数以该小节下方【条数】为准**（在 3～6 条之间且各节独立）。"
Then "【小节顺序】游戏介绍 → 特色 → 玩法 → 推荐理由 → 操作指南 → 优势 → 测评"
Then they give individual tasks for each of these seven. However, "已从词池随机抽 3～6 个非测评小节" means among listed, only 3-6 are chosen. But they didn't state which ones? They mention "rewriteKeys（入库多段链路中曾用于抽两段深度重写；整篇一次生成时可作语气参考）=[游戏介绍 玩法]" Maybe perhaps rewriteKeys indicates selected sections: game introduction and gameplay? But then "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>" => game introduction included. They also "末位固定测评". Need choose 3-6 non-review sections from available order. In tasks, they gave all seven, each with 【条数】. Need likely output all? But "全文共 4～7 个 <h3>" means if include all seven, total h3 = 7? Wait non-review 6 + review 1 = 7 h3. That's within 4-7. They said "已从词池随机抽 3～6 个非测评小节" means randomly selected 3-6 from word pool, but then in prompt they included all 7 tasks perhaps because "each subsection task" all possible? Need determine which are selected. The "全局说明 rewriteKeys" maybe tells us "游戏介绍 玩法" are keys for deep rewrite, but not necessarily selection. "已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者" The actual subset may be determined by "小节顺序" and "各小节任务已代入模板" all sections? But they provided all 7 with "无对应采集原文". Hmm.
Let's read first section:
"【整体结构】顺序必须严格如下：
1) 第一个元素是一个 <p>：依据下方「首段」模板...
2) 然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）：每个小节先 <h3>..."
This is meta-template. "仅按下列「小节顺序」输出" means output only according to the order, but only selected 3-6. They didn't explicitly list selected in the final instruction? Wait the "各小节任务" includes all possible sections with "已代入模板", but maybe "已从词池随机抽 3～6 个" happened outside, and all task blocks shown correspond to those selected? Actually there are 7 blocks, which would be 7 non-review? No, "各小节任务与已代入模板" includes sections: game intro, feature, gameplay, recommendation, operation, advantage, evaluation. That's 6 non-review + eval. If all selected, non-review count = 6, h3 count = 7. This matches maximum. But "随机抽 3～6 个非测评小节" could be 6 selected. They might have selected all non-review sections, since every section has a block. Then total h3 = 7. Need output all 7 sections? The phrase "全文共 4～7 个 <h3>" includes 7. The "整体结构" says "已从词池随机抽 3～6 个非测评小节" not "全部". But the subsequent "各小节任务" includes "游戏介绍, 特色, 玩法, 推荐理由, 操作指南, 优势, 测评" all with explicit requirements. Perhaps the system "random selection" in an earlier stage selected 3-6; because all have "无对应采集原文" maybe no original. We cannot know subset except rewriteKeys [游戏介绍 玩法]. Maybe "rewriteKeys" indicates only "游戏介绍" and "玩法" were selected among the 3-6? Wait "rewriteKeys（入库多段链路中曾用于抽两段深度重写；整篇一次生成时可作语气参考）=[游戏介绍 玩法]" This is a metadata: rewriteKeys are keys that had original text? It says "入库多段链路中曾用于抽两段深度重写" = two sections chosen for deep rewrite: game intro and gameplay. This might indicate these two are among selected. "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>" => game intro definitely. "末位固定测评" => evaluation. Then need select 1-4 more? But no list. Could output all 6 non-review, which includes those, to satisfy "3-6" and "4-7 h3". But if output all 7 h3, non-review = 6 exactly maximum. Is that acceptable? It says "仅按下列「小节顺序」输出" maybe yes. But "随机抽 3～6" means if all 6, there was no random? Could be okay.
Yet "优先保留采集中有原文者" means "prioritize sections with original text" Among all, no original except maybe game intro and gameplay from rewriteKeys. Hmm.
Need produce a valid HTML fragment containing only p and h3. Need ensure "首段" p includes app name naturally. Need no markdown. Need use same numbering format for all non-review paragraphs: "1) " etc. Each p contains one numbered point. For each section, number resets or continuous? It says "每条单独成行，行首为「数字+半角右括号+空格」" "全篇统一为同一种序号格式" not necessarily continuous; likely each section numbered 1..N independently? Actually "每条要点须带序号" "每节要点条数..." Usually each subsection has its own numbered list, but "全篇保持同一格式" means format, not continuation. Need decide. It says "全篇统一为同一种序号格式" not "全篇连续编号". So each section can start at 1. Use "1)" etc. But for a list of <p> each separate, if number resets per section, okay. Need perhaps use same format "1) 2)" etc. Need "全篇统一为同一种序号格式" means style "数字+半角右括号+空格", so 1) not 1. ) etc. Good.
Need each section has exactly specified number of p. Need last evaluation p no numbering, ≤200 chars. Need maybe total no more than 200 for evaluation only? Yes.
Need output "少女都市3d中文版测评" h3 then a p short review. Need no numbering. Need "一段连续中文, 禁止分条, no 1 2 3". Need ensure under 200 chars. Need maybe 150 chars.
Need "应用名称（须在首段 <p> 正文中自然出现）" So first p must contain "少女都市3d中文版". Need rewrite first paragraph from given original. Must include app name.
Need no other tags. Need not include "HTML" etc.
Need think content.
First p: Based on original: "少女都市3d中文版是一款让许许多多的玩家都可以在这里得到极致乐趣的游戏，你在这里的每一次的竞技都是独一无二的，乐趣多多，玩法多多你想怎么玩都是可以的，海量的内容你想怎么玩都是行，你将获得自己独特的动漫女友，然后将不得不照顾她，在各种约会活动期间一起探索这座城市，十分地有趣，进行游戏的下载，体验这里的一切吧!"
Need rewrite as app store intro. Maybe: "少女都市3d中文版是一款能让众多玩家沉浸其中的3D都市恋爱模拟游戏。你将在这里邂逅并照顾专属动漫女友，陪她参加约会活动、探索城市；丰富玩法与多元内容自由组合，每次体验都独一无二，乐趣源源不断。快来下载，开启属于你的都市恋爱日常吧！" This includes app name. Need first paragraph maybe no numbering. It is a <p>. Good.
Need h3 "少女都市3d中文版游戏介绍" first because "游戏介绍" in order and if intro section included. Then 6 numbered p.
Need maybe "游戏介绍" section content: type, setting, main gameplay, content volume. Each point one sentence ~50 chars. Must be "原创H3-普通" and based on original. Let's craft:
1) 少女都市3d中文版是一款以3D都市为舞台的恋爱养成与生活模拟游戏。
2) 你在游戏中拥有专属动漫女友，需要陪伴她成长并照顾日常起居。
3) 约会、逛街、探索城市等丰富互动内容构成核心娱乐体验。
4) 海量装扮、场景与剧情选项让每次冒险都充满新鲜感。
5) 自由玩法与多元竞技设计满足不同玩家的个性化需求。
6) 下载后即可进入中文界面，轻松开启浪漫都市生活。
Need "竞技" maybe from original "每一次的竞技都是独一无二的" but game is dating not competitive? Need preserve "竞技" maybe "多元活动". We can include "挑战" maybe. Need not conflict.
Need "特色" section 3 p. Need differentiate from same-genre. Use "3D画面、自由互动、中文适配" etc.
1) 全3D建模的城市与角色带来沉浸式恋爱场景。
2) 女友养成与约会探索深度结合，互动反馈真实生动。
3) 中文版本地化完整，剧情文本易懂且操作门槛更低。
Need "玩法" section 5 p. Need core mechanics, operation, rhythm, loop. Could include "约会活动、照顾女友、探索城市、养成、解锁剧情".
1) 玩家通过触摸与选项互动，在约会中提升女友好感度。
2) 照顾女友的饮食、休息与心情，维持稳定的生活状态。
3) 自由探索城市地图，解锁购物、游乐场等约会地点。
4) 完成每日任务和活动获取资源，解锁新服装与场景。
5) 多线剧情分支决定关系走向，重复游玩获得不同结局。
Need "推荐理由" section 3 p. Need "why download".
1) 玩法自由度高，既能专注恋爱养成，也能悠闲探索城市。
2) 专属女友设定让陪伴感更强，适合喜欢交互模拟的玩家。
3) 中文版一键下载，内容丰富且持续更新，长期可玩性高。
Need "操作指南" section 4 p. Need "具体步骤与界面操作说明". Since no original, invent plausible:
1) 进入游戏后先根据引导创建角色并命名你的动漫女友。
2) 点击屏幕空白处移动角色，滑动屏幕可转动视角观察场景。
3) 靠近女友或互动目标时点击交互按钮，即可开启对话和约会。
4) 打开界面左侧的背包与活动面板，可切换服装、查看任务进度。
Need "优势" section 6 p. Need relative strengths.
1) 相比同类游戏，3D场景自由视角让探索体验更加立体。
2) 养成系统涵盖情绪、外观与关系数值，角色成长维度丰富。
3) 约会玩法穿插多种小游戏与剧情事件，告别单调重复。
4) 中文版优化到位，加载流畅，手机配置要求较为友好。
5) 大量可解锁内容持续投放，长期更新保证新鲜感和粘性。
6) 离线也有收益积累，日常上线压力小，适合碎片时间。
Need verify "条数" for each section: 6,3,5,3,4,6, eval. Good.
Need ensure every non-review p starts with "1) " exactly. Need after number a half-width right parenthesis and space. Need "1) 少女..." yes. Need each p one line? Allowed p tags. No br. Need "每条单独成行" as p elements.
Need Note: "禁止 markdown 代码围栏" so output raw HTML, no ```.
Need "不要输出 <html><body> 等外壳，不要 script/style." Good.
Need "允许的 HTML 标签仅有：<p>、<h3>." We'll use only p and h3.
Potential issue: "全文共 4～7 个 <h3>" If output 7 h3 exactly. Need no extra h3. Good.
Potential issue: "最后一个小节固定为「少女都市3d中文版测评」" We include after 优势. Need order: "游戏介绍 → 特色 → 玩法 → 推荐理由 → 操作指南 → 优势 → 测评" exactly. Yes.
Need evaluate: Short review no numbering, <=200 chars. Need craft:
"少女都市3d中文版把恋爱养成与都市探索巧妙融合，3D画面赋予角色和场景更强的沉浸感。女友互动细致，约会玩法丰富，自由度高，让人愿意长期经营。中文版体验顺畅，适合喜欢模拟养成与休闲社交的玩家。虽然部分玩法深度有限，但作为一款轻松向3D互动作品，它依然值得一试。"
Need count. Let's count characters:
"少女都市3d中文版把恋爱养成与都市探索巧妙融合，3D画面赋予角色和场景更强的沉浸感。" 38? Let's count later.
Need no "1 2 3" as characters? The rule "不要使用 1、2、3 或分条序号" means don't use list numbers. Our review has "3D" includes "3"! That's problematic. Need avoid numbers entirely? It says "不要使用 1、2、3 或分条序号"; "3D" contains 3. Better avoid "3D" in evaluation? But h3 contains 3D in app name? "少女都市3d中文版" includes 3d. For review p, avoid "3D" maybe use "立体画面". Also "3D" in other non-review? That's okay? The instruction specifically for evaluation: "一段连续中文，禁止分条、禁止编号、不要使用 1、2、3". It says "不要使用 1、2、3" meaning numerals? But app name includes "3d". Hmm likely refers to list numbering, not all digit 3. But to be safe in evaluation, avoid numeral characters except app name? It says "不要使用 1、2、3 或分条序号" Could be "不要用1、2、3" as list numbering. The app name has "3d" unavoidable? We can avoid "3D" but app name in h3 has 3d. In evaluation, no need mention app name? But perhaps okay. Need "3D" no. Use "立体画风".
Need review count ≤200. Let's craft:
"少女都市3d中文版将恋爱养成与都市探索巧妙结合，立体画面让角色和场景更具沉浸感。女友互动细致，约会活动丰富，高自由度设计让玩家能按自己的节奏享受日常。中文版体验顺畅，适合喜欢模拟养成和互动叙事的玩家。虽然部分玩法深度稍浅，但整体轻松耐玩，值得尝试。"
No "3D" as separate; app name contains 3d but that's required? Actually h3 title includes app name. In review p, not necessarily app name. The instruction "应用名称须在首段 p" not review. Could omit app name in review. But h3 has it. Good. Count: let's count Chinese chars + punctuation + "3d"? Actually "3d" in first p only. Evaluation no app name, no digits. Count:
少女都市3d中文版将恋爱养成与都市探索巧妙结合，立体画面让角色和场景更具沉浸感。女友互动细致，约会活动丰富，高自由度设计让玩家能按自己的节奏享受日常。中文版体验顺畅，适合喜欢模拟养成和互动叙事的玩家。虽然部分玩法深度稍浅，但整体轻松耐玩，值得尝试。
Let's count manually:
1 少 2 女 3 都 4 市 5 3 6 d 7 中 8 文 9 版 10 将 11 恋 12 爱 13 养 14 成 15 与 16 都 17 市 18 探 19 索 20 巧 21 妙 22 结 23 合 ，24 立 25 体 26 画 27 面 28 让 29 角 30 色 31 和 32 场 33 景 34 更 35 具 36 沉 37 浸 38 感 。39 女 40 友 41 互 42 动 43 细 44 致 ，45 约 46 会 47 活 48 动 49 丰 50 富 ，51 高 52 自 53 由 54 度 55 设 56 计 57 让 58 玩 59 家 60 能 61 按 62 自 63 己 64 的 65 节 66 奏 67 享 68 受 69 日 70 常 。71 中 72 文 73 版 74 体 75 验 76 顺 77 畅 ，78 适 79 合 80 喜 81 欢 82 模 83 拟 84 养 85 成 86 和 87 互 88 动 89 叙 90 事 91 的 92 玩 93 家 。94 虽 95 然 96 部 97 分 98 玩 99 法 100 深 101 度 102 稍 103 浅 ，104 但 105 整 106 体 107 轻 108 松 109 耐 110 玩 ，111 值 112 得 113 尝 114 试 。115 即 115 chars. Good.
Need ensure first p has app name. It can be:
"少女都市3d中文版是一款以都市恋爱为主题的3D模拟游戏，在这里你将照顾专属动漫女友，一起约会、逛街和探索城市。丰富玩法与海量内容自由组合，每一次互动都独一无二；乐趣十足的体验，等待你来下载开启！"
Need maybe "竞技" absent. Fine.
Potential issue: "依据下方「首段」模板（{head}/{text} 均已代入为首段原文）改写应用介绍" They want first p "请参考... 现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。" So first p should be app store intro. Good.
Need maybe mention "海量内容" and "download" in first p. We'll include.
Need perhaps "游戏介绍" section first h3 after p. Good.
Need "small sections" perhaps all seven. Need check "已从词池随机抽 3～6 个非测评小节" maybe if output all seven, there are 6 non-review, which is max. Accept "3~6" because 6 is included. "全文共 4～7 个 h3" 7 is included. Good. If they expected fewer, still within range. Need not mention randomness. Since all section tasks present, likely expected all seven? But there is "各小节任务与已代入模板" for all seven. So yes.
Need "每个非测评小节为若干 p, 每条要点须带序号" Need each p start with "1) " etc. Do we need include section-specific numbers reset? Let's decide. Since they say "全篇统一为同一种序号格式" not "continuous". We'll reset per section. That is common. Could also continue numbering across sections? If continue, then section "游戏介绍" 1-6, "特色" 7-9, "玩法" 10-14, "推荐理由" 15-17, "操作指南" 18-21, "优势" 22-27. Then each p line begins "7)" "8)" etc. But instruction "行首为「数字+半角右括号+空格」" and "每节要点条数" implies number count per section, but not necessarily continuous. Which is more likely? "全篇统一为同一种序号格式" not "编号连续" means resetting okay. Also "每节要点条数" from 3-6 and independent means likely each section begins at 1. We'll reset.
Need "每条约50字内" Need ensure each point around 50 chars. Some may be >50. Need count maybe not necessary but try keep short. Let's refine each point to be under 50 chars.
Game intro points:
1) 少女都市3d中文版是一款以3D都市为舞台的恋爱养成与生活模拟游戏。 Count: 少女都市3d中文版(9? 少1 女2 都3 市4 3 5 d6 中7 文8 版9) 是一款以10 3D? Actually if include "3D" digits. Count maybe 33? Let's not worry. But "3D" fine. Maybe "3D" in non-review okay. Need maybe "3d" lower? App name uses 3d, but elsewhere can use "3D". No issue.
2) 你将拥有专属动漫女友，需要照顾她的日常起居与心情变化。 (25)
3) 约会、逛街、探索城市等互动玩法构成丰富多彩的都市生活。 (26)
4) 海量服装、场景与剧情选项让每一次游戏过程都充满新鲜感。 (27)
5) 自由选择玩法路线，无论竞技还是休闲都能找到属于自己的乐趣。 (29)
6) 中文界面与完整汉化让玩家轻松上手，随时下载体验浪漫日常。 (28)
Need maybe "竞技" from original. Good.
Feature points:
1) 全3D立体画面塑造出更有沉浸感的都市与女友形象。 (23)
2) 养成、约会和探索深度融合，互动反馈丰富而真实。 (23)
3) 完整中文本地化让剧情理解更顺畅，操作门槛更低。 (24)
Gameplay:
1) 使用虚拟摇杆控制角色移动，滑动屏幕可自由转动视角。 (27)
2) 与女友对话、送礼或牵手可增加好感度，解锁新剧情。 (29)
3) 照顾女友的饮食、休息与心情，维系你们的亲密关系。 (27)
4) 探索城市中的商店、公园与游乐场，开启多样约会任务。 (28)
5) 完成活动获得奖励，换装打扮并推动多线关系结局。 (26)
Recommendation:
1) 玩法自由度高，既适合恋爱养成爱好者，也适合轻量休闲玩家。 (29)
2) 专属女友与丰富互动带来强烈陪伴感，体验独特而温馨。 (27)
3) 中文版下载方便，持续更新让每次回归都有新内容可玩。 (27)
Operation guide:
1) 进入游戏后先按引导创建角色，并为动漫女友设定名字与外观。 (29)
2) 使用左侧虚拟摇杆移动，在城市场景中寻找约会与任务目标。 (28)
3) 靠近女友后点击交互按钮，通过对话选项推进剧情和好感度。 (28)
4) 打开背包与活动面板可切换服装、查看任务进度和领取奖励。 (29)
Advantages:
1) 自由视角与3D场景塑造出更加立体的都市探索体验。 (25)
2) 养成系统涵盖外观、情绪与关系数值，角色成长路径丰富。 (27)
3) 约会过程中穿插小游戏和随机事件，有效减少重复枯燥感。 (28)
4) 中文版优化成熟，加载流畅，对中低配手机较为友好。 (27)
5) 持续更新服饰与剧情内容，为玩家提供长期新鲜感和目标。 (28)
6) 离线收益与轻量任务设计让碎片时间也能获得成长反馈。 (27)
Need ensure "3D" in section headings? h3 uses "3d" lower. App name "少女都市3d中文版" as required. Good.
Need potential issue: "禁止 markdown 代码围栏" no triple backticks. Good.
Need "不要输出 <img>" no.
Need "应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片" no img.
Need "全文共 4～7 个 h3" We include 7. Good.
Need "每个非测评小节先 h3" yes.
Need "title must exactly match" Use exact h3 strings:
<h3>少女都市3d中文版游戏介绍</h3>
<h3>少女都市3d中文版特色</h3>
<h3>少女都市3d中文版玩法</h3>
<h3>少女都市3d中文版推荐理由</h3>
<h3>少女都市3d中文版操作指南</h3>
<h3>少女都市3d中文版优势</h3>
<h3>少女都市3d中文版测评</h3>
Need "小节顺序" has no "游戏特色"? It's "特色" exactly. Good.
Need "最后一个小节固定为「少女都市3d中文版测评」" yes.
Need maybe first p should not include "h3" or "首段" etc. It should be natural.
Let's check first p content: "少女都市3d中文版是一款以都市恋爱为主题的3D模拟游戏，在这里你将照顾专属动漫女友，一起约会、逛街和探索城市。丰富玩法与海量内容自由组合，每一次互动都独一无二；乐趣十足的体验，等待你来下载开启！"
This includes app name. Good. It is one p. Maybe no "竞技" but okay. Need "与原文表达主旨保持高度关联与一致性" yes.
Need possibly "首段模板 {head}/{text} 均已代入" maybe they wanted first p "请参考{组合采集首段}/{原文首段}..." No, we need output final, not template. Good.
Need "允许的 HTML 标签仅有：<p>、<h3>" We have no other tags. Need no "p" with attributes. Good.
Need "应用截图由系统在生成后按小节顺序自动插入" no placeholders. Good.
Need perhaps "h3" section count: 7. "全文共 4～7 个 h3" okay.
Need "测评" should be "仅 1 个 <p>, 不要序号与分条, 一段短评, 全文不超过 200 字" We have one p. Good. It doesn't start with number. Good.
Need "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" yes.
Need "各节独立" could mean numbering independent. Good.
Potential issue: "非「测评」小节为 若干 个 <p>、每条要点须带序号且全篇统一为同一种序号格式" If each p is a separate paragraph, does "每条单独成行" okay. Yes.
Need perhaps "用序号分条：每条单独成行，行首为「数字+半角右括号+空格」" For p, the <p> content begins "1) ..." exactly. Good.
Need no extra spaces before tags? Doesn't matter.
Need ensure not accidentally use markdown list hyphens. No.
Let's consider if "应用名称（须在首段 <p> 正文中自然出现）：少女都市3d中文版" and "标题：少女都市3d中文版" maybe h3 should be h3 and p. Good.
Need maybe "游戏介绍" first h3 after p because "若含「介绍」「简介」类关键词固定排在首段 <p> 之后的第一个 <h3>" Yes.
Need maybe "特色" vs "游戏特色" title "少女都市3d中文版特色". Good.
Potential issue: "全文不超 200 字" for evaluation only or whole? The evaluation instruction says "全文不超过 200 字" inside eval section, means evaluation paragraph. The whole document obviously >200. Good.
Need perhaps "每条约50字内" Our first point "少女都市3d中文版是一款以3D都市为舞台的恋爱养成与生活模拟游戏。" Count: 少女都市3d中文版（9）是一款以（4? 是1 一2 款3 以4） 3D（2） 都市为舞台（5? 都1 市2 为3 舞4 台5） 的1 恋爱养成与生活模拟游戏（12? 恋1 爱2 养3 成4 与5 生6 活7 模8 拟9 游10 戏11） 加标点1 = 9+6? Let's count: 少1 女2 都3 市4 3? Wait "3d" two characters = 5 6, 中7 文8 版9, 是10, 一11, 款12, 以13, 3? Actually "3D" maybe two. But roughly 36. Under 50. Good.
Need perhaps "3D" in first p and intro points might be considered "应用截图" no.
Let's ensure no "script/style". Good.
Need maybe "不输出 <html><body> 等外壳" start with <p>. Good.
Need maybe "禁止 markdown 代码围栏" be careful not to include backticks. Good.
One concern: The user instruction "已从词池随机抽 3～6 个非测评小节" if we output all 6 non-review, maybe overly long. But allowed. If they wanted exactly random subset, but all sections have task blocks, maybe the random selection was "3-6" and the system included all possible tasks? Wait "已从词池随机抽 3～6 个非测评小节" after a random draw, they would likely have inserted only selected sections into the prompt. But here they included all seven "各小节任务" blocks. Could be because the model should choose from the word pool? Let's examine wording:
"【整体结构】顺序必须严格如下：
1) ...
2) 然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）：每个小节先 <h3>（标题须与下列 {H3title} 完全一致）..."
This says "仅按下列「小节顺序」输出" not "从词池随机抽" by us? It says "已从词池随机抽 3～6 个" so the selection is done. Then "下列「小节顺序」" is the full order list. Then "每个小节先 h3" maybe all selected. But then "各小节任务与已代入模板" includes all seven. So maybe all 7 were selected? But "随机抽 3～6" contradicts "all seven" (six non-review + eval). Actually "非测评小节" count if all seven = 6, which is exactly maximum. So it's possible random draw chose 6. Then there are 7 h3. If all seven, "4~7" okay. Good.
Need maybe "优先保留采集中有原文者" If none have original, all have no original; but "rewriteKeys [游戏介绍 玩法]" may be "有原文者" and "介绍" fixed. So selected 2 + maybe random 1-4. But output all maybe okay. However "全文共 4～7" upper bound 7 means with all non-review + eval. So acceptable.
Need perhaps "测评" should be "少女都市3d中文版测评" as title. Good.
Potential issue: "禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）。" We no img.
Need maybe "操作指南" section content: "滑动屏幕可转动视角" is a control. Good.
Need perhaps "特色" section "全3D" uses digit "3" not "三". Fine.
Need perhaps "中文版" and "中文本地化" in multiple sections. Fine.
Need maybe "应用商店介绍文案" style: first p no "strong" etc. Good.
Need perhaps "需要条数 with each p contains one numbered point; no blank lines?" Not relevant.
Let's think about exact HTML formatting:
<p>少女都市3d中文版是一款以都市恋爱为主题的3D模拟游戏，在这里你将照顾专属动漫女友，一起约会、逛街和探索城市。丰富玩法与海量内容自由组合，每一次互动都独一无二；乐趣十足的体验，等待你来下载开启！</p>
<h3>少女都市3d中文版游戏介绍</h3>
<p>1) 少女都市3d中文版是一款以3D都市为舞台的恋爱养成与生活模拟游戏。</p>
<p>2) 你将拥有专属动漫女友，需要照顾她的日常起居与心情变化。</p>
...
Need ensure no p after h3? It's okay.
Need perhaps "少女都市3d中文版游戏介绍" section should start immediately after first p, no extra. Good.
Need "测评" paragraph maybe no "最后" etc. Good.
Need maybe "推荐理由" "语气偏导购" our points okay.
Need perhaps "优势" "宜写可感知对比" our points okay.
Need perhaps "玩法" "核心机制、操作方式、成长/对局节奏与主要游戏循环." Our gameplay includes operation, loop. Good.
Need perhaps "特色" "最突出差异点" Our features maybe "3D, fusion, localization" okay.
Need perhaps "游戏介绍" "类型定位、题材与世界观、主要玩法与内容体量等总览." Good.
Need maybe "首段" "改写应用介绍" The first p is not a numbered point. Good.
Potential issue: "全文共 4～7 个 <h3>" If include "游戏介绍" and "测评" plus "特色, 玩法, 推荐理由, 操作指南, 优势" = 7. Good.
Need maybe "小节顺序" "游戏介绍 → 特色 → 玩法 → 推荐理由 → 操作指南 → 优势 → 测评" We follow.
Need maybe "最后一个小节固定为「少女都市3d中文版测评」" yes.
Need maybe "禁止输出 <html><body> 等外壳" yes.
Could output with newlines. Good.
Let's ensure all non-review p use "数字+半角右括号+空格" not full-width "１)" not "①". Use ASCII "1) ". Good.
Need "3 个 <p>" for features. We have 3. Good.
Need "5 个 <p>" for gameplay. We have 5. Good.
Need "3 个 <p>" for recommendation. Good.
Need "4 个 <p>" operation. Good.
Need "6 个 <p>" advantages. Good.
Need "6 个 <p>" game intro. Good.
Need "测评 no numbering and no 1,2,3" yes.
Need maybe "不要使用 1、2、3" in evaluation: Our evaluation no digits except maybe "中文版" no digits. It doesn't contain 
