变更摘要

本 PR 为“8 月社区任务——Ascend 950PR SpMV 算子开发”新增团队设计文档（仅文档变更，1 个文件、新增 286 行、无删除），不提交算子源码。文档路径为 04_tasks/01_community-task-2026/tasklist/08-SPMV/fffjjjlll1005/docs/design.md，核心内容围绕 SpMV 算子的接口约定、Host/Kernel 分层、数据流与验收标准展开，并明确本 PR 不构成 IT 验收或上游源码合入的完成标志。

主要改动

• 新增设计文档: 在 04_tasks/01_community-task-2026/tasklist/08-SPMV/fffjjjlll1005/docs/design.md 新增约 286 行设计文档，定义公共三阶段 API 与 arch35 Host/Kernel 分层设计。
• 数据流与数据布局合同: 文档规定了 N/T 两种数据流、workspace 生命周期、类型与确定性要求，以及 CSR 三数组和一维 X/Y 的正元素 stride 合同。
• 测试与性能验收标准: 文档写入测试与性能标准，并附 Ascend 950PR / CANN 9.1.0 实测证据（200/200 公共 API 精度、stride 5/5、生命周期/确定性 7/7、13 个必需 affected ops 测试、P1~P4 三轮 12/12、56/56 泛化性能覆盖，TARGET_ACCEPTANCE=PASS），同时如实标注 PERFORMANCE_DIAGNOSTICS=BLOCKED 及外部流程未关闭的状态。
• 交付范围声明: 明确本 PR 仅提交设计文档，不提交算子实现代码，也不代表 IT 验收或验收后的上游源码 PR 已经完成。

Hi @fffjjjlll1005, welcome to submitting your first PR to cann-ops-competitions!

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.

/approve

The MR can not be merged, because of CodeReview discussion not resolved

If you want to solve this problem, you can click here to do it in the FAQs.