[Backlog Discovery] feat(backlog): scheduled-workflow-health-guardrails

[bestony]

[Backlog Discovery]

• Requirement title: 为定时工作流增加健康守护与延迟/停用检测
• Priority: P2
• Requirement file: backlog/20260220222057-scheduled-workflow-health-guardrails.md
• Dedupe key: scheduled-workflow-health-guardrails
• Source run: https://github.com/bestony/self/actions/runs/22243391455

[gemini-code-assist]

Summary of Changes

Hello @bestony, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

本拉取请求引入了一个新的需求文档，旨在提升 GitHub Actions 定时工作流的可靠性和可观测性。通过识别并解决定时任务可能面临的延迟或意外停用问题，确保关键自动化流程能够持续稳定运行，并提供及时的问题发现与恢复机制。

Highlights

• 新增需求文档: 增加了关于为定时工作流提供健康守护和延迟/停用检测的需求文档。
• 解决痛点: 旨在解决 GitHub Actions 定时任务可能出现的排队延迟或因长期无活动被自动停用，导致关键自动化静默停止的问题。
• 解决方案假设: 提出了通过新增通用 preflight 脚本来检测异常、创建/更新 issue 并记录健康状态的解决方案。

Changelog

• backlog/20260220222057-scheduled-workflow-health-guardrails.md
  • 新增了关于为定时工作流增加健康守护与延迟/停用检测的需求文档。

Activity

• 目前没有记录到任何活动。

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

[Reviewer Workflow]
Reviewer: Product Manager

• Acceptance criteria are not fully testable because “延迟” and “阈值” are undefined (no concrete minutes/hours or comparison logic). Suggest adding explicit thresholds (e.g., max schedule delay, max time since last success) and how they’re computed.
• Scope is unclear on which scheduled workflows are covered (all schedules vs. critical ones like backlog-discovery). Suggest listing in-scope workflows and any exclusions to avoid over-alerting.
• Alerting/output behavior is underspecified (issue creation/update rules, dedupe key, escalation when issue already exists). Suggest defining how issues are created/updated and when to close or suppress them to prevent noise.

[gemini-code-assist]

Code Review

本次变更通过 backlog-discovery 工作流新增了一份需求文档，用于为定时工作流增加健康状况守护功能。这份文档结构清晰，内容详实，明确了需求背景、目标用户、核心场景和验收标准。

我发现文档中“需求摘要”和“用户问题”部分的内容完全重复。为了提高文档的清晰度和价值，我建议对“用户问题”部分进行重写，将其分解为更具体的用户痛点。这有助于更好地阐明问题，为后续的设计和开发提供更明确的指引。

总体而言，这是一次不错的自动化需求发现实践，我的建议旨在进一步提升文档质量。

[github-actions]

[Backlog Discovery]
Reviewer: Product Manager

• Acceptance criteria are not fully testable: “issue or notify” and “状态文件” lack a defined channel/location, and threshold units/cadence are unspecified, making success ambiguous. Suggest explicitly define the notification mechanism (issue only vs other), the storage location/format for the status file, and threshold units (e.g., minutes/hours) with default values.
• The requirement relies on “recent successful run time” but doesn’t specify the source of truth (GitHub API, artifacts, or persisted state), which affects feasibility and data retention. Suggest naming the authoritative data source and any retention/permission constraints to keep implementation scope clear.

[github-actions]

[Backlog Discovery]
Reviewer: Product Manager

需求价值评估

• 是否有价值: 有价值
• 优先级: P2
• Reviewer 视角结论: 对自驱动系统核心定时流程的可观测性补齐，能降低静默停摆风险，值得进入中优先级待办。

价值点

• 直接解决 schedule 延迟或自动停用导致的“无人感知中断”，保障 backlog-discovery 等关键自动化持续运行。
• 通过健康守护与告警缩短发现与恢复时间，减少人工排查成本。
• 为维护者提供可配置阈值与恢复指引，提升自治迭代的稳定性与可预期性。

风险与建议

• 风险: 仅基于“上次成功时间+阈值”可能产生误报；建议明确延迟判定口径并加入容错区间。
• 建议: 明确告警触达方式与去重策略（issue 更新频率/关闭条件），避免噪声降低响应意愿。

[bestony]

风险: 仅基于“上次成功时间+阈值”可能产生误报；建议明确延迟判定口径并加入容错区间。
建议: 明确告警触达方式与去重策略（issue 更新频率/关闭条件），避免噪声降低响应意愿。

[github-actions]

[Product Designer]

@bestony 当前需求分析中存在待确认问题，请在本 Issue 回复：

1. 延迟判定口径：以“最近成功”还是“最近触发”作为主判断，容错区间默认值是多少？

来源文档：plans/64-scheduled-workflow-health-guardrails.md

[github-actions]

[Product Designer]

@bestony 当前尚未满足 Ready For Review 条件，请补充以下信息后再回复：

1. 计划文档的“待确认问题”仍有未清空条目。

参考文档：plans/64-scheduled-workflow-health-guardrails.md