chore: bump salt version to 1.0.6

[flyq]

Summary

Bumps the salt crate from 1.0.5 to 1.0.6 so downstream consumers can pick up the eight changes merged since the 1.0.5 bump (#138). Version-only change: salt/Cargo.toml:3 plus the matching Cargo.lock entry, regenerated with cargo update -w.

Changes since 1.0.5

• feat: add fallible StateUpdates::try_add and try_merge #149 feat: fallible StateUpdates::try_add and try_merge
• feat(mutation): domain-specific operator packs via universalmutator (#141) #143 feat(mutation): domain-specific operator packs via universalmutator (Domain-specific mutation operators via universalmutator (complementing cargo-mutants) #141)
• docs: add REVIEW.md #147 docs: add REVIEW.md
• fix(trie): isolate SHARED_COMMITTER init from the global rayon pool #148 fix(trie): isolate SHARED_COMMITTER init from the global rayon pool
• test(salt): remediate the full-run mutation baseline (issue #144) #145 test(salt): remediate the full-run mutation baseline (Full-crate mutation baseline: 54 survivors + 20 timeouts, triaged #144)
• fix(hasher): make the deterministic hasher endian-independent #142 fix(hasher): read bytes as little-endian in the deterministic hasher
• test(salt): add mutation testing coverage #140 test(salt): add mutation testing coverage
• perf(ipa): parallelize per-round G fold in IPA prover #139 perf(ipa): parallelize per-round G fold in IPA prover

Testing

No code change, so no new tests. cargo update -w regenerated the lock cleanly (2 files, 2 insertions, 2 deletions — same shape as #138 and #136); CI covers the build.

[github-actions]

Mutation testing - PASS

Nothing to test: no viable mutants were generated.

[github-actions]

Mutation testing - PASS

Nothing to test: no viable mutants were generated.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: b45a5a37f5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Use a breaking version for the new public error variant

When a downstream crate specifies a semver-compatible requirement such as salt = "1.0.5" and exhaustively matches the public SaltError enum, Cargo may upgrade it to 1.0.6, but compilation will then fail because this release adds SaltError::UnchainedTransition to an enum that is not marked #[non_exhaustive]. Publish these changes under a breaking version, or avoid extending the exhaustive public enum, so a nominally compatible patch update cannot break downstream builds.

Useful? React with 👍 / 👎.

[github-actions]

Performance Benchmark Comparison

Compared 5 benchmark(s) against the latest main baseline.

Detailed Comparison

Benchmark	Baseline Throughput (Kelem/s)	New Throughput (Kelem/s)	Change
update 10000 KVs/1 threads	73.27	75.71	+3.34%
update 10000 KVs/2 threads	140.50	139.86	-0.46%
update 10000 KVs/4 threads	258.14	258.86	+0.28%
update 10000 KVs/8 threads	433.01	436.26	+0.75%
update 10000 KVs/16 threads	580.17	581.50	+0.23%