feat(api): update API spec from langfuse/langfuse b19a2f5

[langfuse-bot]

Greptile Summary

Updates the generated API client from the latest upstream specification.

• Adds session_id filtering to synchronous and asynchronous observation-list requests.
• Documents semantic-root filtering for metrics and evaluation rules.
• Updates blob-storage, comment-author, SCIM password, and score endpoint documentation.

Confidence Score: 5/5

The PR appears safe to merge because the runtime-affecting observation filter is wired consistently across sync, async, public, and raw clients.

No concrete blocking or non-blocking defect remains; the new filter is keyword-only and correctly serialized, while the other changes are documentation updates that preserve existing generated-client behavior.

_{Reviews (1): Last reviewed commit: "feat(api): update API spec from langfuse..." | Re-trigger Greptile}

Context used:

• Knowledge Base — API Client (langfuse/api/)

[github-actions]

@claude review

[claude]

LGTM — mechanical, auto-generated SDK update mirroring an upstream API spec change.

Extended reasoning...

Overview

This is a Fern auto-generated update to the Python API client mirroring an upstream API spec change (langfuse/langfuse@b19a2f5). The changes span 16 files but are almost entirely docstring/documentation updates: clarified wording on exportSource defaults for blob storage integrations, a new isRootObservation dimension documented in the metrics API docstrings, removal of a stale "deprecated" notice on the scores v2 endpoints, clarified SCIM password field semantics, comment authorUserId behavior, and added boolean operator documentation across the EvaluationRuleFilter_* docstrings (the EvaluationRuleFilter_Boolean type already existed in code; this just documents it consistently elsewhere).

The one functional change is the addition of an optional session_id parameter to ObservationsClient.get_many / raw_client.get_many, threaded through to the sessionId query param exactly the way the existing user_id parameter is handled. This is a straightforward, mechanical addition with no new logic branches.

Security risks

None. There is no new authentication, authorization, crypto, or input-handling logic — parameters are passed straight through to httpx_client.request params/json dicts exactly as existing sibling parameters are, and docstrings do not affect runtime behavior.

Level of scrutiny

Low. This is auto-generated client code (comment at top of every file: "auto-generated by Fern from our API Definition") that mirrors a server-side spec change already merged upstream. The pattern (add optional query param, update docs) is well established elsewhere in this file and repo, with no ambiguous design decisions for a human to weigh in on.

Other factors

No CODEOWNERS-sensitive paths are touched, and there's no prior review history on this PR. The bug-hunting pass found no issues, consistent with the low-risk nature of the diff.