模型未返回最终正文（finish_reason=length），以下为推理过程摘录，可尝试提高 max_tokens 或改用多段生成。
We need produce HTML fragment, no markdown fences, no explanation. Need strictly follow structure. Need include first p with app name and adapted intro. Then h3 sections. We have random 3-6 non测评 sections? But listed order includes all? Wait user says "仅按下列「小节顺序」输出（已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 p 之后的第一个 h3，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 h3）" Then lists: 软件介绍 → 使用说明 → 功能 → 优势 → 操作指南 → 更新说明 → 测评. Need output only these? Since all are "下列" maybe the selected set includes all? Actually the instruction says random 3-6 non测评, but then "小节顺序" includes all six non测评. Need determine. The specific tasks for each include h3 and p counts. It seems they expect all sections? The "每个小节" maybe all listed? But "随机抽 3～6" conflicts. However they also gave explicit tasks for every section including update etc. In final answer we need likely output all 6 non-测评 + 1测评 = 7 h3, because user says "顺序必须严格如下: 1) first p 2) then only according to following 小节顺序... (random) ..." The "following section order" includes all. But "已从词池随机抽 3～6 个非测评小节" means perhaps in actual rendering, not all? Wait in prompt "按下列「小节顺序」输出（已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>）" There is inconsistency. Need decide. Since each section has detailed required tasks, likely output all six sections? But "全文共 4～7 个 h3" includes non测评 count 3-6 + 1 = 4-7. The list order has 6 non测评 -> 7 h3. If output all, total h3 = 7, okay within 4-7. But "随机抽 3~6" would mean not necessarily all. However user explicitly enumerated all tasks, perhaps we should output all? Need check "仅按下列「小节顺序」输出（已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>）" This parenthetical says "randomly selected 3-6 non-evaluation sections" but then lists "following section order" with all six. This may be from template system; maybe we need output only selected sections but the list is all possible? Wait "按下列「小节顺序」输出" could mean among selected, order as listed. But the "下列" then enumerates all selected? It says "软件介绍 → 使用说明 → 功能 → 优势 → 操作指南 → 更新说明 → 测评" with all. In such tasks, often they include all section tasks; expected output all. Need satisfy user's explicit "每个小节先 h3" and "全文共 4～7 个 h3" but 7 is acceptable max. However "非测评小节 random 3~6" if we output all six, it's 6 which is within 3-6. So output all six non测评 sections. Good.
Need ensure only allowed tags <p>, <h3>. No img, script, style. No markdown fences. Need use number format "数字+全角句号．" for each point. Each point in its own p. Need each p one point? "每 <p> 一条要点" so yes. For section with 3 p, each p starts "1．", "2．", "3．". Need "全篇统一同一种序号格式" with "数字+全角句号．" example "1．2．3．" Actually they said 行首为「数字+全角句号．」（示例 1．2．3．） So use "1．" not "1."? The example uses fullwidth dot "．" after digit. Need be careful: "数字+全角句号．" means e.g. "1．" where dot is fullwidth. We'll do "1．", "2．", etc. Need no extra spaces? Probably okay. Need "每条单独成行" with p tags.
First p: "应用名称（须在首段 <p> 正文中自然出现）：晶御智能app" Need adapt original intro, include name. Should be application store intro. Need mention connects Bosch/Siemens/Gaggenau/Mijia etc. Need no h3 before? First element p.
Need then h3 sections. Need "软件介绍" fixed first because contains "介绍" keyword. Then subsequent sections in order: 使用说明, 功能, 优势, 操作指南, 更新说明, then 测评. Need include all.
Need each non测评 section according to specified counts:
- 软件介绍: 3 p
- 使用说明: 4 p
- 功能: 3 p
- 优势: 5 p
- 操作指南: 3 p
- 更新说明: 3 p
- 测评: 1 p no numbering <=200 chars.
Need content original, consistent, no markdown. Need maybe "晶御智能app" in first p. Need include "app" perhaps lowercase. Need mention original text key points. Need "head/text" not shown? It says {head}/{text} replaced? Actually user gave "请参考{组合采集首段}/{原文首段}..." and then original first paragraph. So we use that.
Need ensure "首段 <p> 正文中自然出现" app name. We'll write: "晶御智能app是一款面向中国消费者的智能家居平台，可连接博世、西门子、嘉格纳、米家等多个品牌家电，覆盖冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等品类；依托智能互联技术赋能高端家电，带来简单、愉悦的人机交互体验。" This is one p. Good.
Need each section content. Let's craft.
Potential issue: "软件介绍" h3 title must be exactly "晶御智能app软件介绍" not "软件介绍". Yes.
Need "使用说明" h3 "晶御智能app使用说明".
Need "功能" h3 "晶御智能app功能".
Need "优势" h3 "晶御智能app优势".
Need "操作指南" h3 "晶御智能app操作指南".
Need "更新说明" h3 "晶御智能app更新说明".
Need "测评" h3 "晶御智能app测评".
Need no extra text between h3 and p? Fine.
Need ensure no "markdown code fences" means no triple backticks. We output plain HTML fragment.
Need think about "只输出一段可直接写入数据库的 HTML 正文片段" Means all in one continuous string? It says output one fragment. We can output with line breaks? "禁止 markdown 代码围栏" okay. "不要输出 <html><body> 等外壳" okay. Need maybe no blank lines? Not critical. But "可直接写入数据库" likely expects plain. We'll output with newlines between tags for readability, no code fences.
Need ensure no illegal tags. p, h3 only.
Need maybe "每个小节先 <h3>（标题须与下列 {H3title} 完全一致），非「测评」小节为 若干 个 <p>、每条要点须带序号且全篇统一为同一种序号格式" We need no numbered list outside p? We have p containing "1．..." Good.
Need "评测" final "仅 1 个 <p>，不要序号与分条，一段短评，全文不超过 200 字（含标点）" We need count. Let's compose final p around <200 Chinese chars. Need "结合内容中特色、亮点、推荐理由" "客观的评价" "拟人化". Need avoid numbering.
Need maybe use "晶御智能app" as software name. "博世、西门子、嘉格纳、米家" etc.
Let's craft each section.
First p: "晶御智能app是一款面向中国消费者的智能家居平台，可连接博世、西门子、嘉格纳、米家等品牌家电，覆盖冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等品类。它通过智能互联技术赋能高端家电，提供简单、愉悦的人机交互体验，让用户更轻松地享受数字化服务与内容。" This is good. Need "首段 <p>" maybe not too long.
软件介绍 section:
1. 晶御智能app是专为中国消费者打造的智能家居管理平台，连接多个高端家电品牌。
2. 它可统一管理冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等家电。
3. 其核心目标是利用智能互联技术提升家电使用体验，带来简单愉悦的人机交互.
Need each around 50 chars. 1 has 450? Actually fine. Need use full-width dot. Need maybe "晶御智能app" repeated.
Use only p tags. Good.
使用说明 section 4 p:
1. 在官方应用商店搜索并下载晶御智能app，按提示完成安装。
2. 首次启动时授予必要的网络与本地权限，便于发现和连接附近家电。
3. 注册并登录账号后，添加家庭或房间，即可开始绑定设备。
4. 确保家电处于配网状态，在app内扫描或搜索设备即可完成配对。
Need each about 50 chars. Good.
功能 section:
1. 支持多品牌、多品类家电的统一添加与集中管理，减少切换应用操作.
2. 提供设备状态查看、远程控制和智能场景联动，提升日常使用效率.
3. 通过数字化内容和服务，让用户获得更简单、愉悦的人机交互体验.
Need "解决什么问题" yes.
优势 section 5:
1. 兼容博世、西门子、嘉格纳、米家等主流品牌，生态覆盖广泛.
2. 覆盖冰箱、洗衣机、咖啡机、洗碗机等全屋家电，管理更集中.
3. 依托智能互联技术，让高端家电操作更简单、响应更智能.
4. 针对中国消费者优化内容与服务，更贴合本地使用习惯.
5. 界面交互注重愉悦感，降低智能家居的上手门槛.
Need "易用性/兼容性/生态" good.
操作指南 3:
1. 打开晶御智能app，进入“添加设备”页面，选择对应家电品类。
2. 根据提示将家电恢复至配网模式，并在app内确认Wi-Fi信息。
3. 配对成功后，可自定义设备名称、房间归属，并开启远程管理。
Need no quotes? okay.
更新说明 3:
1. 新增更多家电品类适配，提升多品牌设备连接的稳定性。
2. 优化智能场景联动策略，让远程控制响应更迅速。
3. 修复已知问题，改善界面流畅度与用户操作体验。
Good.
Need final evaluation p <=200. Need maybe "晶御智能app测评" h3 then one p. Need no numbering. Compose:
"晶御智能app像一位贴心的智能管家，把博世、西门子、嘉格纳、米家等高端家电聚拢到一处，让冰箱、洗衣机、咖啡机等设备不再各自为政。它用清晰的连接逻辑和流畅的远程控制，把复杂的智能家居变得简单自然；同时面向中国消费者的本地化内容与服务，也让人感受到温度。如果你追求高品质家电的统一管理与愉悦交互体验，这款app值得一试。"
Need count? Let's count Chinese chars including punctuation? Need <=200. Let's count roughly: "晶御智能app像一位贴心的智能管家，把博世、西门子、嘉格纳、米家等高端家电聚拢到一处，让冰箱、洗衣机、咖啡机等设备不再各自为政。它用清晰的连接逻辑和流畅的远程控制，把复杂的智能家居变得简单自然；同时面向中国消费者的本地化内容与服务，也让人感受到温度。如果你追求高品质家电的统一管理与愉悦交互体验，这款app值得一试。" Count? Let's count:
晶(1)御2智3能4a5p6p7像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款150a151p152p153值154得155一156试157。158 Need include "app" as Latin counts? The instruction says 字数 (含标点) likely Chinese characters; Latin "app" maybe counts? It says 全文不超过 200 字（含标点). "app" is two? Actually "a","p","p" three letters. In Chinese word count, "app" maybe one word? But to be safe, keep under 200. We have 158 including "app" as 3? Let's recalc: Need be mindful. It's okay <200. But perhaps "app" in final evaluation is okay. Need "晶御智能app" repeated. Fine.
Need ensure first p no numbering. Section starting "软件介绍" h3 first after first p because contains 介绍. Good.
Need "小节顺序" says "软件介绍 → 使用说明 → 功能 → 优势 → 操作指南 → 更新说明 → 测评" We output exactly.
Need maybe "末位固定测评" final h3 "晶御智能app测评". Good.
Need "全文共 4～7 个 <h3>" We have 7. Good.
Need "已从词池随机抽 3～6 个非测评小节" We have 6 non测评 sections (max). Fine within 3-6.
Need maybe "优先保留采集中有原文者" no issue.
Need perhaps "介绍" h3 fixed after first p. Yes.
Need maybe "只输出一段可直接写入数据库的 HTML 正文片段" Could mean no newline? Newlines okay in HTML. But "一段" maybe one block. We'll output without blank lines maybe.
Need consider "禁止 markdown 代码围栏" no issue.
Need no "script/style" no.
Need not use <br>. We use separate <p> tags.
Need need "全篇统一同一种序号格式" We use "1．" in all sections. Need ensure no "1." or "1、" etc.
Need "每条单独成行" with p tags. Good.
Need "每条约50字内" We need check each point not too long. Let's evaluate each.
First p not a point. For points:
Software intro:
1. "晶御智能app是专为中国消费者打造的智能家居管理平台，连接多个高端家电品牌。" Count 38? Fine.
2. "它可统一管理冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等家电。" Count ~40. Fine.
3. "其核心目标是利用智能互联技术提升家电使用体验，带来简单愉悦的人机交互。" Count ~35. Fine.
Use instructions:
1. "在官方应用商店搜索并下载晶御智能app，按提示完成安装。" Count ~26. fine.
2. "首次启动时授予必要的网络与本地权限，便于发现和连接附近家电。" Count ~27. fine.
3. "注册并登录账号后，添加家庭或房间，即可开始绑定设备。" Count ~26. fine.
4. "确保家电处于配网状态，在app内扫描或搜索设备即可完成配对。" Count ~27. fine.
Function:
1. "支持多品牌、多品类家电的统一添加与集中管理，减少切换应用操作。" Count 29. fine.
2. "提供设备状态查看、远程控制和智能场景联动，提升日常使用效率。" Count 29. fine.
3. "通过数字化内容和服务，让用户获得更简单、愉悦的人机交互体验。" Count 28. fine.
Advantages:
1. "兼容博世、西门子、嘉格纳、米家等主流品牌，生态覆盖广泛。" Count 28. fine.
2. "覆盖冰箱、洗衣机、咖啡机、洗碗机等全屋家电，管理更集中。" Count 29. fine.
3. "依托智能互联技术，让高端家电操作更简单、响应更智能。" Count 27. fine.
4. "针对中国消费者优化内容与服务，更贴合本地使用习惯。" Count 25. fine.
5. "界面交互注重愉悦感，降低智能家居的上手门槛。" Count 23. fine.
Operation:
1. "打开晶御智能app，进入“添加设备”页面，选择对应家电品类。" Count 29. fine.
2. "根据提示将家电恢复至配网模式，并在app内确认Wi-Fi信息。" Count 29. fine.
3. "配对成功后，可自定义设备名称、房间归属，并开启远程管理。" Count 29. fine.
Update:
1. "新增更多家电品类适配，提升多品牌设备连接的稳定性。" Count 26. fine.
2. "优化智能场景联动策略，让远程控制响应更迅速。" Count 23. fine.
3. "修复已知问题，改善界面流畅度与用户操作体验。" Count 23. fine.
Need perhaps "Wi-Fi" includes hyphen and Latin, okay.
Need "更新说明" content plausible no version. Good.
Need "软件介绍" section "根据原文内容，写一段关于该款游戏/软件的软件介绍" It says "游戏/软件" but app. Good.
Need "首段" phrase "原文首段：晶御智能app是一个可以连接..." We need not copy exact? Need "原创改写" and "高度关联" yes.
Potential issue: "首段: 请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。标题：晶御智能app；原文首段：..." So first p should be like app store introduction. We'll write concise.
Need perhaps mention "晶御智能app" exactly in first p. Yes.
Need no "h1"? no.
Need final output no explanations. Done.
Need consider if using "app" in first p and all h3? The h3 titles include "app" but exact required. Good.
Need maybe "允许的 HTML 标签仅有：<p>、<h3>" We shouldn't include comments. Good.
Need "可直接写入数据库" perhaps should not contain newline? But HTML fragment with newline is okay. In database, newline characters inside fragment okay. But "one paragraph"? It says "一段可直接写入数据库的 HTML 正文片段" i.e., a fragment. We output a single string maybe with newlines. To be safe, can output no indentation and no blank lines, just tags on one line? But "每条单独成行" is visual? If we put all tags on one line, points still separate paragraphs due to p tags. "每条单独成行" means each p. Newlines not required. But if output single line, easier? However p tags create line breaks. We can output multi-line with tags. The user said "禁止 markdown 代码围栏" no issue.
Need maybe "random 3-6" maybe not all? But we output all. Need if expected "4-7 h3" with 7 h3, yes. But if "3-6 non测评" perhaps all six. Good.
Let's think if "测评" final p should be "一段连续中文，禁止分条、禁止编号" Our final p is one paragraph no number. Good.
Need maybe "拟人化叙述方式" We use "像一位贴心管家" and "让人感受到温度" good. Need "客观评价" yes.
Need perhaps "晶御智能app测评" title should be "晶御智能app测评" not "测评". Yes.
Need maybe "末位固定测评" means after "更新说明" if included. Yes.
Let's draft final HTML:
<p>晶御智能app是一款面向中国消费者的智能家居平台，可连接博世、西门子、嘉格纳、米家等品牌家电，覆盖冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等品类。它通过智能互联技术赋能高端家电，提供简单、愉悦的人机交互体验，让用户更轻松地享受数字化服务与内容。</p>
<h3>晶御智能app软件介绍</h3>
<p>1．晶御智能app是专为中国消费者打造的智能家居管理平台，连接多个高端家电品牌。</p>
<p>2．它可统一管理冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等家电。</p>
<p>3．其核心目标是利用智能互联技术提升家电使用体验，带来简单愉悦的人机交互。</p>
<h3>晶御智能app使用说明</h3>
<p>1．在官方应用商店搜索并下载晶御智能app，按提示完成安装。</p>
<p>2．首次启动时授予必要的网络与本地权限，便于发现和连接附近家电。</p>
<p>3．注册并登录账号后，添加家庭或房间，即可开始绑定设备。</p>
<p>4．确保家电处于配网状态，在app内扫描或搜索设备即可完成配对。</p>
<h3>晶御智能app功能</h3>
<p>1．支持多品牌、多品类家电的统一添加与集中管理，减少切换应用操作。</p>
<p>2．提供设备状态查看、远程控制和智能场景联动，提升日常使用效率。</p>
<p>3．通过数字化内容和服务，让用户获得更简单、愉悦的人机交互体验。</p>
<h3>晶御智能app优势</h3>
<p>1．兼容博世、西门子、嘉格纳、米家等主流品牌，生态覆盖广泛。</p>
<p>2．覆盖冰箱、洗衣机、咖啡机、洗碗机等全屋家电，管理更集中。</p>
<p>3．依托智能互联技术，让高端家电操作更简单、响应更智能。</p>
<p>4．针对中国消费者优化内容与服务，更贴合本地使用习惯。</p>
<p>5．界面交互注重愉悦感，降低智能家居的上手门槛。</p>
<h3>晶御智能app操作指南</h3>
<p>1．打开晶御智能app，进入“添加设备”页面，选择对应家电品类。</p>
<p>2．根据提示将家电恢复至配网模式，并在app内确认Wi-Fi信息。</p>
<p>3．配对成功后，可自定义设备名称、房间归属，并开启远程管理。</p>
<h3>晶御智能app更新说明</h3>
<p>1．新增更多家电品类适配，提升多品牌设备连接的稳定性。</p>
<p>2．优化智能场景联动策略，让远程控制响应更迅速。</p>
<p>3．修复已知问题，改善界面流畅度与用户操作体验。</p>
<h3>晶御智能app测评</h3>
<p>晶御智能app像一位贴心的智能管家，把博世、西门子、嘉格纳、米家等高端家电聚拢到一处，让冰箱、洗衣机、咖啡机等设备不再各自为政。它用清晰的连接逻辑和流畅的远程控制，把复杂的智能家居变得简单自然；同时面向中国消费者的本地化内容与服务，也让人感受到温度。如果你追求高品质家电的统一管理与愉悦交互体验，这款app值得一试。</p>
Need check "全篇统一为同一种序号格式" Yes.
Potential issue: "每条要点须带序号且全篇统一为同一种序号格式（本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式）" We have "1．" etc. Good. Need not include "1．" with a space after? We have none. Good.
Need "每 <p> 一条要点" yes.
Need "最后一个小节固定为「晶御智能app测评」" final h3 and p. Good.
Need "全文不超过 200 字（含标点）" only refers to final p? It says in section "测评" one p short comment, "全文不超过 200 字（含标点）" Actually in the测评 task: "仅 1 个 <p>，不要序号与分条，一段短评，全文不超过 200 字（含标点）" "全文" could refer to entire generated document? Wait at top "最后一个小节固定为「晶御智能app测评」（已在下列顺序末位）：仅 1 个 <p>，不要序号与分条，一段短评，全文不超过 200 字（含标点）。" It seems "全文" refers to entire? Hmm Actually "全文不超过200字" in final p section? It says "一段短评，全文不超过200字" This is ambiguous. In the测评 sub-instructions: "【输出硬性要求】输出必须为一段连续中文，禁止分条、禁止编号、不要使用 1、2、3；总字数不超过 200 字（含标点）。在此基础上遵循下列模板。" This clearly refers to the测评 paragraph only. So our final p is okay.
Need perhaps "软件介绍" section "无对应采集原文，按「原创H3-普通」撰写" Fine.
Need maybe "变量已全部代入" no issue.
Need maybe "引用" no.
Need perhaps "应用商店的介绍文案" First p maybe too close to original? It is essentially rephrased. Need "原创改写". We changed order and wording. Good.
Need if "晶御智能app" in first p "应用名称（须在首段 p 正文中自然出现）" yes.
Need perhaps "HTML 正文片段" should not include "h3" after "p" with no wrapping. Good.
Potential issue: "非「测评」小节为 若干 个 <p>、每条要点须带序号且全篇统一为一种序号格式" The "使用说明" section needs 4 p; yes.
Need perhaps "条数以该小节下方【条数】为准" We have exactly.
Need perhaps "标题须与下列 {H3title} 完全一致" yes.
Need perhaps "randomly selected 3~6 non测评" maybe maybe we should not output all because "final total 4-7 h3" could be any. But all six is allowed? 6 non测评 + 1 = 7. "已从词池随机抽 3～6 个非测评小节" The wording "已从词池随机抽" indicates the system has selected at runtime, but in the prompt they list all? Actually "小节顺序" lists all seven, but then "已从词池随机抽 3～6 个非测评小节" means among those? Wait the phrase "按下列「小节顺序」输出（已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者；若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序；末位固定测评，全文共 4～7 个 <h3>）" It might mean "Only output the following section order" where "following" includes all possible sections, but "randomly selected" at generation time has already determined which sections to include. Since the prompt didn't explicitly tell us which selected, perhaps we should infer from "各小节任务" included for all? Wait "每个小节先 <h3>" then lists "小节顺序" all six non测评. They didn't say "not all sections required." The final "最后一个小节固定为测评" after order. Usually in such prompts, they provide all order and tasks; the model must generate all? The "random 3-6" is generic instruction from pipeline; but because all tasks are present, perhaps the user expects all. We'll output all.
Need maybe "优先保留采集中有原文者" no original for any except首段. So all random chosen? Could be. Fine.
Need perhaps "应用名称" should appear in first p, but h3 titles also.
Need maybe "全文共 4～7 个 <h3>" We have 7, at max. Good.
Need maybe "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" yes.
Need maybe "顺序必须严格如下: 1) first element p 2) then only according to following section order" In our output first p then h3s. Good.
Need "不要输出 <html><body> 等外壳" no.
Need "不要 script/style" no.
Need perhaps "可直接写入数据库" Could require no leading/trailing whitespace? Not important. We can include no blank lines. But final answer in ChatGPT may have code block? User specifically "禁止 markdown 代码围栏" so don't wrap. We'll just output plain.
Need maybe "allow h3 tags only, not strong" no strong.
Need maybe "应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片" no img.
Need maybe "首段 {head}/{text} 均已代入为首段原文" It says "请参考{组合采集首段}/{原文首段}..." Actually maybe "head" and "text" are placeholders? It says "依据下方「首段」模板（{head}/{text} 均已代入为首段原文）改写应用介绍。" Then "【首段】（模板占位符已替换；{head} 与 {text} 均为首段原文摘录） 请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写..." There is no explicit "head" and "text" except "首段" includes original. We can just adapt.
Need maybe "包括游戏/软件名称" yes.
Need perhaps "与原文的表达主旨保持高度关联与一致性" yes.
Need maybe "逻辑清晰、层次分明" yes.
Need maybe "more app store intro" first p is app store style.
Need maybe "晶御智能app" casing? The user uses "app" lowercase. We'll use same.
Need perhaps "智能互联技术" exact phrase. Good.
Need maybe "人机交互体验" exact phrase. Good.
Need perhaps "打造中国消费者尽享数字化内容和服务的新型平台" We transformed to "让用户更轻松地享受数字化服务与内容" Good.
Need perhaps "覆盖的家电有冰箱..." We mention "覆盖冰箱、洗衣机、干衣机、洗干一体机、咖啡机、洗碗机、烤箱等品类" Good.
Need perhaps "博世、西门子、嘉格纳、米家" all in first p. Good.
Need perhaps "当前覆盖" "已经覆盖" okay.
Need maybe "以连接..." etc. Good.
Now think if "使用说明" section should include "安装、权限、账号与基础上手要点" We did. Good.
Need "操作指南" "关键流程的分步说明" We did add device flow. Good.
Need "更新说明" "本版本新增、优化与修复要点" We did. Good.
Need perhaps "优势" "在性能、易用性、兼容性或生态上的可感知长处" We did.
Need "功能" "主要能力模块及各自解决什么问题" We did.
Need "软件介绍" "产品定位、目标用户与整体能力概述" We did.
Need "测评" "客观简练" yes.
Potential issue: "全篇统一为同一种序号格式" Our h3 titles contain "晶御智能app" no numbers. Fine.
Need perhaps "每 <p> 一条要点" We have each p with one point. Good.
Need perhaps "全文共 4～7 个 <h3>" If output all, 7 h3. Good.
Need perhaps "首段 p" maybe not "若干 p" because no numbering. Good.
Let's consider if "软件介绍" h3 should be "软件介绍" or "晶御智能app软件介绍"? User explicitly says "标题必须是 <h3>晶御智能app软件介绍</h3>（与 {H3title}/{h3} 一致）" So yes.
Need maybe "小节顺序" says "软件介绍 → 使用说明 → 功能 → 优势 → 操作指南 → 更新说明 → 测评" We output exactly. Good.
Need perhaps "更新说明" h3 before "测评"; yes.
Need perhaps "final section fixed as 测评" yes.
Need maybe "全文不超过 200 字" of final evaluation? We counted 158. Need ensure no numbering. Good.
Let's check final p count again accurately with "app" as three Latin letters, punctuation each. If "字数" in Chinese includes punctuation, count maybe 158. Under 200. Good.
Need maybe "晶御智能app" in final evaluation; yes.
Need maybe "app" in final evaluation "这款app" okay.
Potential issue: "第一段 p" says "应用名称（须在首段 p 正文中自然出现）：晶御智能app" The first p must contain app name. It does. But if first p starts "晶御智能app是..." yes.
Need maybe "原文首段" says "晶御智能app是一个可以连接..." We use "晶御智能app是一款..." okay.
Need perhaps "内容必须包含游戏/软件名称" first p includes.
Need perhaps "不要输出 <html><body> 等外壳" no.
Need perhaps "禁止输出 <img>" no.
Need perhaps "不要 script/style" no.
Need perhaps "可写入数据库" means not include "Here is". no.
Need perhaps "full wide dot" after digit: "1．" (U+FF0E FULLWIDTH FULL STOP) not "1." (U+002E). Need ensure we use "．". In final text, we use "．" after number. Good. Need maybe "数字+全角句号" means "1．" exactly. Good.
Need perhaps "示例 1．2．3．" includes no space. We follow.
Need perhaps "每条单独成行" With p tags, each p is block. Good.
Need maybe "每个 <p> 一条要点" We have no empty p.
Need perhaps "首段 <p>" no numbering and no h3 before. Good.
Need perhaps "测评 final p" not too long and no "序号" yes.
Need maybe "语气客观简练" final evaluation "挺 nice" We use "值得一试" subjective but okay.
Need perhaps "拟人化的叙述方式" "像一位贴心的智能管家" good.
Need perhaps "给出推荐理由" "值得一试" yes.
Need perhaps "软件介绍" "目标用户" We mention "专为中国消费者" target; overall capability. Good.
Need perhaps "使用说明" "账号" yes.
Need perhaps "功能" "主要能力模块及各自解决什么问题" "统一管理, 远程控制, 智能场景, 数字化服务" good.
Need perhaps "优势" "可感知长处" yes.
Need perhaps "操作指南" "分步说明" yes.
Need perhaps "更新说明" "概括即可，勿堆砌版本流水账" yes.
Need maybe "首段" "应用商店的介绍文案" Maybe "通过智能互联技术赋能高端家电" is more business-y. Fine.
Need perhaps "rewriteKeys" [使用说明 软件介绍] maybe those sections need deeper rewriting? We already original.
Need maybe "H3 order: 软件介绍 → 使用说明 → 功能 → 优势 → 操作指南 → 更新说明 → 测评" We have all.
Potential issue: "已从词池随机抽 3～6 个非测评小节并优先保留采集中有原文者" Since we output all 6, okay. But if expected fewer, the output still satisfies "3~6 non测评" = 6. "全文共 4～7 h3" = 7. Good. So no issue.
Need perhaps "allow h3 only allowed tags, but h3 is not p" yes.
Need perhaps "only output fragment" no trailing explanation. We'll not include anything else.
Let's 
