Fail-closed baseline pairing with lower-memory retries

Release: InvarLock 0.3.4 - Required pairing evidence and chunked adapter snapshots

Highlights

• CI/Release baseline pairing now fails closed with strict parity checks.
• Report generation requires paired-windows evidence (non-perfect pairing is rejected).
• Chunked snapshot/restore and proof-pack workflow helpers reduce retry and long-run friction.

This release makes baseline pairing a checked contract instead of a convention. If a CI/release run says it is paired to a baseline, it now has to carry valid evaluation_windows evidence, and the system enforces dataset, tokenizer, and masking parity instead of letting ambiguous comparisons slip through.

Report generation is equally strict: paired_windows evidence is required, and non-perfect pairing is rejected. That gives reviewers a clearer answer to the most important question: when a report says it is paired, it really is paired.

On the practical side, chunked HF adapter snapshot/restore helps reduce peak memory during retries, and the new proof-pack workflow helpers (run_suite, scheduler/queue utilities, and model creation tooling) make longer evidence runs easier to operate without weakening the pairing rules.

For the immutable release record, read the tagged CHANGELOG.md for v0.3.4.