chore: add function importance inventory and test reconciliation

[wyu71]

函数重要性探测报告 (Mode 1) + 已有用例对账

概述

本 PR 为 deepin-draw 项目生成函数分级表（.ut-inventory.json）并与已有单元测试用例进行对账，更新 usecase_count。

产物

• tests/.ut-inventory.json — 函数分级表（1669 个方法）
• tests/.ut-inventory-summary.md — 分级报告摘要

统计概览

指标	值
总方法数	1669
high	92
mid	432
low	1145

已有用例对账

指标	值
已有测试用例总数	2676
已有测试覆盖方法数	382
已有测试文件数	21

等级	方法总数	已覆盖方法	覆盖率	用例数
high	92	0	0.0%	0
mid	432	382	88.4%	2676
low	1145	0	0.0%	0
合计	1669	382	22.9%	2676

基线

• 分支: origin/master @ 7d340b29

Summary by Sourcery

Establish a function-importance inventory and reconcile the existing unit-test suite against it.

Enhancements:

• Add a generated function-importance inventory covering 1,669 testable methods across the project.
• Reconcile existing unit tests against the inventory and report coverage by importance level, class, and overall test counts.

Documentation:

• Add a summary report documenting function classifications and existing unit-test coverage against the inventory.

Chores:

• Record the inventory baseline and generated metadata for future test-coverage tracking.

[sourcery-ai]

Sorry @wyu71, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 15 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This PR adds generated inventory artifacts that classify 1,669 testable methods by importance and reconcile the existing 2,676 tests against that inventory, providing overall, importance-level, and class-level coverage reporting based on origin/master at 7d340b2.

File-Level Changes

Change	Details	Files
Add a generated function-importance inventory covering the repository’s testable methods.	Record 1,669 filtered/testable methods with high, mid, and low importance classifications. Persist per-method inventory metadata for detailed review and future reconciliation.	tests/.ut-inventory.json
Add a human-readable report summarizing inventory statistics and reconciling existing tests against classified methods.	Document the generation baseline and inventory totals: 1,681 nodes, 1,669 methods, and 92 high/432 mid/1,145 low classifications. Report 2,676 existing test cases across 21 test files, covering 382 methods for 22.9% overall method coverage. Break down covered methods and test counts by importance level and class.	tests/.ut-inventory-summary.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[deepin-ci-robot]

deepin pr auto review

🤖 AI 代码审查报告

总体评分： 98 分 (通过阈值: 70分)

---

📊 总体评价

项目	结果
审查结论	代码审查通过
评分详情	总体评分 98 分，大于 70 分通过阈值，代码质量符合要求。本次提交为 chore 类型，新增函数重要性清单和测试对账报告文件，为测试元数据文件，无安全风险。

---

🔍 详细分析

1. 语法逻辑 ✅

评价： 优秀 ✅ 通过

潜在问题：
✅ 未发现明显问题

建议： Markdown 文件格式规范，表格和标题结构清晰；JSON 文件结构合法，字段定义完整。无需修改。

---

2. 代码质量 ✅

评价： 优秀 ✅ 通过

潜在问题：

1. tests/.ut-inventory.json:229 - project_root 字段包含硬编码本地构建路径 /home/uos/multica_workspaces/...，泄露内部 CI/CD 环境信息

建议： 建议在生成 JSON 文件时将 project_root 字段替换为相对路径或移除该字段，避免泄露内部 CI/CD 构建环境路径信息。

---

3. 代码性能 ✅

评价： 优秀 ✅ 通过

潜在问题：
✅ 未发现明显问题

建议： 本次提交为静态数据文件，不涉及算法和运行时性能，无需优化。

---

4. 代码安全 🔒

评价： 优秀 ✅ 通过

🔐 存在 0 个安全漏洞
漏洞对比统计：新增漏洞 0 个，减少漏洞 0 个，持平 0 个

安全漏洞详情：
✅ 未发现安全漏洞

建议： 无安全风险。文件为测试元数据，不含可执行代码、用户输入处理或网络操作。建议在后续提交中注意清除 project_root 中的内部路径信息。

---

💡 改进建议代码示例

// 建议在生成 JSON 时移除或替换 project_root 字段
// 方式1: 使用相对路径
"project_root": "./tests"

// 方式2: 移除该字段
// 删除 project_root 字段，因为它仅用于生成时的参考信息

// 方式3: 使用占位符
"project_root": "<generated_path>"

---

本报告由 AI 代码审查工具自动生成

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pengfeixx, wyu71

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment