变更摘要

本 PR 为文档更新，围绕混合容差中的 max_abs_error_limit 补充说明其 ULP 动态锚点的定义，并明确 ±inf 场景下比对收窄的规则，属于对既有容差判定语义的说明性澄清，不涉及接口、数据结构或运行逻辑调整。改动仅集中于单个文档文件，以少量新增与删改的说明文字表达上述规则。

主要改动

• 文档性质改动：本次仅修改文档内容，不涉及代码实现、配置项或对外接口的行为变化，目的是把既有容差规则表述得更明确。
• max_abs_error_limit 的 ULP 动态锚点定义：补充说明混合容差中 max_abs_error_limit 所对应的 ULP 动态锚点含义，使该阈值在不同量级下的取义更清晰。
• ±inf 比对收窄规则：明确正负无穷参与比对时的收窄处理规则，界定无穷值与其他取值比较时的容差适用方式。
• 实践适用性说明：描述中指出该规则已在长尾算子的实际使用中得到验证，为文档表述提供依据。

说明：本任务未提供该文件的具体补丁内容与文件名，以上总结仅依据 PR 标题、描述及变更统计得出，未对未给出的实现细节作推断。

Hi @dengguojie, welcome to submitting your first PR to opbase!

PR Merge Steps

1. CLA Signing

If the current PR label includes cann-cla/yes, it means you have signed the CLA and can proceed to the next step. If the label includes cann-cla/no, please sign the CLA first. If you have any questions, please refer to the FAQ.

2. CI Check

Please comment /compile to trigger the CI pipeline check. If the CI run is successful, the PR will be tagged with ci-pipeline-passed and you can proceed to the next step. If the CI run fails, the PR will be tagged with ci-pipeline-failed, please check the CI logs to fix the issues in the PR. If you have any questions, please refer to the FAQ.

3. Code Review

After CI passes, please refer to the PR Approval Progress and proactively @ the committers in the table to review the code. After approval, committers will comment /lgtm and /approve. Once the lgtm and approved labels are successfully added, the PR will be merged automatically.

🤖 本次改动均为数据 / 生成 / 二进制文件（如测试用例、锁文件、媒体资源），没有可审查的代码逻辑，已跳过 AI 代码审查。

CLA Signature Pass

dengguojie, thanks for your pull request. All authors of the commits have signed the CLA. 👍

Thanks for your pull-request.
The full list of commands accepted by me can be found at here.
You can get sig-info at here.
You can self-configure the PR merge rules for this repository. For more details, please refer to Here.
For more, you also can visit HICANN.

PR Approval Progress

✅ Congratulations! All modules have met the lgtm and approve requirements.

Module Approval Details

💡 Tip:

• Committer can comment /approve or /lgtm
• Commenting /approve implies both code review (lgtm) and intent to merge (approve)

/compile

/lgtm
/approve

@zhou-qilong

@songkai111

/approve

/lgtm
/approve

The following users do not have permission to comment /lgtm or /approve on any module in this PR:
/approve: 唐超
/lgtm: 唐超