模型未返回最终正文（finish_reason=length），以下为推理过程摘录，可尝试提高 max_tokens 或改用多段生成。
We need produce HTML body fragment exactly. Need follow structure. Need no markdown fences, no explanation. Allowed tags p, h3. Need first element p containing app name naturally. Then sections fixed? User gave whole structure with sections: game intro, advantage, operation, charm, usage, review. However also "然后仅按下列「小节顺序」输出（已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>）" But then "小节顺序" includes six non-review sections plus review. Need output all? They said random 3-6 non测评 small sections, but in provided list includes all five non-review? Actually "小节顺序" later in prompt: "游戏介绍 → 优势 → 操作指南 → 魅力 → 使用说明 → 测评" That's 5 non-review + review = 6 h3. But earlier says 3-6 non测评 and final fixed review, total 4-7. Since listed "按下列顺序" likely need output all six h3? Let's parse carefully.
User: "【整体结构】顺序必须严格如下：
1) 第一个元素是一个 <p>：依据下方「首段」模板改写应用介绍。
2) 然后**仅按下列「小节顺序」输出**（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）：每个小节先 <h3>..."
Then provides "【小节顺序】游戏介绍 → 优势 → 操作指南 → 魅力 → 使用说明 → 测评". It says 3-6 non测评, and we have 5 non测评. Should output all non-review sections? "已从词池随机抽 3～6 个非测评小节" could imply actual set may be 3-6, but in this instance the given order includes 5 non-review? Actually maybe "已从词池随机抽 3～6 个非测评小节" is a global instruction for generated prompt; but then list maybe selected order? Let's read: "然后**仅按下列「小节顺序」输出**（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）" Then immediately after: "【小节顺序】游戏介绍 → 优势 → 操作指南 → 魅力 → 使用说明 → 测评" This likely is the actual order. Need output all? Maybe "随机抽" among pool, not necessarily all; but since list has 5 non-review, output 5 non-review plus review = 6 h3, total h3 6. That's within 4-7. Need include all listed sections? The prompt "仅按下列「小节顺序」输出" and "下列" references the order list. So likely output all sections in that order. Need adhere to each section's required number of p. For each non-review section, h3 title exactly as given: "梦回白玉京游戏介绍", "梦回白玉京优势", "梦回白玉京操作指南", "梦回白玉京魅力", "梦回白玉京使用说明", "梦回白玉京测评" (though title "梦回白玉京测评" appears). Need first p is an intro paragraph. Need mention app name in first p naturally. Need not include head/text. Need rewrite app introduction based on first paragraph, include app name. It says "标题：梦回白玉京；原文首段：梦回白玉京手游以唯美水墨画风..." Need write a <p> naturally containing "梦回白玉京". Let's craft.
Need ensure "全篇统一为同一种序号格式": "数字+全角句号．" e.g. "1．". Need each point as separate line? "每条单独成行" within p? We cannot use br tags because allowed only p,h3. If "每条单独成行" within a section, need each point in its own <p>, "行首" of that paragraph. That's what they specify: "随后 6 个 <p>，每 <p> 一条要点". So each point is in separate <p>. Do not use <br> because not allowed. Good.
Need "每条约50字内" one sentence. Need "本节固定 6 条" for game intro and charm; 3 for advantage, operation; 4 for use. Need ensure all content original but related. Need avoid prohibited tags and markdown. Need no front/back.
Need think about "首段" rewrite. Should be a p, not numbered. It should contain app name and be an original rewrite. Maybe:
"梦回白玉京是一款以唯美水墨画风构筑的仙侠放置卡牌手游，将玩家带入飘渺云海与古雅楼阁交织的奇幻修仙世界。游戏以东方美学为底色，从灵兽异兽到仙家法宝皆精心雕琢，带来沉浸式的放置养成体验。"
Need "app store intro style".
Need sections content. Need use each h3 and p's. Need each p contain "1．...", etc. Need "one sentence core info each". Need "全篇保持同一格式" for numbering. Since each p has paragraph start with number. For "测评" no number.
Need ensure "梦回白玉京测评" final p <=200 chars. Need one paragraph, no numbers. Need include objective review. Need count. Let's draft with careful length. Need no "1./2." etc in final.
Need ensure "梦回白玉京" appears in first p naturally. It will.
Need maybe "非「测评」小节为 若干 个 <p>、每条要点须带序号且全篇统一为同一种序号格式" means within a section, each p is a point with number. Good.
Need not output "应用截图由系统...". We ignore.
Need maybe "随机抽 3～6 个非测评小节" Could be interpreted we should not output all non-review, but the "【小节顺序】" says output exactly "游戏介绍 → 优势 → 操作指南 → 魅力 → 使用说明 → 测评" maybe because the random draw selected all five? Let's examine the phrase "已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>". This is a generated condition. They might have included "游戏介绍" and "使用说明" as 'rewriteKeys'? They note rewriteKeys=[游戏介绍 使用说明]. "优先保留采集中有原文者" perhaps meant from a multi-link pipeline. But in this prompt, "【小节顺序】" includes all six sections. It says "非测评小节" [游戏介绍, 优势, 操作指南, 魅力, 使用说明] = 5. "3～6" allows 5. Thus output all five. Good.
Need verify "每个小节先 <h3>（标题须与下列 {H3title} 完全一致）". For game intro h3 "梦回白玉京游戏介绍" etc. For "测评" h3 "梦回白玉京测评". We don't need h3 for "游戏介绍" as "梦回白玉京游戏介绍" exactly? The list says "游戏介绍 →..." and "小节关键词「游戏介绍」：标题必须是 <h3>梦回白玉京游戏介绍</h3>" yes.
Need "使用说明" is a non-review section; h3 "梦回白玉京使用说明". Good.
Need "末位固定测评" — final h3 with p. Good.
Need "全文共 4～7 个 <h3>" — we have 6 h3. Good.
Need "只输出一段可直接写入数据库的 HTML 正文片段" — no "HTML" wrapper. Good.
Need "禁止 markdown 代码围栏" — no fences.
Need "允许的 HTML 标签仅有：<p>、<h3>。禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）。" Good.
Need "不要输出 <html><body> 等外壳，不要 script/style." Good.
Now content. Let's craft each section.
First p:
"梦回白玉京是一款以唯美水墨画风描绘东方仙侠世界的放置卡牌手游。其架空世界观融合缥缈云海、古朴建筑、灵兽异兽与仙家法宝，营造出极具诗意的沉浸氛围，让玩家在赏画般的心境中开启修仙之旅。"
Need maybe "应用名称须在首段 <p> 正文中自然出现" yes. Is this "改写" enough? Good. Maybe mention "独特放置卡牌体验" to align: "带来轻松独特的放置卡牌体验". Let's include.
First p maybe:
"梦回白玉京是一款以唯美水墨画风勾勒东方修仙世界的放置卡牌手游。游戏用缥缈云海、古朴建筑、灵兽异兽与仙家法宝构建出充满东方美学的架空仙侠世界，让玩家在如诗如画的意境中体验与众不同的修仙之旅。"
This includes "梦回白玉京". It is original.
Now Game intro section with 6 points. Need each 50 words? "每条约50字内" means each point no more than 50 Chinese chars maybe including number? We need keep around 25-45 chars. Need "游戏介绍" typology, world, main gameplay, content volume. Let's craft.
1．游戏定位为水墨仙侠题材的放置卡牌手游，玩家无需频繁操作即可推进修仙进度。
2．世界观取材东方修仙文化，围绕缥缈云海、古老门派与仙妖共存的奇妙天地展开。
3．核心玩法以卡牌收集与阵容搭配为主，结合离线放置与自动战斗，让成长更加轻松。
4．功法、法宝与灵兽等多线养成系统相互贯通，提供丰富而清晰的长期养成目标。
5．剧情与探索融合在章节关卡中，玩家可一路游历山河，逐步揭开白玉京的仙缘真相。
6．角色立绘与场景均采用水墨笔触，将古典诗词意境融入每一处界面的视觉呈现。
Check length: Each line p. Good.
Need "游戏定位为" maybe "梦回白玉京游戏定位..."? No need? But in h3 title. Let's ensure "game intro" covers type. Good.
Advantage section 3 points. Need "相对同类在玩法、画面、系统、优化等方面的长处". Let's craft:
1．水墨画风在同类放置卡牌中辨识度突出，画面既有传统东方韵味又有细腻光影层次。
2．放置玩法兼顾休闲与策略，日常收益稳定，适合碎片时间玩家长期沉浸养成。
3．美术、数值与玩法结合紧密，零氪或轻度付费也能获得顺滑的成长体验。
Need no mention "零氪" maybe fine. "优化" maybe "加载流畅". Could replace third:
3．系统架构轻量，挂机与战斗流程流畅，长时间运行也不易产生明显卡顿。
Need "相对同类" maybe in first. Good.
Operation guide 3 points. Need concrete steps/interface. Let's craft:
1．进入游戏后先跟随新手引导，在“洞府”界面领取初始资源并完成首次召唤。
2．点击主界面的“出征”按钮进入章节关卡，上阵卡牌后选择自动战斗即可挂机推进。
3．在“养成”面板中可消耗丹药与灵石提升角色等级，并根据敌方阵容调整站位与技能顺序。
Need check "禁止 <br>" not issue. Need maybe "界面" with Chinese quotes okay. Need "操作指南" maybe "具体步骤". Good.
Charm section 6 points. Need "情感吸引力与愿意长期玩的理由, 氛围, 代入感, 社交". Need no repeated from earlier? Okay. Craft:
1．行舟于云海、漫步于古阁，每一步都让人仿佛置身会呼吸的水墨画卷。
2．仙侠角色性格鲜明，随着羁绊剧情展开，玩家会日渐牵挂他们的命运。
3．轻量放置机制让回归玩家毫不吃力，离线收益带来“每天回来看看”的温情牵挂。
4．宗门、论道、好友助战等社交玩法，让修行之路不再孤单。
5．随机奇遇与隐藏事件散落在地图中，让每次探索都保留新鲜期待。
6．悠扬国风配乐配合水墨画面，营造出远离尘嚣、清静逍遥的修仙心境。
Need "魅力" section perhaps "情感吸引力". Good. "宗门论道" maybe okay.
Use instructions 4 points. Need "安装与权限、首次上手、常见设置与注意事项，偏实用". Need "使用说明" maybe app store instructions. Craft:
1．游戏包体经过轻量化处理，建议在Wi-Fi环境下完成下载，并为设备预留充足存储空间。
2．首次启动会下载基础资源并申请必要权限；玩家按提示授权即可正常进入修仙世界。
3．在“设置”中可调整画质、音效与推送通知，低配机型建议开启省电模式以保证流畅。
4．同一账号支持多端数据同步，切换设备前请确认已绑定手机号或第三方账号，避免进度丢失。
Need "必要权限" maybe "存储" etc. Good.
Need final review "测评": one p no number <=200. Need combine features, objective, realistic, maybe "拟人化". Need not too long. Need count characters including punctuation. Let's craft:
"梦回白玉京以水墨画风与放置玩法形成鲜明反差，乍看是安静赏景，细品却发现成长脉络清晰可循。它不追求激烈操作，而是用云海楼阁、灵兽法宝和舒缓国风曲调，把修仙的逍遥感缓缓送到玩家手中。对偏爱东方美学和碎片化体验的人来说，它像一卷可随时展开的山水长卷，既有收集养成的满足，也有闲庭信步的从容。虽然玩法深度不算极致，但氛围营造极具辨识度，值得在忙碌间隙静下心来慢慢游历。"
Need count. Let's count Chinese characters and punctuation. Use rough count:
梦回白玉京(5) 以水墨画风(6?) Let's carefully count.
"梦回白玉京" 5
"以水墨画风与放置玩法形成鲜明反差，" Let's count: 以(1) 水(2) 墨(3) 画(4) 风(5) 与(6) 放(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)卷(116)，(117)既(118)有(119)收(120)集(121)养(122)成(123)的(124)满(125)足(126)，(127)也(128)有(129)闲(130)庭(131)信(132)步(133)的(134)从(135)容(136)。(137)
"虽然玩法深度不算极致，但氛围营造极具辨识度，值得在忙碌间隙静下心来慢慢游历。" 虽(138)然(139)玩(140)法(141)深(142)度(143)不(144)算(145)极(146)致(147)，(148)但(149)氛(150)围(151)营(152)造(153)极(154)具(155)辨(156)识(157)度(158)，(159)值(160)得(161)在(162)忙(163)碌(164)间(165)隙(166)静(167)下(168)心(169)来(170)慢(171)慢(172)游(173)历(174)。(175)
Total ~175. Good.
Need maybe "应用名称 "梦回白玉京" in final? Not required, but good. It appears at start.
Need ensure no numbered in final. Good.
Need ensure "全文不超过 200 字（含标点）" for final only, yes.
Need "每节点条数 exactly": Game intro 6, advantage 3, operation 3, charm 6, use 4. Good.
Need "全篇统一为同一种序号格式：数字+全角句号．" Need use "1．" etc. There is "全角句号．" U+FF0E? Actually "．" is fullwidth full stop? The example "1．" is digit + "．" (U+FF0E FULLWIDTH FULL STOP). Need use that character. Good.
Need "每条单独成行" If each point is separate p, there is block. Good.
Need "每节要点条数以该小节下方【条数】为准" yes.
Need "允许的 HTML 标签仅有：<p>、<h3>" — no other tags. We will output raw HTML starting with <p> and then h3. Need no markdown code fences. Need maybe no trailing newline? Fine.
Need ensure "插入图片由系统..." ignore.
Potential issue: The "首段" says "请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。标题：梦回白玉京；原文首段..." So first p should be a store intro. Good.
Potential issue: "应用名称（须在首段 <p> 正文中自然出现）" We have "梦回白玉京是一款..." Good.
Potential issue: "非「测评」小节为 若干 个 <p>、每条要点须带序号且全篇统一为同一种序号格式". Some might require each point starts at top visually; separate p means paragraph indent? But HTML no indent. Good.
Potential issue: "允许的 HTML 标签仅有：<p>、<h3>" h3 must not have other attributes? Use plain <h3>. Good.
Need maybe no whitespace between tags? Fine.
Need no "HTML 正文片段" could include no starting "这里". Good.
Let's think if "随机抽 3~6 个 non-review" maybe perhaps we should not output all sections? But if output all five, h3 count 6. Within 4-7. Good. If expected only 3-6 h3 + first p? "全文共 4～7 个 <h3>" exactly. We have 6 h3. Great.
Need maybe "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>" Since "游戏介绍" includes "介绍", so first h3 should be "梦回白玉京游戏介绍", which we do. Good.
Need "其余小节再按其下列顺序" after game intro: advantage, operation, charm, use, review. Good.
Need "末位固定测评" yes.
Need "rewriteKeys" note "游戏介绍 使用说明" maybe should make those two sections deeper? Maybe not necessary.
Need "应用商店介绍文案" style. Good.
Need ensure each p in section has "1．" at beginning. Let's verify no missing.
Let's craft final with exact:
<p>梦回白玉京是一款以唯美水墨画风勾勒东方修仙世界的放置卡牌手游。游戏用缥缈云海、古朴建筑、灵兽异兽与仙家法宝构建出充满东方美学的架空仙侠世界，让玩家在如诗如画的意境中体验与众不同的修仙之旅。</p>
<h3>梦回白玉京游戏介绍</h3>
<p>1．游戏定位为水墨仙侠题材的放置卡牌手游，玩家无需频繁操作即可推进修仙进度。</p>
... etc.
Need no extra paragraphs before first h3? yes.
Need "第1小节点数 6" good.
Need ensure "游戏介绍" section title exactly "梦回白玉京游戏介绍", not "梦回白玉京 游戏介绍" no space. Good.
Potential issue: "全篇统一为同一种序号格式" For "游戏介绍", first point uses "1．", second "2．", etc. Good.
Need perhaps each p "一条要点" no other text. Good.
Need "每条约50字内" "游戏定位为水墨仙侠题材的放置卡牌手游，玩家无需频繁操作即可推进修仙进度。" Count maybe 33? Good.
Need "操作指南" third "根据敌方阵容调整站位与技能顺序" maybe "技能顺序" not possible in automatic? Could be okay. Maybe "根据敌方阵容调整上阵角色与技能顺序" better.
Need use "全角句号．" after number. Need some lines have periods? We can end with "。" full stop. Good.
Let's revise content for quality and consistency.
First p:
"梦回白玉京是一款以唯美水墨画风勾勒东方修仙世界的放置卡牌手游。游戏用缥缈云海、古朴建筑、灵兽异兽与仙家法宝构建出充满东方美学的架空仙侠世界，让玩家在如诗如画的意境中体验与众不同的修仙之旅。"
Maybe "勾勒东方修仙世界" is okay. "与众不同的修仙之旅" matches original.
Game intro:
1．游戏定位为水墨仙侠题材的放置卡牌手游，玩家无需频繁操作即可推进修仙进度。
2．世界观以东方修仙文化为基底，在云海、古阁与仙妖共存的天地间展开冒险。
3．核心玩法围绕卡牌收集与阵容搭配，结合离线放置和自动战斗，带来轻松成长体验。
4．功法、法宝、灵兽等多线养成环环相扣，为玩家提供清晰而长远的修炼目标。
5．章节关卡融入探索与剧情，从初入仙门到寻访白玉京，逐步揭开仙缘真相。
6．水墨笔触贯穿角色立绘与场景，以古典诗词般的留白传递东方美学的独特意境。
Need "内容体量" maybe "章节关卡" enough.
Advantage:
1．水墨画风在同类放置卡牌中辨识度极高，既有传统东方韵味，又有细腻的光影层次。
2．放置玩法兼顾休闲与策略，每日收益稳定，适合碎片时间玩家静心养成。
3．系统设计轻量流畅，挂机收益与战斗表现顺滑，中低配置设备也能稳定运行。
"中低配置设备" okay. "优化" yes.
Operation:
1．进入游戏后先跟随新手引导，在“洞府”界面领取初始资源并完成首次召请。
2．点击主界面的“出征”按钮进入章节关卡，上阵卡牌后选择自动战斗即可挂机推进。
3．在“养成”面板中消耗丹药与灵石提升角色，并根据敌方阵容调整上阵站位与技能顺序。
Need maybe "召请" not "召唤"? "首次召唤" better. Use Chinese quotation marks okay. Are quotes allowed? Yes, no tags. Fine.
Charm:
1．乘舟穿行云海、漫步古阁回廊，每一步都仿佛置身会呼吸的水墨画卷。
2．角色性格鲜活生动，随着羁绊剧情推进，让人渐渐牵挂他们在仙途中的际遇。
3．放置机制让每次回归都能领取不菲收益，带来“仙界仍在等待”的温暖归属感。
4．宗门论道、好友助战和仙盟玩法，让独自修行也能拥有并肩同行的伙伴。
5．地图中暗藏随机奇遇与隐秘事件，为熟悉场景注入源源不断的新鲜感。
6．国风配乐与水墨画面相得益彰，营造出超脱尘嚣、清静逍遥的修仙氛围。
Need "放置机制" maybe "place" okay.
Use:
1．建议在Wi-Fi环境下完成游戏下载，安装前为设备预留至少数GB可用空间。
2．首次启动需下载基础资源并授权存储、通知等必要权限，按提示操作即可进入游戏。
3．可在“系统设置”中切换画质、音效与推送提醒，低配设备建议开启省电模式。
4．支持账号多端同步，切换设备前请确保已绑定手机号或常用第三方账号。
Need "数GB" okay.
Review final:
"梦回白玉京以水墨画风与放置玩法形成鲜明反差，乍看是安静赏景，细品却发现成长脉络清晰可循。它不追求激烈操作，而是用云海楼阁、灵兽法宝和舒缓国风曲调，把修仙的逍遥感缓缓送到玩家手中。对偏爱东方美学和碎片化体验的人来说，它像一卷可随时展开的山水长卷，既有收集养成的满足，也有闲庭信步的从容。虽然玩法深度不算极致，但氛围营造极具辨识度，值得在忙碌间隙静下心来慢慢游历。"
Need ensure no numbering. Good.
Potential issue: "每节点条数 fixed" "使用说明" 4 p yes. "魅力" 6 p yes. "优势" 3 p. "操作指南" 3 p. "游戏介绍" 6 p. Good.
Need "全文共 4~7 h3" We have 6. Good.
Need "第一个元素是一个 p" yes no preceding newline? It's okay.
Need maybe "h3" after first p. Good.
Need no h3 for "首段", no "应用介绍" h3. Good.
Need "禁止输出 img" yes.
Need "不允许 markdown" yes.
Let's consider if "梦回白玉京游戏介绍" and "梦回白玉京测评" are "标题必须与下列 {H3title} 完全一致" We have exact. Need "梦回白玉京优势" exact, "梦回白玉京操作指南" exact, "梦回白玉京魅力" exact, "梦回白玉京使用说明" exact. Good.
Need perhaps "H3title" for "使用说明" may be "梦回白玉京使用说明" not "使用说明（FAQ）"? The prompt explicitly "标题必须是 <h3>梦回白玉京使用说明</h3>". Good.
Need maybe "小节顺序" says "游戏介绍 → 优势 → 操作指南 → 魅力 → 使用说明 → 测评". Good.
Need maybe "随机抽 3–6 个非测评小节" Could require "last section fixed review; total 4–7 h3" We have 6 h3. Good.
Need "原文首段" includes "梦回白玉京手游" but our app name "梦回白玉京" okay. Need "应用名称在首段自然出现" yes.
Need "根据原文内容创作" We used many original elements.
Potential issue with "使用说明" sections include "安装与权限" whereas game is mobile, okay. "包体经过轻量化处理" maybe not necessary but fine.
Need maybe "首次启动会下载基础资源并申请必要权限；玩家按提示授权即可正常进入修仙世界." The point uses semicolon, okay. It's still one sentence. "每条约50字内" maybe around 30. Good.
Need maybe no comma after "1．"? We have "1．" no space. Good.
Need maybe "全角句号．" is U+FF0E after digit. Need ensure not "1." (halfwidth). In text, "1．" includes fullwidth period. Good.
Let's check all numbered points for use of "．" after number:
"1．游戏定位..." yes. Need no space.
Need "全文不超过200字" for final. We counted ~175. Good.
Need "语气客观简练" final is slightly appreciative, okay. "拟人化" "它像一卷..." good.
Need "应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片" no action.
Need "不要 script/style" no.
Need "可直接写入数据库的 HTML 正文片段" Our output is HTML with tags. Good.
Need if final output should be "一段可直接写入数据库的 HTML 正文片段" not "HTML 正文片段" with double quotes. We'll output just raw.
Let's think if "序号格式" "数字+全角句号．" means each numbered point should be in one line, but since each p is separate, okay. The sentence "每条单独成行" is satisfied because each p is block-level; line breaks in HTML source don't matter, but visually each p on separate line. Good.
Need maybe "每个小节先 <h3>" yes.
Need maybe "除「测评」外" "非「测评」小节为 若干 个 <p>、每条要点须带序号" yes.
Need maybe "第 1 小节「游戏介绍」6 points" But the first p is not section, no issue.
Need maybe "梦回白玉京测评" final should be "最后一个小节固定为「梦回白玉京测评」（已在下列顺序末位）" We have.
Need maybe "无独立测评段，请根据首段与其它小节摘要，内化下列「原创H3-测评」模板，只输出 一个 <p>、无序号、≤200 字." Good.
Potential issue: "字数不超过 200 字（含标点）" We need maybe ensure final review is no more than 200. It is 175. Good. Need maybe "输出必须为一段连续中文，禁止分条、禁止编号、不要使用 1、2、3" Our final uses "它" etc. no numbers. Good.
Need maybe "严禁 markdown 代码围栏" We won't.
Let's consider if "应用名称（须在首段 <p> 正文中自然出现）" We used "梦回白玉京是一款..." Good.
Need maybe "梦回白玉京" in h3 all sections? yes.
Need maybe "首段模板" "请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。" Our first p includes "东方仙侠世界", "水墨画风", "放置卡牌", "修仙之旅". Good.
Need maybe "更偏向于一个应用商店的介绍文案" yes.
Potential issue: "应用商店的介绍文案" maybe first paragraph should be "《梦回白玉京》" with book title marks? But allowed tags, not issue. But "应用名称" maybe should be exact "梦回白玉京" no brackets. Fine.
Need maybe "梦回白玉京手游" in original; Our first p says "梦回白玉京是一款" not "手游" maybe okay. Could include "手游" for clarity: "梦回白玉京是一款以唯美水墨画风勾勒东方修仙世界的放置卡牌手游。" Good.
Need maybe "卡牌" should not be confused with game mechanics? Original says "放置卡牌体验"; yes.
Need "玩法与内容体量" in game intro; okay.
Need perhaps "游戏介绍" first point "定位为水墨仙侠题材的放置卡牌手游" plus "仅需简单操作" okay.
Need maybe "优势" should "相对同类在玩法、画面、系统、优化等方面的长处" Our sections include advantages. Good.
Need "操作指南" "具体步骤与界面操作说明，条理清晰、可照做" yes.
Need "魅力" "情感吸引力与让人愿意长期游玩" yes.
Need "使用说明" "安装与权限、首次上手、常见设置与注意事项" yes.
Need if "常设置" maybe "系统设置" with quotes, yes.
Need "全文共 4~7 h3" We have h3 for each section. Need not count h3 in "首段 p"? no.
Need "只输出一段可直接写入数据库的 HTML 正文片段" Could include newlines between tags. This is okay. It is "HTML 正文片段". Could writing multiple lines be considered "一段"? The prompt says output a fragment, not necessarily one line. Since tags are separate, newlines fine. "一段 HTML 正文片段" not "一段连续文本". Good.
Need perhaps no indentation? Fine.
Let's think about "allowed HTML tags only p, h3" The h3 and p tags have no attributes. Good.
Need maybe "禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）" no. Good.
Potential issue: "全部小节字数" not specified. Good.
Need maybe "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序" The "first h3" should be game intro. Good. "其余小节再按其下列顺序" after game intro: advantage, operation, charm, use. Good. "末位固定review". Good.
Need maybe "已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者" We have 5. The "游戏介绍" and "使用说明" are rewriteKeys; maybe those two are from "采集"? But no matter.
Need maybe "全篇统一为同一种序号格式" but each section restarts numbering? It says "全篇保持同一格式" and "各小节独立" counts. Does "各小节独立" mean numbering resets each section? Likely yes. "每条要点须带序号且全篇统一为同一种序号格式"; "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）". This implies each section numbers 1..N independently. We restart numbering for each h3. That's typical. "全篇保持同一格式" means use same delimiter, not necessarily continuous. Good. Need perhaps if "全篇统一" could mean numbering continues across sections? But "各节独立" and each section has 3-6, so reset. Our output resets. Good.
Need maybe "各节独立" yes.
Need maybe "每小节先 <h3>" but for first p then h3. Good.
Potential issue: "禁止输出 markdown code fences" If we output raw text, no. Good.
Need maybe "only output" no "Here is" text. Good.
Let's ensure review final no "1." etc. It says "一段短评" but with 175 chars, yes.
Need maybe "测评" section h3 "梦回白玉京测评" followed by one p, no numbered. Good.
Need perhaps "最后一个小节固定为「梦回白玉京测评」（已在下列顺序末位）" So "梦回白玉京测评" h3 should be the 6th h3. Good.
Let's formulate final now with exact raw HTML. Need perhaps not include any indentation? It's okay. I can output:
<p>梦回白玉京是一款以唯美水墨画风勾勒东方修仙世界的放置卡牌手游。游戏用缥缈云海、古朴建筑、灵兽异兽与仙家法宝构建出充满东方美学的架空仙侠世界，让玩家 
