Inflection AI (direct)

TENG-2205: Direct Inflection AI API calls (Inflection 3 Pi / Productivity) called from customer code. Inflection has no admin or billing API — console-only. This connector only receives data if the customer's own code emits an OTel span or log record per chat call carrying the attributes below; an uninstrumented integration reports nothing, not zero. First-party API status is UNCLEAR and stated as such rather than guessed: developers.inflection.ai did not resolve (DNS NXDOMAIN, checked twice this pass) and inflection.ai's own site has no visible developer/API section — it is entirely focused on the Pi consumer product. The only independently confirmed access path this pass is via third-party resellers (OpenRouter lists "Inflection 3 Productivity" and "Inflection 3 Pi" through its own unified API), which is consistent with the prior research note that resellers, not Inflection itself, are the better-documented OpenAI-compatible surface. Do not assume a first-party Inflection endpoint exists or is OpenAI-compatible without re-confirming; if a customer is only reachable via a reseller, that reseller's own OTel/OpenAI-compatible wrapper is what actually instruments this call, not anything Inflection ships. There is no telara-observability SDK wrapper for Inflection (first-party or reseller). Instrumentation must be manual: hand-written OTel spans, or an OpenAI-compatible wrapper pointed at whatever base_url the customer is actually calling (first-party or reseller), emitting the gen_ai.* attributes below.