chore: bump renderers to 0.1.11; drop legacy RendererClient

[hallerite]

Summary

• Require renderers[multimodal]>=0.1.11: renderers 0.1.11 makes transformers optional, and verifiers both loads HF tokenizers (renderers.base.load_tokenizer / create_renderer) and renders image_url content that renderers resolves to PIL images at render time — so pin the extra that carries transformers + pillow.
• Refresh the lock file for renderers 0.1.11.
• Remove the legacy RendererClient and its tests: 0.1.11 removes the renderer pool APIs (RendererPool, create_renderer_pool, renderers.client._maybe_offload) that only the legacy client still used. The v1 train client has its own ElasticRendererPool and is unaffected. client_type="renderer" in a legacy ClientConfig now raises with a pointer to the v1 train client.

Verification

• uv lock --check
• uv run --locked --python 3.13 ty check verifiers
• uv run --locked ruff check / ruff format --check
• pytest collect passes with no import errors; verifiers, verifiers.legacy, verifiers.legacy.clients import cleanly

🤖 Generated with Claude Code

---

Note

Medium Risk
Breaking change for legacy configs using client_type="renderer"; v1 train path is unaffected but migrations are required for any remaining legacy renderer rollouts.

Overview
Upgrades the renderers dependency to renderers[multimodal]>=0.1.11 (lockfile refreshed) so transformers and pillow stay available for HF tokenizers and multimodal rendering after 0.1.11 made transformers optional.

Removes the legacy RendererClient (verifiers/legacy/clients/renderer_client.py) and its unit/e2e tests, because 0.1.11 dropped RendererPool, create_renderer_pool, and related APIs that only that client used. RendererClient is no longer exported from verifiers.legacy; client_type="renderer" in legacy resolve_client now raises ValueError directing callers to the v1 train client. Legacy docs drop RendererClient from the built-in clients table and note that prompt_attribution on trajectory tokens applied to renderer-backed rollouts removed with 0.1.11.

^{Reviewed by Cursor Bugbot for commit 9dc9356. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Drop legacy RendererClient and bump renderers to 0.1.11

• Removes the RendererClient implementation, its lazy import mapping, __all__ exports, and tests under tests/test_renderer_*.py
• resolve_client now raises ValueError for client_type='renderer', directing users to the verifiers.v1 train client
• Changes the dependency to renderers[multimodal]>=0.1.11 in pyproject.toml and updates the lockfile
• Updates docs/legacy/reference.md to remove the RendererClient row and note the removal
• Risk: any code importing verifiers.legacy.clients.RendererClient or calling resolve_client with client_type='renderer' will now raise AttributeError/ValueError instead of returning a client

^{Macroscope summarized 9dc9356.}

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — This PR intentionally removes the legacy RendererClient and changes renderer-configured legacy rollouts from executable to failing, while directing users to a different v1 client API. That breaking runtime and compatibility impact warrants human review despite the otherwise straightforward dependency and cleanup changes.

^{You can add or adjust custom eligibility rules. Learn more.}