build(lockfile): prove CWC lock sync preserves registry checksums #597

Finding

The CWC stack reconciliation had a real lockfile-integrity failure at exact commit 5a5a2201b341bdc8c62cc23f0a2f62fc4dbe9c36 (fix(longitudinal): synchronize CWC lock dependency). The intended delta was one analysis_engine dependency entry for psychometric_core, but the same commit also mutated registry checksums for unrelated packages (adler2, scopeguard, tracing-attributes, untrusted, wasi) and removed the final newline.

This is not a harmless formatting change: Cargo.lock registry checksums are package-integrity metadata and must not be hand-edited while reconciling a workspace dependency stanza. Four mutated values were no longer 64-hex digests; the wasi value remained 64 hex characters but no longer matched the inherited lock authority.

The exact inherited #416 lock authority is Cargo.lock@03f8de2ed0a0fb842d2022d411814e440df7cfb4 / blob 84367638e57c3542b85728b2d35c4cd2565d0c82.

Ordinary-forward repair

456f0a30f4dcaae10bc01bf902e83f75154d3dfb restores all five inherited registry checksums and the final newline while retaining the only intended lock delta: analysis_engine.dependencies += "psychometric_core".

No force push, destructive rebase, package-version change, checksum suppression, or dependency removal was used.

Acceptance

Keep this issue open until one unchanged successor head proves all of the following:

• compare against feat(analysis): bind template-copy identity refusals to an analysis-run profile #416 shows the Cargo.lock delta is exactly the one psychometric_core dependency entry;
• cargo metadata --locked and the applicable Rust test/rustdoc/Clippy gates succeed from the committed lockfile without rewriting it;
• package fetch/build verifies registry checksums normally;
• no unrelated package checksum or source/version entry changes;
• feat(analysis): bind CWC within/between slopes to an analysis-run profile #372 authority points to the exact repaired head and does not transfer predecessor GREEN evidence.

This is a build/reproducibility prerequisite only; it does not satisfy #501 scientific recovery or #596 permutation stability.