Twenty more const uint16_t* casts over borrowed safetensors bytes remain after the six that landed

Row: -

Owed by .agents/specs/unaligned-safetensors-consumers.md under ## Owed.

What was measured

Repairing the three consumers named in #2540 and #2558 exposed a fourth of the same shape on the very next sanitizer run (#2578, WeightF32), because -fno-sanitize-recover=all stops the binary at the first report and each repair only reveals the next site.

A grep over src/ at aedad724c finds 20 further occurrences of the identical shape -- a const uint16_t* formed over an OwnedTensor's borrowed bytes:

grep -rn "reinterpret_cast<const uint16_t\*>([A-Za-z_.]*bytes\.data())" src/

What was NOT measured, and why this is filed rather than fixed

Whether each of those sites is actually reached with an ODD base is unmeasured. BorrowStTensorBytes only borrows when direct upload is on and the tensor is a whole-range view, and a checkpoint whose header length happens to be even puts every tensor on an even address. So this list is a population of the SHAPE, not a list of confirmed findings, and turning it into findings needs a run per model rather than a grep.

Fixing 20 sites across ten model files is also not the unit of work #2540 and #2558 describe, and each one wants the model's own suite green beside it.

Fix shape

Identical to the six that landed: a byte cursor plus vt::LoadUnaligned<uint16_t> (include/vt/unaligned.h), which at -O2 compiles to the same load. Do NOT gate the borrow instead: .agents/specs/unaligned-safetensors-consumers.md records the measurement showing a producer-side alignment refusal switches direct upload off for every tensor in roughly half of all checkpoints.

A checker that refuses this shape outright would be the durable answer, and #627 already proposed one for the loader half of the class.

Start with .agents/specs/unaligned-safetensors-consumers.md and run the provided grep over src/ to review the 20 sites in the ten listed model files. Check each consumer's model-specific suite and sanitizer coverage before applying the established unaligned-load approach. Done means all listed borrowed-byte casts are addressed and the relevant model suites remain green.