Repository navigation
v1.3.1
Hotfix: curve refit now works with mirror/HF copies of the weights
v1.3.0 bound the experimental curve refit to exact SHA-256 hashes of the fitted files. In practice the adapter file on Hugging Face (and various mirrors) has different bytes than the fitted copy — same weights, different file — so download_if_missing users and manual mirror downloads got curve refit disabled: no fit matches.
v1.3.1 replaces the all-or-nothing check with tiered matching:
- Exact files → fit applies silently (unchanged)
- Byte-different copies of the fitted base or adapter (HF downloads, mirrors, repacks — same filename, different bytes) → fit applies best-effort with a one-line console warning. The recipe (strength 1, default gate/sigmas) is always validated from your actual files.
- Unknown checkpoints / modified MODEL → backbone-only fallback, and the warning now prints the actual file hashes, so support just needs your log — no PowerShell required.
- A ModelSampling node placed before ApplyHyperFlow is now whitelisted (previously blocked the refit with "requires an unmodified checkpoint"); any other pre-patching node still blocks it.
- A corrupt fit file no longer blocks the others.
Verified end-to-end against the real checkpoints: all seven scenarios (exact / HF-copy adapter / mirror base / renamed / ModelSampling / foreign prepatch / strength override) behave as intended, and the 88-test suite passes.
If you got the fallback warning on v1.3.0: update to v1.3.1 and re-run — the refit will apply (with a "best-effort" warning if your file bytes differ from the fitted ones).