Summary
The source-backed frontend and SGLang integration currently assume newer runtime symbols and method signatures than the shipped ai-dynamo-runtime==1.0.0 bindings expose.
Observed mismatches
- optional import surface such as AicPerfConfig
- RouterConfig / KvRouterConfig constructor kwargs drift
- WorkerMetricsPublisher.publish signature drift
- ModelRuntimeConfig fields only present in newer builds
- EngineShutdown import path drift
Why this matters
These mismatches block source-backed validation and make it hard to test runtime fixes in the RL360 harness without patching the source tree locally.
Desired outcome
Harden the Python frontend/SGLang integration to degrade gracefully when older runtime bindings are present instead of crashing at import or constructor time.
Summary
The source-backed frontend and SGLang integration currently assume newer runtime symbols and method signatures than the shipped ai-dynamo-runtime==1.0.0 bindings expose.
Observed mismatches
Why this matters
These mismatches block source-backed validation and make it hard to test runtime fixes in the RL360 harness without patching the source tree locally.
Desired outcome
Harden the Python frontend/SGLang integration to degrade gracefully when older runtime bindings are present instead of crashing at import or constructor time.