Building the web image showed that `next build` failed.
- The console imported runtime values from the contracts entry point.
- Turbopack cannot follow the NodeNext `.js` imports inside that entry,
which also carries zod and every schema into the browser.
- Only `next dev` had ever run before, and the console used to import
types only.
The fix:
- The executor catalog moves to an entry without imports, exported as
@wishforge/contracts/providers. The console takes its values from
there.
- providerBaseUrl moves to its own module.
- A test keeps value imports of the entry point out of the console.
With the console's default budget of 50,000 tokens, every Codex run
stopped after one model request:
- The proxy reserves one token per request byte, and a Codex request is
already about 50 KB.
- The executor then reported a bare 429 as a provider failure.
The fix:
- A request the remaining budget cannot cover now puts the run into the
`budget` wait, with what it needs and what remains.
- The console defaults to 300,000 tokens and explains the reservation.
The run page also marked the stage a successful run ended in as not yet
done; it now shows it as complete.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>