Entire

Short answer: yes, but not yet — wait until 2409 is merged and deployed.

Here's the dependency that matters:

The live worker reads each repo's runner configs from that repo's main via the GitHub API. Today it only knows the .entire/runners/v2/ path.
This repo (entireio/cli) currently has its 7 configs in .entire/runners/v2/ and is actively running trail evals.
PR 2409 is OPEN, not merged (and therefore not deployed). The backward-compatible fallback (prefer .entire/runners/, fall back to v2/) isn't live yet.

So if you move the configs up now, the deployed worker won't find them at the new path and won't fall back → cli's trail evals break in the gap.

The safe sequence (which is exactly what 2409's own "Follow-ups" note describes):

Merge 2409 and let it deploy to the worker.
Then move cli's configs .entire/runners/v2/*.json → .entire/runners/*.json.
After that lands, remove the old-path fallback in entire.io.

Want me to prepare the file move on a branch now so it's ready to merge the moment 2409 deploys? I'd hold off on actually opening/merging it until the deploy is confirmed.

Done. Branch evjan/move-runner-configs is ready, not pushed, not a PR.

What's on it:

git mv of all 7 configs .entire/runners/v2/*.json → .entire/runners/*.json (100% renames, no content changes).
No other repo references to runners/v2 exist, so nothing else to touch.
Commit message includes a DO NOT MERGE until 2409 is deployed warning.

Status check: PR 2409 is still OPEN. When it merges and deploys, push this branch and open the PR.

Want me to push it now (as a draft) or leave it purely local until 2409 lands?