…d throw on exhaust

Replaces the prior lenientBool default-false approach which silently
masked bu-2-0's tendency to emit undefined for `is_correct` and
`verdict` boolean fields. Defaulting to false hid the model bug from
operators and left the orchestrator unable to distinguish "model
emitted false" from "model emitted nothing".

Now: when SimpleJudgeSchema or JudgeSchema fails parse, we send the
prettified zod errors back to the LLM and retry up to 2 times,
matching PR webllm#34's pattern for action-emission retries. If retries
exhaust, surface the failure on the run's final ActionResult so
harbor's failure_reason picks it up — `_run_simple_judge` marks the
run as failed with a `[Judge schema invalid: ...]` note;
`_judge_trace` synthesizes a verdict=false judgement with the
schema error in `failure_reason`. Adds JudgeSchemaInvalidError
(src/exceptions.ts) for the internal throw.

A first-attempt shape check (any judge-related key present) preserves
the prior graceful-skip path when the LLM returns a non-judge JSON
shape entirely (e.g. an agent-step JSON in mocked tests), so we don't
regress component tests that wire one mock LLM for both agent and
judge calls.

This pairs strict zod with feedback-driven self-correction (per
reference_zod_pydantic_parity.md) instead of papering over the model
bug with a default. Adds test/agent-judge-schema-retry.test.ts
covering: (1) bu-2-0 missing-is_correct retry-then-recover, (2)
retries exhaust → run marked failed, (3) network errors stay
swallowed, (4) JudgeSchema verdict-missing exhaustion path, (5)
verdict self-correction on retry.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…d throw on exhaust

Replaces the prior lenientBool default-false approach which silently
masked bu-2-0's tendency to emit undefined for `is_correct` and
`verdict` boolean fields. Defaulting to false hid the model bug from
operators and left the orchestrator unable to distinguish "model
emitted false" from "model emitted nothing".

Now: when SimpleJudgeSchema or JudgeSchema fails parse, we send the
prettified zod errors back to the LLM and retry up to 2 times,
matching PR webllm#34's pattern for action-emission retries. If retries
exhaust, surface the failure on the run's final ActionResult so
harbor's failure_reason picks it up — `_run_simple_judge` marks the
run as failed with a `[Judge schema invalid: ...]` note;
`_judge_trace` synthesizes a verdict=false judgement with the
schema error in `failure_reason`. Adds JudgeSchemaInvalidError
(src/exceptions.ts) for the internal throw.

A first-attempt shape check (any judge-related key present) preserves
the prior graceful-skip path when the LLM returns a non-judge JSON
shape entirely (e.g. an agent-step JSON in mocked tests), so we don't
regress component tests that wire one mock LLM for both agent and
judge calls.

This pairs strict zod with feedback-driven self-correction (per
reference_zod_pydantic_parity.md) instead of papering over the model
bug with a default. Adds test/agent-judge-schema-retry.test.ts
covering: (1) bu-2-0 missing-is_correct retry-then-recover, (2)
retries exhaust → run marked failed, (3) network errors stay
swallowed, (4) JudgeSchema verdict-missing exhaustion path, (5)
verdict self-correction on retry.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

…arity)

Empirical observation: bu-2-0 (browser-use cloud LLM) occasionally emits
`{input_text: {index: true, text: "..."}}` (boolean) where the schema expects
an integer. python upstream silently coerces `True -> 1` / `False -> 0` via
pydantic's default lax mode. zod (TS) hard-rejects with
`expected number, received boolean`, the agent retries with the same broken
output, and bails at max_failures. observed bail mode in production for every
auth0-style form fill (daytona, zeroentropy, kernel, browserbase).

This patch ports the lax-coercion behavior to TS at the validation boundary.
A `lenientInt(min)` helper preprocesses booleans into numbers before
delegating to `z.number().int().min(min)`. Same shape for `lenientNumber()`
covering `num_pages` / `pages` floats. Helper is applied only to
LLM-emitted index/element-index/page-count fields where pydantic's silent
coercion is documented behavior. Fields where bool->0/1 would be
semantically wrong (timeout, delay, max_results, coordinate_x/y) are left
strict to avoid masking a different model bug.

This is a graceful-degradation patch, not a fix to the model. bu-2-0 should
not emit booleans for integer fields. With this patch the agent now
progresses + relies on existing retry-feedback (PR webllm#34) to self-correct on
bad index choice rather than looping to max_failures.

Helpers + per-schema regression coverage in
`test/coerce-boolean-to-int.test.ts` (23 tests).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…arity)

Empirical observation: bu-2-0 (browser-use cloud LLM) occasionally emits
`{input_text: {index: true, text: "..."}}` (boolean) where the schema expects
an integer. python upstream silently coerces `True -> 1` / `False -> 0` via
pydantic's default lax mode. zod (TS) hard-rejects with
`expected number, received boolean`, the agent retries with the same broken
output, and bails at max_failures. observed bail mode in production for every
auth0-style form fill (daytona, zeroentropy, kernel, browserbase).

This patch ports the lax-coercion behavior to TS at the validation boundary.
A `lenientInt(min)` helper preprocesses booleans into numbers before
delegating to `z.number().int().min(min)`. Same shape for `lenientNumber()`
covering `num_pages` / `pages` floats. Helper is applied only to
LLM-emitted index/element-index/page-count fields where pydantic's silent
coercion is documented behavior. Fields where bool->0/1 would be
semantically wrong (timeout, delay, max_results, coordinate_x/y) are left
strict to avoid masking a different model bug.

This is a graceful-degradation patch, not a fix to the model. bu-2-0 should
not emit booleans for integer fields. With this patch the agent now
progresses + relies on existing retry-feedback (PR webllm#34) to self-correct on
bad index choice rather than looping to max_failures.

Helpers + per-schema regression coverage in
`test/coerce-boolean-to-int.test.ts` (23 tests).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…arity)

Empirical observation: bu-2-0 (browser-use cloud LLM) occasionally emits
`{input_text: {index: true, text: "..."}}` (boolean) where the schema expects
an integer. python upstream silently coerces `True -> 1` / `False -> 0` via
pydantic's default lax mode. zod (TS) hard-rejects with
`expected number, received boolean`, the agent retries with the same broken
output, and bails at max_failures. observed bail mode in production for every
auth0-style form fill (daytona, zeroentropy, kernel, browserbase).

This patch ports the lax-coercion behavior to TS at the validation boundary.
A `lenientInt(min)` helper preprocesses booleans into numbers before
delegating to `z.number().int().min(min)`. Same shape for `lenientNumber()`
covering `num_pages` / `pages` floats. Helper is applied only to
LLM-emitted index/element-index/page-count fields where pydantic's silent
coercion is documented behavior. Fields where bool->0/1 would be
semantically wrong (timeout, delay, max_results, coordinate_x/y) are left
strict to avoid masking a different model bug.

This is a graceful-degradation patch, not a fix to the model. bu-2-0 should
not emit booleans for integer fields. With this patch the agent now
progresses + relies on existing retry-feedback (PR webllm#34) to self-correct on
bad index choice rather than looping to max_failures.

Helpers + per-schema regression coverage in
`test/coerce-boolean-to-int.test.ts` (23 tests).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>