模型未返回最终正文（finish_reason=length），以下为推理过程摘录，可尝试提高 max_tokens 或改用多段生成。
我们需要理解用户请求。用户要求“你只输出一段可直接写入数据库的 HTML 正文片段。禁止 markdown 代码围栏、禁止任何解释或前言后记。允许的 HTML 标签仅有：<p>、<h3>。禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）。不要输出 <html><body> 等外壳，不要 script/style。”
We need generate HTML fragment exactly as specified. Need follow structure.
Important: First element is <p> based on "首段" template with {head}/{text}? They gave "首段" text: "请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。标题：多乐够级捕鱼版本；原文首段：多乐够级捕鱼版本下载是一款融合了经典够级玩法与捕鱼乐趣的休闲竞技游戏。玩家可以在游戏中体验刺激的捕鱼对战，同时享受够级牌局的策略乐趣。游戏画面精美，操作简单，支持多人实时在线对战，无论是单人闯关还是组"
Actually "首段" perhaps needs us to write original introduction paragraph containing app name. Need first <p> natural appear app name. It should mention "多乐够级捕鱼版本" naturally. We need produce an intro paragraph.
Then after first <p>, only h3 sections based on order. They say from random selected 3–6 non-evaluation subsections and prioritized original? Here we have all six non-evaluation subsections in order: 游戏介绍, 使用说明, 推荐理由, 魅力, 玩法, 操作指南, 测评. We need output all? Actually "小节顺序" lists all 7, including 测评. User says "然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）"
Hmm interesting: They say "已从词池随机抽 3～6 个非测评小节" but then provided all sections? Wait they list all sections with detailed tasks, including 游戏介绍, 使用说明, 推荐理由, 魅力, 玩法, 操作指南, 测评. That would be 6 non-evaluation + 测评 = 7 h3. But maybe according to their "各小节任务与已代入模板" they included every possible section, but "已从词池随机抽 3～6 个非测评小节" means need select? Yet the instruction says "顺序必须严格如下: ... 2) 然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）" It might imply the actual set of sections to output is determined by random subset, but since all six non-evaluation sections are listed maybe need output? However the parenthetical explains generated from random selection; "以下 '小节顺序' 游戏介绍 → 使用说明 → 推荐理由 → 魅力 → 玩法 → 操作指南 → 测评" likely is the list to choose subset. But then they provided detailed task for every section, including all. Need infer expected output length. They also state "全文共 4～7 个 h3" could include all 7. But earlier from word pool random 3-6 non测评 plus 测评 = 4-7 h3. So if all 6 non测评 are included, that's 7 h3, within 4-7. The order given includes all 6 and测评; maybe output all? Let's parse: "随后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）" Since "已从词池随机抽 3～6 个" suggests a random subset has been chosen but not visible? Yet in explicit sections all tasks included. "优先保留采集中有原文者" Here they say "本小节无对应采集原文，按原创..." for all. So no original. "若含「介绍」「简介」类关键词会固定排在首段后第一个 h3": we have 游戏介绍, so it first. Then remaining sections in order. They list "小节顺序" as all sections: Game intro, instructions, reasons, charm, gameplay, operation guide, review. The final fixed review. Could be that all six non-review sections were chosen (random 3-6 includes 6). Then output 7 h3. Given each section has specified number of <p>, this is longer but within allowed. Need do that? Let's consider constraints in "整体结构": The first <p>, then "only according to the following 'section order'" with "from word pool randomly drawn 3~6 non-evaluation sections" perhaps indicates some sections may be omitted. But the user provided sections explicitly with tasks for all, so perhaps the "random draw" was pre-executed and we should output all these sections? The phrase "已从词池随机抽 **3～6** 个非测评小节" says has been randomly drawn 3-6, but no indication which. They then list "【小节顺序】游戏介绍 → 使用说明 → 推荐理由 → 魅力 → 玩法 → 操作指南 → 测评" as full order not subset. It may be that we should output all listed subsections in order; random draw isn't our task. Also they include "全文共 4～7 个 <h3>" if all 7. So likely output all 7 h3.
But wait: User says "然后**仅按下列「小节顺序」**输出（已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）" This is complex. If we output all 6 non-review sections, we meet "仅按下列「小节顺序」" and "4-7 h3". Also if they wanted subset, "随机抽 3～6" could be interpreted as choose any? But they instruct no explanation, "each subsection task" all included. In a generated content system, they often provide all candidate sections with "word pool randomly selected 3-6" and expect model to select? Hmm.
Let's examine the exact "小节关键词「游戏介绍」：标题必须是 ... 随后 **4 个** <p> ... **本节固定 4 条**" etc. They didn't say "if chosen" for each. It appears each section is to be output as part of a template. The "小节顺序" is the list. We can output all seven. The final "测评" fixed. The phrase "全文共 4～7 个 h3" includes 7. If we output all, okay.
Need use only <p> and <h3>. No code fences. No explanations. Need ensure the first paragraph contains app name. Need write 3-6? Actually all sections: game introduction 4 p; use instructions 6 p; reasons 6 p; charm 3 p; gameplay 4 p; operation guide 3 p; review 1 p. Total <p> = 1 first +4+6+6+3+4+3+1 = 28. h3 = 7. That's lengthy but allowed? "全文共 4～7 个 <h3>" yes. Each section with 3-6 p. This could be within "可直接写入数据库" maybe okay.
Need ensure each non-review p has "序号分条", each line starts with "数字+英文句点+空格" (e.g., "1. "). Full text uses same format. Need decide numbering: Each section restarts numbering at 1? They say "每节要点条数 ... 全篇统一为同一种序号格式：用序号分条：每条单独成行，行首为「数字+英文句点+空格」（示例 1. 2. 3.），全篇保持同一格式". "每节要点条数" suggests within each section, number restarts at 1 presumably. "全篇统一为同一种序号格式" means use "1." style consistently, not necessarily continuous across sections. Need maybe restart at 1 per h3. Since each section has its own count, likely start at 1. We should not continue numbering across h3? If all sections are separate lists, restarting at 1 is natural. Need ensure no bullet or markdown. Each p contains one numbered point, with line break? User says "每条单独成行" in HTML p creates block. "每条单独成行，行首为..." So each <p> starts with "1. " etc. A <p> is a block; separate lines. We don't need <br>. Good.
Need produce first <p> as application intro: "多乐够级捕鱼版本是一款融合经典够级与捕鱼乐趣的休闲竞技游戏..." Need include app name. Since the app name includes "版本", maybe "多乐够级捕鱼版本" exactly. Can say "多乐够级捕鱼版本下载是一款..." Better not "下载" in name? Name given is "多乐够级捕鱼版本" not text. Need include "多乐够级捕鱼版本" in paragraph naturally. The first paragraph should be an original rewrite of original first paragraph; mention name, core fusion, features, online, single-player etc. Need not mention "下载" maybe "多乐够级捕鱼版本将经典够级牌局与捕鱼对战融为一体". Need include "支持多人实时在线对战，无论单人闯关还是组队..." The original sentence truncated: "无论是单人闯关还是组" maybe "组队" etc. We'll complete.
Need think about all sections:
Section 1: <h3>多乐够级捕鱼版本游戏介绍</h3>
Need 4 p with numbered points. Focus: type, themes, main gameplay, content. Each point one sentence <50 chars. Need not exactly 50 but okay. Need possibly use "多乐够级捕鱼版本" or "游戏" etc.
Potential points:
1. 多乐够级捕鱼版本是一款够级牌局与捕鱼玩法融合的休闲竞技手游。
2. 游戏以经典够级规则为基底，加入射击捕鱼的爽快对战体验。
3. 玩家既可享受牌桌谋略，也能在鱼群中体验实时战斗刺激。
4. 画面精美、上手简单，支持单人闯关与多人组队在线对战。
Need ensure "每条约50字内" maybe length okay. Check "多乐够级捕鱼版本是一款够级牌局与捕鱼玩法融合的休闲竞技手游。" 28 chars. Good.
Section 2: <h3>多乐够级捕鱼版本使用说明</h3>
6 p. Focus: installation/permissions, first use, settings, notes. Need write practical. Since no original, create plausible content:
1. 下载安装多乐够级捕鱼版本后，请根据引导完成基础资源加载与账号登录。
2. 首次进入可先体验新手教程，熟悉牌局和捕鱼两种模式的切换方式。
3. 在设置中可调节画质、音效和网络选项，低配设备建议开启流畅模式。
4. 游戏内金币与道具可通过对局获取，参与每日任务可领取额外奖励。
5. 在线对战需保持网络稳定，组队模式可邀请好友或系统自动匹配。
6. 如遇更新或卡顿，请检查版本号并前往官方渠道下载最新补丁。
Need ensure each point ~50. Good.
Section 3: <h3>多乐够级捕鱼版本推荐理由</h3>
6 p. Need "why download/try" tone, concrete. Potential:
1. 一次体验够级策略与捕鱼快感，适合喜欢休闲竞技的玩家尝试。
2. 实时多人对战让每一局都充满变数，重复游玩乐趣高。
3. 画面色彩明快，牌局与捕鱼场景切换自然，视觉体验轻松。
4. 操作逻辑简单，新手也能快速上手，老手可钻研高阶套路。
5. 单人闯关与组队模式兼顾，忙碌或闲暇都能找到合适节奏。
6. 内置任务和奖励体系丰富，零碎时间也能稳定获得成长。
Need perhaps "多乐够级捕鱼版本" included at least once? First p included app name. Recommendations can refer to "游戏" or "这款游戏" but perhaps okay. We can include maybe first point "多乐够级捕鱼版本将够级与捕鱼巧妙结合..." That might be good. But every point no need.
Section 4: <h3>多乐够级捕鱼版本魅力</h3>
3 p. Focus emotional, long-term play, atmosphere, social. Potential:
1. 够级牌局中的默契配合让人沉迷，捕鱼对战又持续带来爽快反馈。
2. 画面与音效营造轻松热闹的氛围，适合与好友一起消遣时光。
3. 实时社交对战让人既有团队归属感，又能感受到竞技的乐趣。
Need maybe each point slightly emotional.
Section 5: <h3>多乐够级捕鱼版本玩法</h3>
4 p. Need core mechanics, operation, growth/rhythm, loop. Potential:
1. 玩家可先进入够级牌局出牌抢科，再切换捕鱼炮台精准射击鱼群。
2. 捕鱼模式通过瞄准鱼群弱点赢取金币，金币可用于升级武器。
3. 够级模式需要与队友配合出牌，按出牌顺序和牌型计算局势。
4. 游戏以“对局—奖励—升级”循环驱动，持续解锁新场景与道具。
Need avoid "先后" maybe okay. Check "够级牌局出牌抢科" maybe too jargon but okay. "抢科" in够级 maybe "争科"? Actually "够级" has "科" (head? In够级, "头科、二科、" etc). But perhaps okay. Need not overdo.
Section 6: <h3>多乐够级捕鱼版本操作指南</h3>
3 p. Concrete steps interface. Potential:
1. 登录后点击主界面的“够级”或“捕鱼”按钮，即可进入对应玩法。
2. 捕鱼模式下长按炮台可调整方向，松开即可开火，连击可触发技能。
3. 够级模式中点击牌面选中手牌，再点“出牌”按钮完成操作。
Need "操作指南" can be 3. Good.
Section 7: <h3>多乐够级捕鱼版本测评</h3>
One <p> no numbering, <=200 Chinese chars, objective concise. Need include app name perhaps. Could be:
"多乐够级捕鱼版本巧妙地将够级的策略深度与捕鱼的即时反馈融为一体，整体体验轻松却不乏竞技感。画面明快、操作简单，多人对战的随机性与组队协作让重复可玩性明显提升。单人闯关和每日任务也提供了稳定的成长曲线。若你喜爱休闲竞技，又想偶尔动脑，这款游戏值得一试。"
Need count <200. Let's count roughly: 多乐够级捕鱼版本巧妙地将够级的策略深度与捕鱼的即时反馈融为一体，整体体验轻松却不乏竞技感。 (40) 画面明快、操作简单，多人对战的随机性与组队协作让重复可玩性明显提升。(30) 单人闯关和每日任务也提供了稳定的成长曲线。(22) 若你喜爱休闲竞技，又想偶尔动脑，这款游戏值得一试。(23) Total around 115. Good.
Need first paragraph: Need "首段" based on original, include name and content. Could be:
"多乐够级捕鱼版本是一款将经典够级玩法与捕鱼乐趣巧妙融合的休闲竞技游戏。玩家既能体验捕鱼对战的爽快刺激，也能享受够级牌局的策略博弈。画面精美、操作简单，支持多人实时在线对战；无论单人闯关还是组队开黑，都能找到适合自己的乐趣。"
Need "自然出现" yes. Good. But "组队开黑" maybe colloquial; could say "组队协作". Original truncated "组" maybe "组队" okay. Need perhaps include "下载" because original "多乐够级捕鱼版本下载是一款..."? But the app name doesn't include "下载"; in natural intro "多乐够级捕鱼版本是一款..." okay. Need "原文的表达主旨保持高关联" yes.
Now need think about "禁止输出 <img>" okay no. "允许的 HTML 标签仅有" use only p h3. No extra. "禁止 markdown code fences" no. "禁止任何解释或前言后记" no. Need output only HTML fragment. Good.
Need ensure every non-review <p> follows same numbering format. Do we need put "1." at beginning of every p? Yes. But "每条单独成行" means each p begins with number. No text before number. h3 headings no numbering. Good.
Potential issue: We have first <p> not numbered. That's correct per "第一个元素是一个 <p>". Non-evaluation sections only numbered.
Potential issue: Need "标题必须与 {H3title} 完全一致": Use exactly:
<h3>多乐够级捕鱼版本游戏介绍</h3>
<h3>多乐够级捕鱼版本使用说明</h3>
<h3>多乐够级捕鱼版本推荐理由</h3>
<h3>多乐够级捕鱼版本魅力</h3>
<h3>多乐够级捕鱼版本玩法</h3>
<h3>多乐够级捕鱼版本操作指南</h3>
<h3>多乐够级捕鱼版本测评</h3>
Need decide if "游戏介绍" first h3 after first p because contains "介绍" and is listed first. Yes.
Now let's examine if section count "4~7 h3" if output all 7. Good.
But wait: "已从词池随机抽 **3～6** 个非测评小节并**优先**保留采集中有原文者；若含「介绍」「简介」类关键词会**固定排在首段 <p> 之后的第一个 <h3>**，其余小节再按其下列顺序；末位固定测评，全文共 **4～7** 个 <h3>）" If "已从词池随机抽 3~6" then perhaps the output should not include all 6 because "随机抽 3~6" means choose 3 to 6 from list. But since "游戏介绍" must be first if included, and "测评" fixed. The "下列「小节顺序」" might just be the order for when selected. The user says "仅按下列「小节顺序」输出" meaning output selected subsections in that order. They didn't tell us which are selected except by all tasks? Hmm.
Let's consider context: This appears from a content generation system where "词池" has many subsections; the prompt might randomly select 3-6. But in this user prompt, they explicitly include "各小节任务与已代入模板" for 6 sections. That might have been generated from a random selection of all subsections? Wait "游戏介绍 → 使用说明 → 推荐理由 → 魅力 → 玩法 → 操作指南 → 测评" includes every possible? Maybe there are other sections not in prompt? But "已从词池随机抽 3～6" if result includes 6, then it's possible all six were selected. The phrase "优先保留采集中有原文者" note all "本小节无对应采集原文" so no original. Maybe "采集" refers to source article, and all sections no corresponding original. Fine.
If we output all six plus测评 = 7, that's exactly max. It should be acceptable. If they expected fewer, perhaps over length but still valid? They said "全文共 4～7" and all 7 valid. But maybe "随机抽 3~6" means output should only include 3-6 non-review sections. If we output 6 non-review, that's within 3-6. Great. All six = 6 non-review, okay. So all good.
Need ensure "首段 <p> 之后的第一个 <h3>" is game intro. Yes.
Need "末位固定测评" yes.
Need "由系统在生成后按小节顺序自动插入图片，模型无需处理图片" no img. okay.
Now, could there be an issue with "小节顺序" says "游戏介绍 → 使用说明 → 推荐理由 → 魅力 → 玩法 → 操作指南 → 测评". If all six non-review are selected, order exactly. Good.
Need write actual p content. Need each non-review point one sentence, <=50 chars? Need maybe all around 25-35. Good. But with Chinese punctuation. Let's carefully craft content to avoid "版本" weird.
Let's draft full HTML:
<p>多乐够级捕鱼版本是一款将经典够级玩法与捕鱼乐趣巧妙融合的休闲竞技游戏。玩家既能体验捕鱼对战的爽快刺激，也能享受够级牌局的策略博弈。画面精美、操作简单，支持多人实时在线对战；无论单人闯关还是组队协作，都能找到适合自己的乐趣。</p>
<h3>多乐够级捕鱼版本游戏介绍</h3>
<p>1. 多乐够级捕鱼版本将够级牌局与捕鱼射击融合为一款休闲竞技手游。</p>
<p>2. 游戏以经典够级规则为基底，加入炮台捕鱼的即时战斗体验。</p>
<p>3. 玩家既能在牌局中运筹帷幄，也能在鱼群中感受射击爽感。</p>
<p>4. 画面精美、上手轻快，支持单人闯关与多人组队在线对战。</p>
Need check first point maybe "版本将" awkward "版本将" if "多乐够级捕鱼版本将" means "version will"? Actually "版本" as app name okay. Use "多乐够级捕鱼版本是一款..." in first. For p1 "多乐够级捕鱼版本将够级牌局与捕鱼射击融合为一款休闲竞技手游。" Reads okay.
Need perhaps "够级牌局" repeated. fine.
Section 2:
<h3>多乐够级捕鱼版本使用说明</h3>
<p>1. 下载安装游戏后，请先完成基础资源验证并选择常用账号登录。</p>
<p>2. 首次进入建议体验新手引导，熟悉“够级”与“捕鱼”模式切换。</p>
<p>3. 在设置中可调整画质、音效与网络选项，低配设备选择流畅模式。</p>
<p>4. 金币和道具通过对局及每日任务获得，优先完成活跃度奖励。</p>
<p>5. 在线对战前请检查网络状态，组队模式支持邀请好友或自动匹配。</p>
<p>6. 若遇版本更新或闪退，请前往官方渠道下载最新安装包并重装。</p>
Need "下载安装游戏" maybe okay. "版本更新" if app name includes version? Fine. Use "多乐够级捕鱼版本" maybe not necessary but okay. Need no punctuation issue.
Section 3:
<h3>多乐够级捕鱼版本推荐理由</h3>
<p>1. 一份游戏同时满足够级牌友和捕鱼爱好者，玩法切换更耐玩。</p>
<p>2. 实时多人对战让对局充满变数，每次匹配都有新鲜感。</p>
<p>3. 画面色彩明快，场景切换流畅，长时间游玩的视觉压力小。</p>
<p>4. 操作门槛低，新手能快速开局，老玩家可钻研更深套路。</p>
<p>5. 单人闯关与组队模式兼有，零碎时间和整段娱乐都适合。</p>
<p>6. 每日任务和成长奖励丰富，不氪金也能获得稳定成长。</p>
Need "一份游戏" awkward; "一款游戏" better. "一款游戏同时满足..." good.
Section 4:
<h3>多乐够级捕鱼版本魅力</h3>
<p>1. 够级中的默契配合与捕鱼时的即时反馈相互交织，令人越玩越上瘾。</p>
<p>2. 轻松热闹的视听氛围让人放松，适合拉上好友一块消遣。</p>
<p>3. 实时社交对战带来团队归属感，也让每次赢牌或爆金更有成就感。</p>
Need "越玩越上瘾" maybe okay.
Section 5:
<h3>多乐够级捕鱼版本玩法</h3>
<p>1. 对局中可进入够级牌区组队出牌，再切至捕鱼场用炮台瞄准鱼群。</p>
<p>2. 捕鱼模式通过击中不同鱼种获取金币，金币可升级火炮威力。</p>
<p>3. 够级模式讲究队友配合与记牌算牌，按牌型与出牌顺序争胜。</p>
<p>4. 游戏以“对局—收益—升级”为主要循环，持续解锁新场景和道具。</p>
Need "够级模式" vs "够级牌区" okay. "按牌型与出牌顺序争胜" okay.
Section 6:
<h3>多乐够级捕鱼版本操作指南</h3>
<p>1. 登录后点击主界面的“够级”或“捕鱼”按钮，即可进入对应玩法。</p>
<p>2. 捕鱼模式下长按炮台调整方向，松开开火，连续命中可积攒技能。</p>
<p>3. 够级模式中点选手牌并点击“出牌”，即可按当前回合完成操作。</p>
Need maybe "操作指南" should include "具体步骤" enough.
Section 7:
<h3>多乐够级捕鱼版本测评</h3>
<p>多乐够级捕鱼版本巧妙融合够级策略与捕鱼快感，整体趣味轻松且具备竞技张力。画面明快，操作简单，多人实时对战和组队协作提高了重复可玩性。单人闯关与每日任务带来清晰成长路径。喜欢休闲竞技的玩家不妨一试。</p>
Need count <200. Good.
Need ensure no "script/style". yes.
Potential issue: "允许的 HTML 标签仅有 <p>、<h3>" We must not include newlines? Newlines are okay in HTML fragment. We can use line breaks between tags. No markdown code fences. Good.
Potential issue: "不要输出 <html><body> 等外壳" okay.
Need maybe "第一条 p" should be an application intro, not numbered. Good.
Now let's think if "全篇统一为同一种序号格式" could mean not restart? Suppose "全篇" numbering should be continuous across all sections? It says "每条单独成行，行首为「数字+英文句点+空格」（示例 1. 2. 3.），全篇保持同一格式" Not necessarily continuous. However if wanting to insert screenshots by system after sections, sections likely separate lists. If "全篇" means all numbered p, using "1." in every section is uniform. Good.
Need "每节要点条数" "本节须写 4 条" etc. So each section starts at 1.
Could there be "游戏介绍" section "4 p" but if there is "介绍" keyword it is first h3 after first p. We comply.
Need think about "测评" final p no numbering, one paragraph <=200 chars. No "1." in the p. "一段短评" yes. Maybe include "多乐够级捕鱼版本" exact. Good.
Let's perhaps refine content to be more "应用商店的介绍文案" for first p. The first p can be:
"多乐够级捕鱼版本是一款融合经典够级玩法与捕鱼乐趣的休闲竞技手游。它既保留了够级牌局的策略深度，又加入捕鱼对战的爽快反馈，画面精美、操作简单。游戏支持多人实时在线对战，无论单人闯关还是组队协作，都能让玩家享受轻松又刺激的竞技体验。"
This is okay. Need include "下载"? Original first line "多乐够级捕鱼版本下载是一款..." The app name maybe "多乐够级捕鱼版本下载" as search phrase? The "应用名称（须在首段 <p> 正文中自然出现）：多乐够级捕鱼版本" So should use exactly "多乐够级捕鱼版本" not "多乐够级捕鱼版本下载". Good.
Need have "画面精美，操作简单，支持多人实时在线对战" yes.
Need maybe "无论是单人闯关还是组队..." complete. good.
Let's decide final exact output:
<p>多乐够级捕鱼版本是一款融合经典够级玩法与捕鱼乐趣的休闲竞技手游。玩家既能体验捕鱼对战的爽快刺激，也能享受够级牌局的策略博弈。游戏画面精美、操作简单，支持多人实时在线对战；无论单人闯关还是组队协作，都能找到轻松又过瘾的竞技乐趣。</p>
Then all sections.
Let's ensure every p point ends with Chinese punctuation? It's okay.
Now, I should consider if "使用说明" with "6 p" might be too generic and not tied to original. The task says "本小节无对应采集原文，按原创H3-普通" so okay.
Need maybe "游戏介绍" section with "type positioning, theme worldview, main gameplay/content volume" We don't have "worldview"; "够级牌局与捕鱼" is thematic. Good.
Need maybe "推荐理由" "语气偏导购但具体" our points are specific enough.
Need maybe "魅力" "情感吸引力" okay.
Need maybe "操作指南" "具体步骤" okay.
Potential issue: "允许的 HTML 标签仅有：<p>、<h3>" We output line breaks outside tags. Does that count? No, text nodes with whitespace are okay. But "不是 HTML tag." Good.
Potential issue: "禁止输出 <img>（应用截图由系统在生成后按小节顺序自动插入，模型无需处理图片）" okay.
Need maybe "不可写 markdown 代码围栏" we won't.
Let's think if "测评" should not use "序号与分条" and "一段短评". Our paragraph no list. Need not be "不超过 200 字" yes.
Let's count "测评" p chars:
"多乐够级捕鱼版本巧妙融合够级策略与捕鱼快感，整体趣味轻松且具备竞技张力。画面明快，操作简单，多人实时对战和组队协作提高了重复可玩性。单人闯关与每日任务带来清晰成长路径。喜欢休闲竞技的玩家不妨一试。"
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? Actually punctuation and Chinese each count as one. It is 98 chars? Let's compute more accurately: phrase "多乐够级捕鱼版本" 8? "多乐" 2, "够级" 2 =4, "捕鱼"2=6, "版本"2=8. Yes. Then 巧妙融合够级策略与捕鱼快感 = 14? "巧妙"2 "融合"2=4 "够级"2=6 "策略"2=8 "与"1=9 "捕鱼"2=11 "快感"2=13? Wait let's count segment by segment:
多乐够级捕鱼版本 8
巧妙融合 4 => 12
够级策略 4 => 16
与 1 =>17
捕鱼快感 4 =>21
， =>22
整体趣味轻松且具备竞技张力 14? 整1体2趣3味4轻5松6且7具8备9竞10技11张12力13 =>13, plus comma =14? Let's just do approximate. It's well under 200 anyway. Good.
Need perhaps "第一段 p" should not be too long? No constraint.
Let's consider if there is "HTML 正文片段" and "可直接写入数据库" means maybe no whitespace? It's okay.
Need perhaps "标题 must be exactly with h3" no extra attributes. Yes.
Need "小节顺序" final includes "测评" fixed after operation guide. We comply.
Potential issue: "若含「介绍」「简介」类关键词会固定排在首段 <p> 之后的第一个 <h3>" Our first h3 game intro. Good.
Need maybe "游戏介绍" is "游戏介绍", not "多乐够级捕鱼版本游戏介绍" yes because H3title says exactly "多乐够级捕鱼版本游戏介绍". We use that.
Need perhaps "首段" text: "请参考{组合采集首段}/{原文首段}，现在需要对这段内容进行原创改写，内容必须包含游戏/软件名称，与原文的表达主旨保持高度关联与一致性。可以根据原文的内容进行内容重组，使其逻辑清晰、层次分明，更偏向于一个应用商店的介绍文案。标题：多乐够级捕鱼版本；原文首段：多乐够级捕鱼版本下载是一款融合了经典够级玩法与捕鱼乐趣的休闲竞技游戏。玩家可以在游戏中体验刺激的捕鱼对战，同时享受够级牌局的策略乐趣。游戏画面精美，操作简单，支持多人实时在线对战，无论是单人闯关还是组" The first paragraph should maybe "应用介绍" not just original. We do.
Need maybe "全文共 4～7 个 <h3>" We have 7. Good.
Let's verify all sections have correct number of p:
- After h3 game intro: 4 p.
- After h3 use: 6 p.
- After h3 recommend: 6 p.
- After h3 charm: 3 p.
- After h3 gameplay: 4 p.
- After h3 operation guide: 3 p.
- After h3 review: 1 p.
Total p non-first = 27? 4+6+6+3+4+3+1 = 27. plus first =28. Good.
Need perhaps "非测评小节为若干 p" "评测 only 1 p" okay.
Need perhaps "每条要点须带序号" for each non-review p. yes.
Need perhaps "全篇统一为同一种序号格式" We use "1. " with a period (English period) and space. Yes.
Need check no "1、2、3" Chinese enumeration. We're using "1. " exactly.
Potential issue: "数字+英文句点+空格" in Chinese text. We have "1. 多乐..." There is a space after period. Good.
Need perhaps "一条一句、每条约50字内" Some of our points are slightly over 50? Let's check. "多乐够级捕鱼版本将够级牌局与捕鱼射击融合为一款休闲竞技手游。" Count: 多乐够级捕鱼版本 (8) 将(1=9) 够级牌局(4=13) 与(1=14) 捕鱼射击(4=18) 融合为(3=21) 一款(2=23) 休闲竞技手游(6=29) 。 =>29. Good.
"游戏以经典够级规则为基底，加入炮台捕鱼的即时战斗体验。" Count: 游戏以经典够级规则为基底 (13?) 加入炮台捕鱼的即时战斗体验 (13) total 26. Good.
"玩家既能在牌局中运筹帷幄，也能在鱼群中感受射击爽感。" 28.
"画面精美、上手轻快，支持单人闯关与多人组队在线对战。" 27.
Use section:
1. " 应用信息
热门推荐
用户评论