[Feature] 支持订阅通知的功能，订阅了该技能后，技能更新能通知使用者

[Youngho-w]

Problem

用户下载技能后，如果后续技能更新，没法及时感知

Proposed Solution

1、用户订阅了某个技能，后续技能更新后，会在通知中心提示
2、记录使用者下载的最新版本，当技能更新后，提示用户更新技能

Alternatives Considered

No response

Impact

No response

Contract Or SDK Impact

No response

[github-actions]

Issue Triage

• Route: triage/core
• Priority: priority/p1 (3.6/5)
• Effort: effort/l (4/5)
• Confidence: 3/5
• Risk: low
• Analysis Mode: rules-only

Why

• Open for 10 days; forced into an active lane before the 14-day closure SLA is missed.

Maintainer Brief

Summary: 用户下载技能后，如果后续技能更新，没法及时感知
Why core:

• Likely spans multiple modules or a public compatibility surface.
• The issue is important, but a maintainer still needs to tighten scope before implementation.
  Reproduction or operator path:
• 用户下载技能后，如果后续技能更新，没法及时感知
  Suspected areas:
• The closest owner-facing workflow module for the issue's reported failure path
• Any docs or help text that currently promise the affected behavior
  Risks to watch:
• Check for regressions in adjacent user-facing workflow paths before merging.
  Validation checklist:
• Validate the primary reported workflow end-to-end after the fix.

Next Action

• Hand the issue to a core maintainer and use a local programming agent for reproduction, scoping, and validation.

---

问题分流结果

• 路由: triage/core
• 优先级: priority/p1 (3.6/5)
• 修复投入: effort/l (4/5)
• 信息完整度: 3/5
• 风险: 低
• 分析模式: rules-only

原因

• 已打开 10 天，为避免超过 14 天仍未闭环，强制进入 active lane

维护者交接摘要

概要: 用户下载技能后，如果后续技能更新，没法及时感知
为何进入 core:

• 大概率跨多个模块或公共兼容面
• 问题本身重要，但仍需要 maintainer 先收敛范围再实施
  复现路径或操作路径:
• 用户下载技能后，如果后续技能更新，没法及时感知
  怀疑影响区域:
• 最接近该失败路径的 owner-facing 工作流模块
• 当前对外承诺该行为的文档或 help 文本
  重点风险:
• 合并前检查相邻用户路径是否出现回归
  验证清单:
• 修复后端到端验证主报告流程

下一步

• 交给 core maintainer，并结合本地编程Agent协助完成复现、收敛范围与验证闭环