Summary
The SGLang handler base should expose the engine control routes needed for external weight synchronization.
Problem
External rollout and training integrations rely on a control-plane contract for:
- initializing weight update groups
- destroying weight update groups
- updating weights
- checking weight version
The handler base does not expose the full route set needed for that contract.
Impact
Trainer-side external weight synchronization cannot complete against the worker control surface without local patching.
Desired behavior
Register the full engine route set needed for external weight updates and weight-version checks.
Scope
This is a source-tree issue in the SGLang handler base route registration.
Validation target
A deployed worker should expose the engine routes required to initialize weight updates, perform them, and query version state through the standard control surface.
Summary
The SGLang handler base should expose the engine control routes needed for external weight synchronization.
Problem
External rollout and training integrations rely on a control-plane contract for:
The handler base does not expose the full route set needed for that contract.
Impact
Trainer-side external weight synchronization cannot complete against the worker control surface without local patching.
Desired behavior
Register the full engine route set needed for external weight updates and weight-version checks.
Scope
This is a source-tree issue in the SGLang handler base route registration.
Validation target
A deployed worker should expose the engine routes required to initialize weight updates, perform them, and query version state through the standard control surface.