8303b38e passed `resolved_name` to _quant_signature from record_vram_delta,
which has no such variable. The NameError was swallowed by an enclosing try,
so measured_vram_gb persisted and the signature beside it never did. Verified
live 2026-10-29: after a real load, measured_quant_sig was None and the
invalidation fired zero times.

Scope was checked at the READING site and assumed at the writing one. They are
different functions.

The deeper fault was hashing the model name at all. The two sites do not have
the same name to hand -- the reader has a resolved path, the writer only a
config key -- so even bound, they could hash different values and every
comparison would be a mismatch, discarding every measurement. The signature is
stored on one model's own entry, so identity is already implied: it now hashes
only precision, load_in_4bit/8bit and component_quantization.

That also drops pipeline_cache's cache version from the hash, which would have
invalidated every measurement on an unrelated cache bump.

A test now walks both call sites and asserts each binds what it passes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZozi1Ehk96NG1WesgC