chore(governance): increase idle community discovery cadence#240
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Increase registered-source community discovery from once every 24 hours to once every 2 hours, with at most 1 hour of lateness, while preserving normal development as the higher-priority path.
The coordinator contract now selects community discovery only after recovery, intake, resumable PR/CI/post-merge work, roadmap decomposition, and executable issues are exhausted. A due scan that is blocked remains pending until the next truly idle tick. Daily global dogfood keeps its existing 24-hour cadence and 6-hour lateness behavior.
Reviewer Test Plan
qrun validate-contractandqrun verifypass and that the durable scheduler records the next due time without rewriting the ledger.Validation
中文说明
将仅限注册来源的社区发现频率从每 24 小时提高到每 2 小时,最大延迟 1 小时;只有在 lease、PR/CI/post-merge、用户 intake/promotion、待激活工作、agent-ready Issue 和 roadmap 拆解均为空时才允许执行。被正常开发阻塞的到期扫描会保持 pending,等下一个真正空闲 tick 再运行。
Fixes #219