[jeffdupont]

What

Upgrades the locked packages that pip-audit flags, split out of #176 so that PR stays CI-only. No pyproject.toml ranges changed; uv lock -P for each package:

Package	main	This PR
claude-agent-sdk	0.2.121	0.2.176
opentelemetry-api / -sdk / -proto / -exporter-otlp-proto-*	1.43.0	1.45.2
opentelemetry-semantic-conventions	0.64b0	0.66b2
opentelemetry-exporter-http-transport, -otlp-common	—	0.66b2 (new)
virtualenv	21.14.13	21.15.2
litellm	1.106.2	1.103.10
filelock	3.29.4	4.2.7
boto3 / botocore	1.43.101	1.43.123 (litellm 1.103.10 requires boto3>=1.43.117)

brotlicffi was also in the uv lock -P set; main already has the fixed 1.2.1.0, so it does not change.

The lock also records the workspace members' 1.0.0 versions; main's lock still lists the pre-1.0 versions, so uv lock --check fails on main.

Changes the upgrades need:

• Claude Agents handler: claude-agent-sdk added four ClaudeAgentOptions fields (resume_session_at, resume_drops_turn, forward_subagent_text, verbatim_prompts). None is a model or run setting, so all four go on the excluded list and a config cannot set them. verbatim_prompts matters most: it decides whether prompt text can make Claude Code read host files, which is the application's call.
• Lifecycle test: OpenTelemetry 1.45 logs a malformed OTEL_EXPORTER_OTLP_TIMEOUT and falls back to its default instead of raising, so the failed-telemetry test now makes _setup_telemetry raise directly. The BYOC comment in lifecycle.py drops the same example.

Why litellm goes back to 1.103.10

filelock 3.29.4 has 9 advisories (GHSA-fq56-3cx3-fjxp and others), all fixed only in 4.x, and litellm 1.106.x requires filelock<4. litellm patches several release lines in parallel: 1.103.10 is from 2026-10-27, newer than the 1.106.2 locked on main (2026-10-21), and it does not pin filelock. So the lock uses uv lock -P litellm==1.103.10 -P filelock.

This only changes what CI and local development install. The published litellm>=1.83.0 floor in packages/litellm-messages/pyproject.toml is unchanged, so users still resolve litellm themselves.

Verified locally

• ruff check, ruff format --check, mypy packages/*/src: clean.
• pytest: 3851 passed, 18 skipped.
• uv lock --check and the API report check: clean.
• make audit (from chore(ci): add dependency audit and Dependabot #176) on this lock: no known vulnerabilities.

🤖 Generated with Claude Code

---

Note

Overview
This PR refreshes uv.lock for packages pip-audit flagged: claude-agent-sdk (0.2.121 → 0.2.176), OpenTelemetry (1.43 → 1.45.2, plus new OTLP helper packages), filelock (4.x), boto3/botocore, and virtualenv. litellm is intentionally locked to 1.103.10 (below 1.106.x) so filelock 4.x can ship without litellm’s filelock<4 pin; published litellm>=1.83.0 floors in pyproject are unchanged.

Claude Agents adds four new ClaudeAgentOptions fields from the SDK upgrade to _CLAUDE_AGENT_OPTIONS_EXCLUDED_KEYS (resume_session_at, resume_drops_turn, forward_subagent_text, verbatim_prompts) so remote config cannot drive session resume, subagent streaming, or @path / slash-command expansion on the host.

Lifecycle tests no longer rely on a malformed OTEL_EXPORTER_OTLP_TIMEOUT to fail telemetry setup (OTel 1.45 logs and defaults instead); they patch _setup_telemetry to raise. A related BYOC comment in lifecycle.py is trimmed to match.

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