refactor(hosts): declare scheduler backends - #627
Merged
evan-ak merged 2 commits intoAug 12, 2026
Merged
Conversation
Make each host's existing scheduling arrangement explicit so callers do not need to infer scheduler ownership from the OS invocation template. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Keep the scheduler metadata tests aligned with the repository formatter so CI can validate the behavior without rewriting the working tree. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
xnne-bot
changed the title
evan-ak
approved these changes
Aug 12, 2026
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
3 participants
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.
📝 Pull Request Summary
在
HostSpec中显式声明每个 host 当前使用的 scheduler backend。✅ What does this PR do?
schedule_backendmetadata：os、native、external。schedule_command仍是现有 Windowsschedulehelper 的唯一 capability gate。🤔 Why is this change needed?
此前需要通过
schedule_command是否存在来推测 host 的 scheduler arrangement，但该字段本身只描述 OS task 启动 headless agent 的 invocation template。显式 backend label 降低了理解每个 host 调度方式的认知门槛，也避免把“调度方式”与“OS invocation command”混为一谈。不涉及任何 scheduler 的迁移、注册、权限或运行行为变更。
Closes #624.
🔍 Type of Change
✅ PR Quality Checklist
feat:,fix:,docs:,memory base:)