[27Bslash6]

What

Moves Cargo.lock from cachekit-core 0.7.1 to 0.7.2 with cargo update -p cachekit-core --precise 0.7.2. Cargo.toml is unchanged: "0.7" already admits 0.7.2, and so does cachekit-rs 0.11.1's requirement.

Lock entries that moved:

Entry	Before	After
cachekit-core	0.7.1 (9bc8d8f4…)	0.7.2 (10167217…)
lz4_flex 0.12.2	depends on twox-hash	no dependencies (core 0.7.2 no longer enables lz4_flex's frame feature)
twox-hash 2.1.4	present	removed

Nothing else moved. One cachekit-core resolves, for both the direct dependency and cachekit-rs (cargo tree -i cachekit-core --target all), which deny.toml's deny-multiple-versions also enforces.

Effect on ck

None on what ck runs or writes. ck stores through cachekit-rs's EncryptionLayer, which seals the plaintext with core's native encrypt_aes_gcm and never goes through ByteStorage or LZ4. 0.7.2's changes are LZ4-side (the native encoder, the literals-only block below 64 B) and a wasm32-only AES-GCM seal; native encrypt_aes_gcm and derive_domain_key are unchanged. ck does store payloads under 64 B (the 16-byte failure marker, and an envelope of 8 bytes plus short stdout), but they are sealed uncompressed, so the sub-64 B change does not reach them. what_ck_writes_the_frozen_format_reads passes on 0.7.2 and pins that: every size it writes, from a 9-byte envelope up, opens as plain nonce ‖ AES-GCM(envelope).

This repo has no instruction-count harness, so there is no A/B table here. The paths ck uses are the ones cachekit-rs measures.

Checks (local, as CI runs them)

• cargo fmt --all -- --check: pass
• cargo clippy --locked --all-targets -- -D warnings: pass
• cargo deny check: advisories ok, bans ok, licenses ok, sources ok
• cargo metadata --locked: pass; no path dependencies outside the workspace
• cargo test --locked: lib 22 passed, readme 1, run 45, saas 17; bench 1 ignored (run below); 0 failed
• cargo build --locked --release, then the admin-API greps on the source and the binary: no match
• cargo test --locked --release --test bench -- --ignored: hit-path budget passes
• cargo +1.91 check --locked --all-targets (rust-version 1.91, the msrv job): pass. cachekit-core 0.7.2 declares rust-version = "1.91", matching this crate's.

No docs change: README and the docs here cite no cachekit-core version, compression behaviour or benchmark numbers.

Closes LAB-11012

[27Bslash6]

@coderabbitai review

[27Bslash6]

@kody start-review