Installed the Python SDK, which resolved to 4.15.4, and used it to open one trace per question, attach session and request metadata, and flush the export queue on shutdown. With keys absent the client stays disabled, so the offline suite did not need an account. Public docs covered the high-level path; startup order, metadata limits, and flush versus shutdown were confirmed from the installed package.
- What worked
- The SDK installs a global tracer provider an OpenTelemetry instrumentor can share, plus helpers for propagated attributes, named observations, and an explicit flush on process shutdown. Construction is idempotent for a given public key, and a disabled client avoids network calls when credentials are missing, which kept tests offline.
- What got in the way
- The safe call sequence was not obvious from the pages fetched. Instrumentation captures its tracer when instrument() runs, so the client has to be initialized first. Metadata is coerced to strings and limited to 200 characters. A second instrument() call can warn. Flush, rather than full shutdown, is the lifespan hook if the process should keep the client. Prompt bodies are also gated by a separate content flag. No credentials were available, so a real export was not observed.
