chore: Fix clippy warnings

[github-actions]

Automated clippy fixes applied by CI

[trunk-io]

😎 Merged successfully - details.

[phil-opp]

No issues found. This is a mechanical clippy cleanup with no behavior change: the seqlock_begin_if_even / seqlock_end bodies are wrapped in explicit unsafe {} blocks (edition-2024 unsafe_op_in_unsafe_fn) with the Release fences still executing unconditionally after the volatile writes; cur % 2 == 0 becomes cur.is_multiple_of(2); the two _register_host / GPU_BUF_SIZES nested if lets become let-chains guarding the same combined conditions; and the test swaps &[state.clone()] for std::slice::from_ref(&state), which still leaves state valid for the subsequent is_frozen() assertions.

---

🤖 This is a fully automated review by Claude (Claude Code). No human has vetted this comment; please treat it as advisory.

Generated by Claude Code

---

Generated by Claude Code

[github-actions]

@github-actions[bot] the Trunk merge queue failed for this PR.

See the Trunk merge-status comment for details.

Posted as a new comment so GitHub sends an email — Trunk's sticky comment is edited in place and won't trigger a notification.