[multi-lora] 3/n Tinker full stack: backend, frontend, and RL/SFT docs

docker/Dockerfile

@@ -165,10 +165,7 @@ RUN pip install "git+https://github.com/NVIDIA-NeMo/Emerging-Optimizers.git@v0.3
 RUN TMS_CUDA_MAJOR=$(python3 -c "import torch; print(torch.version.cuda.split('.')[0])") \
     pip install git+https://github.com/fzyzcjy/torch_memory_saver.git@f05a8754daf68238d54e4cf31cb3ba866684bbaf --no-cache-dir --force-reinstall
 RUN pip install "nvidia-modelopt[torch]>=0.37.0" --no-build-isolation
-# radixark/Megatron-Bridge#24 (TE 2.17 grouped-linear contract), merged to @bridge.
-# Pinned by SHA, not branch: buildkit caches this layer on the instruction text, so a
-# branch that moves leaves the old revision baked into the image with nothing to show it.
-RUN pip install git+https://github.com/radixark/Megatron-Bridge.git@7f0fb3456f8ffe47599b5fd167b454605d85f932 --no-deps --no-build-isolation
+RUN pip install git+https://github.com/radixark/Megatron-Bridge.git@bridge --no-deps --no-build-isolation
 RUN pip install megatron-energon --no-deps
 RUN pip install multi-storage-client --no-deps
 

docs/advanced/lora.md

@@ -300,32 +300,32 @@ its own Adam state and independently clocked scheduler. The trainer coalesces
 ready prompt-group slices or partial adapter batches and selectively upserts
 only changed adapters into SGLang.
 
-Set the slot capacity with `--multi-lora-n-adapters N`. A bounded run registers
-repeatable `--multi-lora-adapter NAME PATH` entries at startup; service mode can
-start with empty slots and register adapters through the controller HTTP API.
+Set the slot capacity with `--multi-lora-n-adapters N`. The operation backend
+starts as a long-running service with empty slots and registers adapters at
+runtime through the controller HTTP API.
 This path currently forces Megatron-Bridge LoRA and requires disaggregated NCCL
 broadcast, PP1, THD, Adam, and no train offload. Shared-outer expert adapters are
 unsupported, and MoE expert adapters cannot use FP8/FP4 experts.
 
 Native multi-LoRA is not implied by the native single-adapter work: both current
-`main` and the Tinker-oriented branch below still build multi-LoRA through
+`main` and the operation-backend branch below still build multi-LoRA through
 Megatron-Bridge. Native multi-LoRA is tracked separately in
 [issue #2141](https://github.com/radixark/miles/issues/2141).
 
-### Future Tinker-compatible operation backend
+### Multi-LoRA operation backend and Tinker compatibility
 
 [PR #2273](https://github.com/radixark/miles/pull/2273) is the active
-Tinker-oriented backend proposal. It changes ownership of the training loop:
+Multi-LoRA operation-backend proposal. It changes ownership of the training loop:
 instead of the server owning a dataset, reward function, and one-step schedule,
 clients submit explicit operations against a registered adapter. Its primary
-intended consumer is a Tinker-compatible training service rather than a generic
-server-owned dataset scheduler.
+consumer today is a Tinker-compatible protocol adapter, but the trainer-side
+operation contract is named independently from that client protocol.
 
 ```text
-Tinker-style client
-  | register + ordered operations
+Tinker client -> Tinker protocol/frontend adapter
+  | normalized register + ordered operations
   v
-controller / operation ledger
+MultiLoraOperationBackend / operation ledger
   | bind one fixed LoRA slot
   v
 Megatron-Bridge multi-LoRA trainer
@@ -335,6 +335,12 @@ Megatron-Bridge multi-LoRA trainer
 SGLang router + registration-scoped adapter identity
 ```
 
+The current concrete is `MultiLoraOperationBackend`, with
+`MultiLoraOperationBatchFn` and `MultiLoraParameterExecutor` handling adapter
+batching and slot execution. `Tinker` remains the wire/SDK compatibility name.
+A future full-parameter executor may reuse the normalized operation contract,
+but this PR does not implement or claim full-parameter training.
+
 The operation surface separates compute, optimization, and publication:
 
 | Operation | Contract |
@@ -349,7 +355,8 @@ are strictly serialized per registration, while idempotent retries, gap-buffered
 arrival, acknowledgements, and backpressure make execution retry-safe and
 order-safe. A registration-scoped serving identity prevents an old request from
 using a slot after that slot has been reassigned. Authenticated remote access is
-the responsibility of the future frontend, not the Ray operation API in #2273.
+provided by the stacked Tinker frontend in #2346; it is not part of the Ray
+operation API in #2273.
 
 The v1 scope in the PR is deliberately narrow: text-only synchronous training,
 one shared base model, shifted 1-D targets, `cross_entropy`, importance-sampling,
@@ -362,9 +369,10 @@ This backend is implemented in an open PR, not released on `main`; the PR
 reports H200 validation. PR #2273 provides the operation backend, but its v1
 training operations are still exposed through the controller's Ray API. The
 stacked [PR #2346](https://github.com/radixark/miles/pull/2346) adds a REST
-frontend compatible with the official `tinker==0.24.1` client; its GPU frontend
-E2E is still pending. If #2273 lands as proposed, it replaces the current
-dataset-driven driver.
+frontend compatible with the official `tinker==0.24.1` client. The stacked
+full system has passed both RL and pure-SFT 2xH200 acceptance; those results do
+not expand #2273 beyond its fixed-slot Multi-LoRA scope. If #2273 lands as
+proposed, it replaces the current dataset-driven driver.
 </Warning>
 
 ## Compatibility and limitations
@@ -404,5 +412,5 @@ dataset-driven driver.
 - `miles/rollout/session/core.py` attaches the single adapter to agentic session
   requests.
 - `miles/ray/multi_lora/`, `miles/rollout/multi_lora/`, and
-  `miles/backends/megatron_utils/multi_lora_*.py` implement the multi-adapter
+  `miles/backends/megatron_utils/api_backends/multi_lora/` implement the multi-adapter
   controller, routing, scheduling, optimization, and checkpoint path.

docs/docs.json

@@ -242,7 +242,7 @@
       "pages": [
        "examples/geo3k-vlm",
        "examples/geo3k-vlm/multi-turn",
-       "examples/multi-lora",
+       "examples/multi-lora-operations",
        "examples/on-policy-distillation",
        "examples/on-policy-distillation/qwen3-5-35b-selfdistill",
        "examples/ppo",