You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge pr2-add-vero into pr3-harness-bench to end the vero/src divergence
Both branches had accumulated real vero/src work the other lacked -- 12 commits
here (wandb URL repair, optimizer-trial harbor flags, model preflight, transient
infra classification) against 5 on pr2 (opencode step limit, litellm base-url
alias, outer Modal app naming, terminal budget status, backend in the eval plan).
The stacked-PR assumption that vero/ lives only on pr2 had quietly stopped
holding, and the cost was concrete: benchmark runs launch from this worktree, so
three fixes committed on pr2 were simply absent at run time. It cost a wasted
mini-swe-agent attempt and a gaia run launched without the step limit it needed.
Merging rather than rebasing: PR #57 is already merged into this branch, so
replaying commits over it would rewrite merged history for no benefit, and a merge
resolves the overlap once instead of per-commit.
Three conflicts, all where both sides edited the same lines:
- The run command gained both sets of appended flags. The derived Modal app name
now defers to an explicit app_name from *either* source, since a build can
declare one in optimizer_harbor_args just as a caller can pass one on the
command line, and appending ours after the build's would have silently won on
harbor's last-value-per-key rule.
- Three config stubs needed both `optimizer_harbor_args` and `name`; they were
written before the other side's field existed.
- Three assertions expecting `_opencode_gateway_args` to return nothing are now
wrong by design: the step limit is unconditional, so a bare model name and a
gateway-less task both still get it. Dropped those and kept every other test
from both sides.
453 passed, 5 skipped.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
0 commit comments