Parent span scheduler.loop.prefill_batch_init records wall + the scheduler
thread's CPU at both existing close points (empty admission and normal
return); the CPU clock is only read when loop detail is enabled and sampled,
through the safe batch_telemetry.thread_cpu_ns() wrapper so a missing clock
degrades to 'not measured' instead of failing the scheduling path.
Fixed children, in call order:
schedule_batch_init, ready_to_load_host_cache, prepare_for_extend,
alloc_for_extend (+ prefix_device_indices attribute-only, sampling_batch_info),
evict_to_free_tokens, evict_for_alloc, prefill_stats (+ pending_tokens),
mixed_chunk_tail.
* prefill_stats wraps the whole assignment so _get_num_pending_tokens() is
included; mixed_chunk_tail only exists when that branch is taken.
* prefill-only shape counters (n_reqs/n_new/n_cached) are snapshotted before
mixed-chunk folding; a mixed batch additionally publishes decode_reqs and
merged totals under explicit *_merged_* names.
* eviction is timed at the call site (outside the allocator wrapper) so
rank-consensus waits are included, and covers base, SWA (x2), UnifiedSWA
(x3) and the extend Mamba reclaim through evict_for_alloc_observed().
Demand, shortfall and plan are separate counters; Mamba plan and realized
counts are both recorded (including zero).
All of it is gated by detail on a sampled loop.