Release 0.9.4

[github-actions]

Release readiness review (v0.9.3 -> TARGET 10e5ad3)

This is a release readiness report done by $final-release-review skill.

Diff

v0.9.3...10e5ad3

Release call:

🟢 GREEN LIGHT TO SHIP Patch-level change with targeted tests and docs updates; no concrete blockers identified.

Scope summary:

• 12 files changed (+1121/-341); key areas touched: tracing payload sanitization (src/agents/tracing/processors.py), trace processor tests, docs (including translated), version bump in pyproject.toml and uv.lock.

Risk assessment (ordered by impact):

1. Tracing usage payload reshaping

   • Risk: 🟡 MODERATE. Usage details are now moved under usage.details for OpenAI trace ingest; if any downstream consumer relied on top-level input_tokens_details/output_tokens_details, they will no longer appear in the ingested payload.
   • Evidence: BackendSpanExporter._sanitize_for_openai_tracing_api now calls _sanitize_generation_usage_for_openai_tracing_api and moves unsupported usage keys into a details sub-dict; tests updated accordingly. Commit: 02e8b03d.
   • Files: src/agents/tracing/processors.py, tests/test_trace_processor.py
   • Action: Run uv run pytest -k trace_processor and confirm all trace sanitization tests pass (expect updated details shape).

2. Usage dropped when required token counts are invalid

   • Risk: 🟢 LOW. If input_tokens/output_tokens are non-finite or missing, usage is removed entirely for trace ingest; this is stricter than before and could reduce telemetry for malformed inputs.
   • Evidence: New _is_finite_json_number and usage-drop behavior when token counts are invalid in processors.py; new tests explicitly verify drop behavior.
   • Files: src/agents/tracing/processors.py, tests/test_trace_processor.py
   • Action: Validate sample trace ingestion with a known-good payload that includes valid input_tokens/output_tokens to ensure usage is preserved.

Notes:

• BASE tag determined locally via git tag -l 'v*' --sort=-v:refname | head -n1 → v0.9.3.
• TARGET set to current HEAD 10e5ad3ee98208ff61a3f0a8d2a2af6d7ee013b6.
• Local verification stack not run here; assume CI runs $code-change-verification per repository policy.