Module session 

Session shapes: the capture identity and the deriver’s projection.

The split the wire draws is kept here rather than flattened: identity is ingest-written and lives at the top of SessionItem, while everything folded from the span layer at derive time lives under rollup. Flattening them would blur which layer owns a field, and “why is this empty?” has two very different answers depending on the side it fell on.

Structs

ModelUsage

One model’s contribution to a session in the API: how many llm calls ran on it and what they spent.

SessionDetailResponse

The response for GET /v1/sessions/:id: the session record alone.

SessionItem

The per-session shape: capture identity at the top level, the deriver- owned projection nested under rollup.

SessionListResponse

The response envelope for GET /v1/sessions.

SessionRollup

The deriver-owned session projection — status, title, counts, and spend, all folded from the span layer at derive time.

SessionTracesResponse

The composite session view on the span model.

SessionUpdateRequest

The PATCH /v1/sessions/{id} body.

SessionUsage

The session’s total token/cost spend, folded from the span layer.

TreeTask

One task folded from the session’s TaskCreate/TaskUpdate calls.