[Backlog Discovery] feat(backlog): evidence-snapshot-archival-for-backlog-research

[bestony]

[Backlog Discovery]

• Requirement title: 为需求发现证据加入快照归档与可追溯引用
• Priority: P2
• Requirement file: backlog/20260221073932-evidence-snapshot-archival-for-backlog-research.md
• Dedupe key: evidence-snapshot-archival-for-backlog-research
• Source run: https://github.com/bestony/self/actions/runs/22252887858

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[github-actions]

[Backlog Discovery]
Reviewer: Product Manager

• Acceptance criteria #3 uses “明显内容漂移” without a measurable detection rule, so it’s not testable and risks inconsistent behavior; define an objective drift signal (e.g., snapshot hash delta over N% text change or title+summary mismatch) and how it will be evaluated.
• Acceptance criteria #2 allows snapshots in “artifacts 或仓库受控目录” without choosing one or specifying selection rules, which can cause inconsistent retention and access; specify the default storage location and when/why the alternative is used.

[github-actions]

[Reviewer Workflow]
Reviewer: Product Manager

需求价值评估

• 是否有价值: 有价值
• 优先级: P2
• Reviewer 视角结论: 该需求可提升需求证据的可追溯性与长期可信度，符合 P2 优先级的流程可靠性改进。

价值点

• 减少外部证据链接失效或内容漂移导致的需求复核失败，提高评审可验证性
• 为仓库维护者与评审者提供稳定证据副本，降低后续审计与复盘成本
• 强化自动化需求发现流程的可信度，避免因证据不可追溯影响决策

风险与建议

• 证据快照的存储成本与合规风险未明确，建议在方案中定义保留策略与范围边界
• 快照最小内容、引用格式与触发时机需要更清晰定义，以便后续可执行拆解