* feat(deepseek_v4): serve image input on the V4-Flash-Vision release
The block layout depends on where the image lands: lead pads align its first row token to
a 4-token compression stride, so the item hash carries the layout and two alignments never
share a radix key.
The block's tokens all carry one content pad id (the shared pad scheme); the sparse
attention reads its spans from batch.mm_spans, which the scheduler recovers from the flat
block ends its existing plan already reports.
* fix(mm): keep the shared mmprocessor signature and own the dsv4 offset in its apply
* fix(models): build dsv4 image spans in the model and start them at image_start
* fix(models): mount the dsv4 vision tower under visual and keep its weights unquantized
* fix(models): keep dsv4 image blocks whole across chunked prefill