How much of the Bridge the generated Python SDK actually reaches.
THIS USED TO BE A TAUTOLOGY. The denominator was a hardcoded list of eight
paths sitting twenty lines below listPythonSdkEndpoints, which returned the
same eight — so coverage was 8/8 and could not be anything else, and
docs/SDK.md published it as "100% Bridge endpoint coverage".
The denominator now comes from the router (BRIDGE_MODEL_ROUTES), which is
where the answer lives. Measured against it the real figure is 7 of 11: the
SDK reaches neither batches, embeddings, images/generations nor
audio/speech. That number is allowed to be below 1, which is the whole
difference between a measurement and a slogan.
outsideModelRouter is the other direction: SDK endpoints the model router
does not match. That is NOT the same as "broken" — /bridge/telemetry lands
there and is served perfectly well by bridgeServer.ts, just not as a model
proxy. Naming it unroutable would have replaced one false claim with
another, in the opposite direction. What it is good for is catching an
endpoint that belongs to neither set, which is how a generated method that
404s would show up.
How much of the Bridge the generated Python SDK actually reaches.
THIS USED TO BE A TAUTOLOGY. The denominator was a hardcoded list of eight paths sitting twenty lines below
listPythonSdkEndpoints, which returned the same eight — socoveragewas 8/8 and could not be anything else, anddocs/SDK.mdpublished it as "100% Bridge endpoint coverage".The denominator now comes from the router (
BRIDGE_MODEL_ROUTES), which is where the answer lives. Measured against it the real figure is 7 of 11: the SDK reaches neitherbatches,embeddings,images/generationsnoraudio/speech. That number is allowed to be below 1, which is the whole difference between a measurement and a slogan.outsideModelRouteris the other direction: SDK endpoints the model router does not match. That is NOT the same as "broken" —/bridge/telemetrylands there and is served perfectly well bybridgeServer.ts, just not as a model proxy. Naming itunroutablewould have replaced one false claim with another, in the opposite direction. What it is good for is catching an endpoint that belongs to neither set, which is how a generated method that 404s would show up.