模型未返回最终正文（finish_reason=length），以下为推理过程摘录，可尝试提高 max_tokens 或改用多段生成。
我们需要理解任务。用户要求只输出一段可直接写入数据库的 HTML 正文片段。禁止 markdown 代码围栏、禁止解释。允许标签 p, h3。需要输出顺序：
1) 第一个元素是一个 <p>：依据「首段」模板改写应用介绍。标题：协同通信app；原文首段：协同通信app是中国电信旗下的一款即时通话的软件，集云通讯录、电话会议和智能拨号等通信能，提供给用户更加快速方便的交流服务，同事、客户随时随地的进行沟通大大提高了办公效率，并且还能够支持多人同时在线通话，采用专用电话网络（PSTN线路）传输语音，语音品质。
需要自然出现应用名称。首段原文中已出现。需要改写为应用商店介绍文案，保持主旨。可能写成：协同通信app是中国电信推出的一款即时通话软件，集成云通讯录、电话会议与智能拨号等能力，让用户与同事、客户随时沟通，显著提升办公效率。它支持多人同时在线通话，并依托PSTN专用电话网络传输语音，带来清晰稳定的通话音质。这样即可。
然后仅按下列小节顺序输出：功能 → 推荐理由 → 操作指南 → 测评。但整体结构说明：先首段 p，然后 3~6 个非测评小节? Wait 整体结构 says "然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）"
But then 小节顺序 shows exactly four: 功能 → 推荐理由 → 操作指南 → 测评. That is 3 non-测评 sections, so total 4 h3. So we do all three non-测评 sections plus final 测评. Need output each h3 with exact titles: <h3>协同通信app功能</h3>, <h3>协同通信app推荐理由</h3>, <h3>协同通信app操作指南</h3>, <h3>协同通信app测评</h3>. Each non-测评 has specified number of p items: 功能 3, 推荐理由 4, 操作指南 5. Each item is a <p> with sequence number "数字+全角句号．" at beginning. All items must use same format, not necessarily restart? Important: "每条要点须带序号且全篇统一为同一种序号格式（本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式）" Ambiguity: Should numbering continue across sections or restart per section? It says "每节要点条数以该小节下方【条数】为准" and "本节固定 3 条" etc. Usually in such generated content, numbering restarts in each section? But "全篇统一为同一种序号格式" means format identical, not necessarily continuous. But "用序号分条" in each section, with examples 1. 2. 3. It likely restarts each section, because each section has 3-6 items and they're separated by h3. Need decide. We can use 1. 2. 3. in each section. But if "全篇统一" maybe continuous sequence across all items? Let's read prompt carefully: "每个小节先 <h3>（标题须与下列 {H3title} 完全一致），非「测评」小节为 **若干** 个 <p>、每条要点须带序号且**全篇统一为同一种序号格式**（本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式）；**每节要点条数以该小节下方【条数】为准**（在 3～6 条之间且各节独立）。" This suggests each section independent in count, but possibly numbering continuous? "各节独立" means counts independent. The phrase "每条单独成行" with <p> means each p contains one line. "行首为数字+全角句号" If continuous, then section 2 would start 4., section 3 7., but "本节固定 4 条" doesn't forbid. Yet examples show 1.2.3. per section? Usually generated subheadings with numbered lists restart at 1. Since "各节独立" perhaps means each section has its own number of points, not continuous. But "全篇统一为同一种序号格式" could just be same style not numbering range. Need infer from "【条数】用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式；**本节须写 3 条**要点" This is repeated for each section. If they wanted continuation, they'd say "全文顺序编号". They don't. So restart each section at 1. likely. But "全篇统一" is satisfied because all use 1．2．3． etc. Let's check surrounding context: "从词池随机抽 3～6 个非测评小节" "全文共 4～7 个 h3" "每个小节先 h3，非测评小节为若干 p，每条要点须带序号且全篇统一为同一种序号格式" If multiple sections with numbered lists, "same format" means each line begins with "1." etc. So yes restart per section. We'll do that.
Need ensure no markdown code fenced, no extra text. Output only HTML fragment. Need include all exact h3. Need final测评 only one p, no numbered list, <=200 Chinese chars. Need write plausible content.
Let's craft content.
Need first p: "协同通信app是中国电信推出的一款专业即时通话软件，集成云通讯录、电话会议与智能拨号等核心通信功能，致力于为用户提供更快捷、更稳定的沟通体验。无论是同事协作还是客户联络，都能随时发起通话，有效提升办公效率；同时支持多人在线通话，依托PSTN专用电话网络传输语音，保障清晰自然的通话音质。" That's one p. Should be fine.
Then h3 功能. Need 3 p items, each a single sentence around 50 chars. Need mention capabilities solving problems.
Possible items:
1．云通讯录自动同步企业联系人，让同事客户信息随手可查，省去手动整理麻烦。
2．电话会议支持多人同时接入，远程协作无需见面即可高效开会，节省沟通成本。
3．智能拨号结合PSTN专用线路，一键快速呼叫且语音清晰稳定，保障重要通话品质。
Need ensure each p starts with "1．" etc. Use full-width dot U+FF0E? Actually "．" is fullwidth full stop (FF0E). User says 数字+全角句号． Example 1．2．3． Yes.
Need h3 推荐理由. 4 p items:
1．依托中国电信PSTN网络，通话音质清晰稳定，关键沟通不掉链子。
2．云通讯录自动同步企业联系人，查找同事客户更快捷，减少通讯录维护成本。
3．支持多人电话会议，随时随地远程开会，让团队协作效率大幅提升。
4．智能拨号与常用联系人分组结合，一键发起通话，操作简单易上手。
Need maybe "面向新用户说明为何值得安装使用，落到具体收益". Good.
Need h3 操作指南. 5 p items:
1．下载安装协同通信app后，使用中国电信手机号码完成注册并登录账号。
2．进入云通讯录同步企业通讯录，或手动添加同事与客户联系电话。
3．点击联系人即可发起智能拨号，通话中可随时邀请更多成员加入电话会议。
4．在电话会议界面选择需要参会的人员，一键发起多人同时在线通话。
5．通过设置中的通话记录与通讯录分组，快速管理常用联系人和后续回拨。
Need be careful: "操作指南" key processes step-by-step. Good.
Need h3 测评. One p, no numbered list, <=200 chars. Need include "协同通信app" perhaps. Objective. Could be:
协同通信app将云通讯录、智能拨号和电话会议整合在同一个即时通话平台中，依托中国电信PSTN线路带来稳定清晰的语音体验。实际使用中，企业联系人同步与一键拨号让沟通路径更短，多人会议功能也很好地满足了远程协作需求。整体界面简洁，功能实用，对追求高效办公的团队来说是一款值得尝试的通信工具。
Count? Let's count roughly. Chinese chars including punctuation. Need ≤200. Let's count carefully later.
Need ensure final p not start with number. Good.
Potential issue: "首段" says "请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。标题：协同通信app；原文首段：..." So first p must be a rewrite, not exactly original. We'll do.
Need include "协同通信app" in first paragraph. Yes.
Need "禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）。" No img.
Need "不要输出 <html><body> 等外壳" ok.
Need "only output a paragraph block" no intro.
Need ensure no blank lines between elements? Could be no extra whitespace? It's fine. But "可直接写入数据库的 HTML 正文片段" likely store string. We can output h3 and p tags on separate lines? It says no markdown, no explanations. Plain HTML can have newlines. Should be fine. But to be safe, output as one line? Hmm, database HTML snippet can include newlines. Newlines between blocks are fine. But if "正文片段" maybe they'd prefer no leading/trailing whitespace? We'll output each on its own line without indentation. That's acceptable.
Need ensure numbering format with full-width dot after numeral. "1．" includes no space. Good.
Need consider "全篇统一为同一种序号格式" But if we restart at 1 for each section, all same format. Good.
Need maybe "推荐理由" and "功能" had rewriteKeys [推荐理由 功能], but no special? It says "整篇一次生成时可作语气参考" no issue.
Need check if "操作指南" "5 个 <p>，每 <p> 一条要点" We'll output 5 p.
Need "最后一个小节固定为「协同通信app测评」" yes.
Need "全文共 4～7 个 <h3>" We have 4.
Need "末位固定测评" yes.
Need "若含「介绍」「简介」类关键词会固定排在首段 p 之后的第一个 h3" Our sections don't include. Good.
Need "非测评小节为若干个 p" Good.
Need "每条单独成行" Since each p is its own line. Good.
Need "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" We have 3,4,5.
Need "功能" "主要能力模块及各自解决什么问题" Our items mention cloud contacts, conference, intelligent dial. Good.
Need "推荐理由" "面向新用户说明为何值得安装使用，需落到具体收益" Good.
Need "操作指南" "关键流程的分步说明" Good.
Need "测评" "根据上文中对协同通信app的内容介绍，原创一篇200字左右的的评测，需要结合内容中对于协同通信app的特色、亮点、推荐理由等部分进行一个客观的评价，保证语句通顺流畅，尽量拟人化的叙述方式。" Need "拟人化" perhaps means personification? Hmm "尽量拟人化的叙述方式" weird for app review. Maybe means "口语化/有人情味"? Could adjust final p to be slightly conversational. But "客观简练" from earlier. Need combine. Let's craft final p with a human touch: "协同通信app像一位可靠的通信助手，把云通讯录、智能拨号和电话会议都装进一个界面。依托中国电信PSTN线路，它的语音表现清晰稳定，开会、联络客户时都让人放心；企业通讯录同步也让找人变得很省事。整体功能扎实、上手简单，尤其适合追求高效协作的团队日常使用。" This is 100 chars. Good.
Need count final p ≤200. Let's count final p: "协同通信app像一位可靠的通信助手，把云通讯录、智能拨号和电话会议都装进一个界面。依托中国电信PSTN线路，它的语音表现清晰稳定，开会、联络客户时都让人放心；企业通讯录同步也让找人变得很省事。整体功能扎实、上手简单，尤其适合追求高效协作的团队日常使用。" Count roughly: 协同通信app (6? Chinese 4 + app? Let's count "协同通信app" as 6 chars? Actually 协(1)同(2)通(3)信(4)a(5)p(6)p(7) maybe 7. We'll just ensure under 200. This is definitely under 200.
Need perhaps "app" in final allowed? Yes.
Need perhaps "测评" section should not use "分条" or "编号". Good.
Potential issue: "全篇统一为同一种序号格式" Could be interpreted as numbering should continue from 1 to 12 across all sections. Let's re-evaluate. The prompt says "每个小节先 <h3>... 非「测评」小节为 **若干** 个 <p>、每条要点须带序号且**全篇统一为同一种序号格式**（本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式）；**每节要点条数以该小节下方【条数】为准**（在 3～6 条之间且各节独立）。" If each section restarts, "本节须写 3 条" in each section. "全篇统一" likely "same format" not "sequence continues". It explicitly says "本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式" The "same format" is "数字+全角句号" not "continuous numbering". So restarting is fine. However, could "全篇统一为同一种序号格式" mean if you choose "1." in first section, all sections use "1."; irrelevant. There's no instruction to continue numbering across sections. In fact if "全篇统一" included sequence, they'd need specify "从1到最后一条连续编号" and "各节条数" would still matter. But "各节独立" suggests each section independent in count; not necessarily numbering. Yet "本节固定 3 条" for each section means in each section there are 3 items; if numbering continuous, first section ends at 3, second begins at 4, but "本节固定 4 条" would mean 4 items in section, not necessarily numbers 1-4. Which is more common? In documents, numbered lists under H3 often restart at 1. But "全篇统一" could require all lists use Arabic numerals, not restart? Hmm.
Let's look at phrase "用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式" They don't say "各小节独立编号" or "每小节从1开始". But if we use 1.-3. in first section, 1.-4. in second, 1.-5. in third, there are duplicate numbers. Would that violate "全篇统一"? No, same format. But "全篇统一" may be read as all numbered items should follow a single continuous sequence, but they specifically say "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" Actually "各节独立" could mean each section has its own independent count, so restart. I think restart is acceptable.
Need maybe "数字+全角句号．" The dot is after number. If using 1. with ASCII period? Need ensure fullwidth. We'll use "1．" (U+FF0E). Good.
Need perhaps "推荐理由" section: "每条约50字内" Our items maybe 30-40. Good.
Need ensure all p content "原创改写" not copied from original. We'll write distinct.
Let's craft final HTML.
Potential issue: "首段 {head}/{text} 均已代入为首段原文" The first element should be "依据下方「首段」模板（{head}/{text} 均已代入为首段原文）改写应用介绍." Could be more formal. We'll include first p.
Let's write final:
<p>协同通信app是中国电信推出的一款即时通话软件，将云通讯录、电话会议和智能拨号等能力融为一体，帮助用户与同事、客户随时保持高效沟通。它支持多人同时在线通话，并采用PSTN专用电话网络传输语音，带来清晰稳定的通话音质，让办公协作更加便捷流畅。</p>
<h3>协同通信app功能</h3>
<p>1．云通讯录自动同步企业联系人，让同事客户信息随手可查，省去手动整理麻烦。</p>
<p>2．电话会议支持多人同时接入，远程协作无需见面即可高效开会，节省沟通成本。</p>
<p>3．智能拨号结合PSTN专用线路，一键快速呼叫且语音清晰稳定，保障重要通话品质。</p>
<h3>协同通信app推荐理由</h3>
<p>1．依托中国电信PSTN网络，通话音质清晰稳定，关键沟通不掉链子。</p>
<p>2．云通讯录自动同步企业联系人，查找同事客户更快捷，减少通讯录维护成本。</p>
<p>3．支持多人电话会议，随时随地远程开会，让团队协作效率大幅提升。</p>
<p>4．智能拨号与常用联系人分组结合，一键发起通话，操作简单易上手。</p>
<h3>协同通信app操作指南</h3>
<p>1．下载安装协同通信app后，使用中国电信手机号码完成注册并登录账号。</p>
<p>2．进入云通讯录同步企业通讯录，或手动添加同事与客户联系电话。</p>
<p>3．点击联系人即可发起智能拨号，通话中可随时邀请更多成员加入电话会议。</p>
<p>4．在电话会议界面选择需要参会的人员，一键发起多人同时在线通话。</p>
<p>5．通过设置中的通话记录与通讯录分组，快速管理常用联系人和后续回拨。</p>
<h3>协同通信app测评</h3>
<p>协同通信app像一位可靠的通信助手，把云通讯录、智能拨号和电话会议都装进一个界面。依托中国电信PSTN线路，它的语音表现清晰稳定，开会、联络客户时都让人放心；企业通讯录同步也让找人变得很省事。整体功能扎实、上手简单，尤其适合追求高效协作的团队日常使用。</p>
Need ensure no extra text. Good.
But let's examine "功能" section "本节固定 3 条，与其它小节条数独立." We have 3. Good.
Need maybe "操作指南" "关键流程的分步说明" Our step 5 "through settings..." is okay.
Need maybe "推荐理由" "面向新用户说明为何值得安装使用，需落到具体收益." Our items mention. Good.
Need final p "全文不超过 200 字（含标点）" We should ensure. Let's count final p carefully. It contains "协同通信app" which may be counted as Chinese? The limit says 全文不超过 200 字. If "app" letters counted as characters, still under. Let's approximate.
Final p string:
协同通信app像一位可靠的通信助手，把云通讯录、智能拨号和电话会议都装进一个界面。依托中国电信PSTN线路，它的语音表现清晰稳定，开会、联络客户时都让人放心；企业通讯录同步也让找人变得很省事。整体功能扎实、上手简单，尤其适合追求高效协作的团队日常使用。
Let's count:
协(1)同(2)通(3)信(4)a(5)p(6)p(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)P(48)S(49)T(50)N(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) Under 200. Good.
Need check overall no markdown code fences. We'll output plain text. Should not include "```html" etc. Good.
But let's consider if "允许的 HTML 标签仅有：<p>、<h3>" We comply. We have no extra. Good.
Need perhaps "应用截图由系统在生成后按小节顺序自动插入" no issue.
Need perhaps "首段" p should "应用名称须在首段 <p> 正文中自然出现" Yes.
Potential issue: "应用名称：协同通信app" In first p, we have "协同通信app". Good.
Need perhaps "标题必须是 <h3>协同通信app功能</h3>" yes exactly.
Need perhaps "测评" final section title "协同通信app测评" exactly. Good.
Need perhaps "最后一个小节固定为「协同通信app测评」" We have.
Now, is there any need to include "介绍/简介" if not? no.
Let's think if there is any hidden "rewriteKeys" influence: "rewriteKeys（入库多段链路中曾用于抽两段深度重写；整篇一次生成时可作语气参考）=[推荐理由 功能]" Not relevant.
Need maybe "不要输出 <img>" no.
Need maybe "直接写入数据库的 HTML 正文片段" means no leading/trailing spaces? We'll produce final with no leading/trailing blank line? We can include newlines after each tag. The content itself is a string. Fine.
Potential issue with "行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式" In our output, each p starts with "1．" etc. However, because HTML rendering ignores newlines, "每条单独成行" not visually line? But in HTML p tags are block elements, so each p is a separate line visually. Good.
Need perhaps "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" Our first section 3, second 4, third 5. Good.
Need perhaps "每个小节先 <h3>，非「测评」小节为 若干 个 <p>" We do.
Need perhaps "非「测评」小节为 **若干** 个 <p>、每条要点须带序号" yes.
Need perhaps "最后一个小节固定为「协同通信app测评」" yes.
Potential issue: "末位固定测评，全文共 4～7 个 <h3>" We have exactly 4 h3. Good.
Let's think if "协同通信app功能" heading could be considered "介绍" class? No.
Need maybe "测评" p "一段连续中文，禁止分条、禁止编号、不要使用 1、2、3；总字数不超过 200 字" We don't have digits except "PSTN" and "app" (letters). No numbers. Good.
Need "尽量拟人化" We used "像一位可靠的通信助手" good.
Need "客观简练" It's objective. Good.
Let's perhaps refine final p to be more "拟人化": "协同通信app像一位可靠的通信助手..." already.
Now, is there any need to ensure "协同通信app是中国电信旗下的一款即时通话的软件" in first p? We say "协同通信app是中国电信推出的一款即时通话软件" Good.
Need "云通讯录、电话会议和智能拨号" all included. Yes.
Need "同事、客户随时随地的进行沟通大大提高了办公效率" We include. Good.
Need "支持多人同时在线通话" We include "多人同时在线通话" in first p. Good.
Need "采用专用电话网络（PSTN线路）传输语音，语音品质" We include "PSTN专用电话网络传输语音，带来清晰稳定的通话音质" Good.
Need "应用商店介绍文案" Our first p fits.
Need maybe "标题：协同通信app" not output as h1 etc. We have p.
Let's check if all p items under 功能 and 推荐理由 are "每条约50字内". Let's count:
功能 item1: "1．云通讯录自动同步企业联系人，让同事客户信息随手可查，省去手动整理麻烦。" Count: 1． (2?) Let's not worry; under 50.
Item3: "3．智能拨号结合PSTN专用线路，一键快速呼叫且语音清晰稳定，保障重要通话品质。" PSTN letters 4, total ~40. Fine.
推荐理由 item4: "4．智能拨号与常用联系人分组结合，一键发起通话，操作简单易上手。" ~33.
操作指南 item1: "1．下载安装协同通信app后，使用中国电信手机号码完成注册并登录账号。" ~34.
Need maybe "每个 p 一条要点" yes.
Let's consider if "序号" should be at beginning of each item, but we put "1．" inside p. Good.
Need perhaps "全篇统一为同一种序号格式" We use same "数字．" all sections. Good.
Potential issue: "数字+全角句号．" The "全角句号" is U+FF0E (．). Yes.
Need perhaps "no markdown code fences" final output should not be in a code fence. We'll not.
Need perhaps "禁止任何解释或前言后记" We only output HTML. Good.
Need maybe "可直接写入数据库" If we include newline and indentation, okay. But if database field is text, newlines preserved. Fine.
Need perhaps "禁止输出 <html><body> 等外壳" no.
Need perhaps "不要 script/style" no.
Now, let's revisit "整体结构" says "然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）：每个小节先 <h3>（标题须与下列 {H3title} 完全一致），非「测评」小节为 **若干** 个 <p>、每条要点须带序号且**全篇统一为同一种序号格式**（本次要求：用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式）；**每节要点条数以该小节下方【条数】为准**（在 3～6 条之间且各节独立）。"
This weirdly says "已从词池随机抽 3～6 个非测评小节" but then "小节顺序" only has 3 non-测评. We obey current list. Good.
Need maybe "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>，其余小节再按其下列顺序" Not relevant.
Let's think if "功能" first should be "协同通信app功能" and not "功能" due "rewriteKeys" maybe. Good.
Potential issue: "操作指南" "关键流程的分步说明" Step 5 "通过设置中的通话记录与通讯录分组" maybe not a key flow? It's fine. Could perhaps be:
1. 下载安装...
2. 登录后授权同步云通讯录...
3. 在通讯录中选择联系人...
4. 通话中点击添加成员...
5. 在会议管理界面查看/结束会议...
Our step 5 maybe less actionable. Let's adjust to make it more step-like:
5．在通话或会议界面点击「管理成员」，可随时添加、移除参会人或结束会议。
This is more direct. But need "具体" and "分步". Let's use this instead. Does it fit? Yes.
Need maybe "操作指南" "每条约50字内" yes.
Let's revise third section:
<h3>协同通信app操作指南</h3>
<p>1．下载安装协同通信app后，使用中国电信手机号码完成注册并登录账号。</p>
<p>2．进入云通讯录同步企业通讯录，或手动添加同事与客户联系电话。</p>
<p>3．点击联系人即可发起智能拨号，通话中可随时邀请更多成员加入电话会议。</p>
<p>4．在电话会议界面选择需要参会的人员，一键发起多人同时在线通话。</p>
<p>5．在通话或会议界面点击「管理成员」，可随时添加、移除参会人或结束会议。</p>
Good. Need perhaps "管理成员" quotes use Chinese corner brackets, acceptable. But perhaps in HTML, <p> content includes left/right angle? No, we used 「」 not < >.
Need perhaps "功能" section "主要能力模块及各自解决什么问题" Our item1 cloud contacts, item2 conference, item3 intelligent dial. Good.
Need perhaps "推荐理由" section "each item should specify concrete benefit" Good.
Could final p mention "推荐理由" and "功能" to tie together? It does.
Need perhaps "协作通信app" should be "协同通信app" all instances. We have correct.
Let's verify all h3 exact:
<h3>协同通信app功能</h3> yes.
<h3>协同通信app推荐理由</h3> yes.
<h3>协同通信app操作指南</h3> yes.
<h3>协同通信app测评</h3> yes.
Need maybe "第一个元素是一个 <p>" In our output first element is p. Good.
Need maybe "不允许有注释" no.
Let's decide final output with no blank lines? We'll output all tags each on own line; no blank lines. That is fine.
Potential issue: "应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片" no need to leave placeholders. Good.
Let's maybe include "中国电信" in final p? yes.
Need final p "全文不超过 200 字（含标点）" It's under. Good.
Let's think if "语音品质" original says "语音品质" maybe we should mention "通话音质" instead. Good.
Need perhaps "PSTN" should be uppercase. We use.
Need perhaps "app" in Chinese text lowercase okay.
Potential issue: "数字+全角句号．" Some might see "1．" as using "digit + fullwidth period" but the dot after number is "．" (fullwidth). Good.
Need perhaps "全文共 4～7 个 h3" We count 4. Good.
Need perhaps "非测评小节为 若干 个 <p>、每条要点须带序号" We have. Good.
One more thought: "各节独立" might mean "各节条数独立" but "全篇统一" might be "same sequence numbering across entire article"? Let's revisit with exact "各节独立" only appears in "每节要点条数以该小节下方【条数】为准（在 3～6 条之间且各节独立）" It says each section's points count independent, not "numbering independent". If we restart numbering, each section's numbering is independent too. If we continue, counts are still independent but numbering not. Which is more likely in "直接写入数据库的 HTML 正文片段" generated by a template? Usually all "H3-普通" section instructions: "用序号分条：每条单独成行，行首为「数字+全角句号．」（示例 1．2．3．），全篇保持同一格式；**本节须写 3 条**要点". This "本节须写 3 条" implies in this section, write 3 numbered lines. It doesn't mention previous numbering. It would be weird to start with 4 in a subsection if "本节须写 4 条" because "条" means list items, not digits. But if continuous, the second section's numbers would be 4,5,6,7; still 4 items. But then the example "1.2.3." in each "本条" instruction would not match the actual numbers in later sections. They say "示例 1．2．3．" not "从1开始". Could be example of format only. Hmm.
Let's search memory: This style is from a content generation prompt. They often require "每个 H3 下分条，条数如 3-6 条" with "每条单独成行，行首为 1." They expect each section's points numbered independently. Because otherwise a section with 5 points would be "1-5" if it's the first list; if there are multiple sections, continuous numbering is awkward and not usually used in web content. Also "全篇统一为同一种序号格式" means all sections use "数字+全角句号" rather than bullet points. I'm comfortable restarting.
Need perhaps "首段" p should not be numbered. We don't.
Potential issue: "推荐理由" could be written with "1．2．3．4．" but if we restart, okay. We'll do.
Let's think if "操作指南" section could be "5 个 <p>，每 <p> 一条要点" We have 5. Good.
Need maybe "测评" "一段短评，全文不超过200字" It's final p only under 200. Good.
Let's prepare final answer. But before final, let's examine if there is any contradiction: "允许的 HTML 标签仅有：<p>、<h3>。禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）。" It says "仅有 <p>、<h3>" but also "应用截图由系统自动插入" no img. Good.
Need perhaps "标题须与下列 {H3title} 完全一致" We have.
Need perhaps "正文片段" maybe no "h3" as "h3" without closing? We'll close.
Need perhaps "全文共 4～7 个 <h3>" yes.
Let's maybe add "首段" p more polished:
"协同通信app是中国电信推出的一款即时通话软件，集云通讯录、电话会议和智能拨号等通信能力于一体，让用户随时与同事、客户高效沟通。它支持多人同时在线通话，采用PSTN专用电话网络传输语音，通话清晰稳定，能够显著提升办公协作效率。"
This is a rewrite. Good.
Let's use this first p. It includes "协同通信app", "云通讯录、电话会议和智能拨号", "PSTN", "多人同时在线通话", "提升办公效率". Good.
Need maybe "原文首段" says "即时通话的软件" not "即时通话软件"; okay.
Let's ensure "集云通讯录、电话会议和智能拨号等通信能" original missing 
