[d-tietjen]

All-feature publishing resolves chacha20 0.10.1 through object_store → rand. Upstream withdrew that release for undefined behavior in its SSE2 RNG/legacy backend. Upgrade only its lockfile version/checksum to the compatible fixed 0.10.2 patch and refresh the generated inventory.

Upstream fix and yank rationale.

Validation at fc27e45:

• Registry readback confirms 0.10.2 is not yanked; parsed lockfile comparison proves every other package record unchanged.
• Strict native workspace all-target/all-feature Clippy and workspace all-feature tests completed with genuine reaped zero exits: 646 reported successes, zero failures and 18 ignored tests. Three enabled real GPU smoke cases passed; eight disabled GPU benchmark functions have no measurement credit. Filesystem object-overflow integrations are included.
• A paired isolated Miri probe uses the same rand 0.10.2 caller and forced SSE2 backend. Locked 0.10.1 reproduces the unsupported SSE4.1 call as Undefined Behavior and exits 1; locked 0.10.2 completes 64 RNG outputs and exits 0. Complete logs and genuine wait/reap receipts are retained. Miri uses a separate task-private nightly toolchain; production checks use Rust 1.93.
• The canonical package checker passed on a clean standalone checkout of this exact commit, including all binary and four consumer configurations. All three retained archives identify fc27e45 without a dirty flag.
• All hosted Rust, hygiene and Docker CI checks passed.

The earlier QEMU attempt did not reproduce the bug despite reporting missing SSE4.1 and has no regression credit. The initial probe build inherited the parent workspace and failed. Both attempts remain retained. Miri provides a scoped interpreter regression, not physical SSE2 hardware or benchmark qualification.

Targets PR 32, which prepares the 0.9.1 packages for PR 30. Main integration, registry publication and production benchmark qualification remain pending.

Issue: EDEN-2426

Final composed release validation

The canonical scripts/proof-gate.sh release also passes on exact source fc27e450ae2abb6c66ec464733fbd41ce63fedb1, with genuine zero direct-child exit/reap and the explicit completion marker. Rust 1.93.1 used four jobs, disabled incremental compilation and disabled dev debug information; debug assertions retained their default. Earlier missing-tool and disk-floor attempts remain failed. Fresh HWM driver build/tests (35 passed) and six native synthetic transport fault subprocess cases also pass. No operating admission, benchmark execution or performance qualification is claimed.

Integration status

This correction is included in PR30 through feature-branch merge 1c15b0af51708185a047fdf9d94a5bee31a2af7b. Final-head Rust, hygiene and Docker CI passed. Closing this separate follow-up because its exact source commit is already incorporated in the parent candidate; the parent PR remains open, and main has not been merged.