fix(workflows): expose call capacity in sandbox usage - #94
Merged
Conversation
Merged
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.
问题
Workflow V2 的 host 已经把
controller.capacity()放进usageSnapshot().limits,Skill 和模型提示也要求脚本使用usage().limits.callsRemaining做动态 fan-out;但 sandbox child 在重建usage()返回值时只复制了 token/cost/agents 字段,静默丢弃了limits。真实 run
wf_815de99b4a45因此在 Discovery 完成后失败:修复
limits四个 Runtime facts;deepFreeze,模型脚本不能篡改容量;验证
bun run check✅git diff --check✅这是
0.4.0发布阻塞修复;不包含 Issue #93 的 child transcript UI 改动。