Summary

PR #505 (policy: activate Clippy 1.94/1.95 ratchets) is the long-standing draft that promotes 8 planned Clippy lints to active in [workspace.lints.clippy]. The workspace MSRV is now 1.95 (v0.7.0), so the 1.94 and 1.95 ratchets are eligible. #505 is intentionally PARKED until v0.7.0 publishes; this issue tracks the prerequisites, merge plan, and acceptance criteria so the flip is clean once unblocked.

PR reference

• policy: activate Clippy 1.94/1.95 ratchets #505 — policy: activate Clippy 1.94/1.95 ratchets (draft, 8 lints to activate, +53/-50)
• Last commit on the branch: 40405a4 (2026-05-08) — predates the publish-recovery lane below.
• Branch: policy/clippy-rust-1.95-ratchets → main.

Lints to activate

Sourced from policy/clippy-lints.toml [[planned]] entries.

#505 also fixes resulting duration_suboptimal_units warnings by replacing Duration::from_secs(N*3600/86400) with from_hours / from_mins.

Prerequisites

• v0.7.0 published to crates.io.
• main CI green post-publish (publish-recovery lane xtask: fix PUBLISH_CRATES order so compat shims publish after their owners #565/ci: migrate release publish to shipper #566/ci: gitignore .shipper/ and pass --allow-dirty to shipper preflight #567/ci: pass --allow-dirty to shipper publish/resume too #568/fix: make internal test-helper deps path-only in workspace.dependencies #569/ci: revert publish workflow to cargo xtask publish (shipper#173 blocker) #570 already merged).
• policy: activate Clippy 1.94/1.95 ratchets #505 rebased against current main (last commit 2026-05-08 predates xtask: fix PUBLISH_CRATES order so compat shims publish after their owners #565/ci: migrate release publish to shipper #566/ci: gitignore .shipper/ and pass --allow-dirty to shipper preflight #567/ci: pass --allow-dirty to shipper publish/resume too #568/fix: make internal test-helper deps path-only in workspace.dependencies #569/ci: revert publish workflow to cargo xtask publish (shipper#173 blocker) #570 merged on 2026-05-11; rebase definitely required).
• cargo clippy --workspace --all-targets --all-features --locked -- -D warnings re-runs clean on the rebased PR.
• cargo xtask check-lint-policy passes on the rebased PR.

Merge plan

1. Confirm v0.7.0 is on crates.io and main CI is green.
2. Rebase policy: activate Clippy 1.94/1.95 ratchets #505 onto current main. Resolve any conflicts in Cargo.toml ([workspace.lints.clippy]) and policy/clippy-lints.toml.
3. Re-run rtk cargo xtask gate --check locally and re-confirm rtk cargo clippy --workspace --all-targets --all-features --locked -- -D warnings.
4. Push the rebased branch; verify the pr workflow run is green.
5. Mark policy: activate Clippy 1.94/1.95 ratchets #505 ready for review; merge once CI passes and review is complete.
6. After merge, verify on main that cargo xtask check-lint-policy reports the 8 lints as active in [[active_clippy]] (not [[planned]]).

Risks

• Adapter crates (uselesskey-jsonwebtoken, uselesskey-rustls, uselesskey-ring, uselesskey-rustcrypto, uselesskey-aws-lc-rs, uselesskey-tonic) may touch the same lint surfaces (raw-parts, casts, durations) and could trip the new lints in code that was clean on 2026-05-08 but has since changed.
• Workspace movement since 2026-05-08: the publish-recovery lane (xtask: fix PUBLISH_CRATES order so compat shims publish after their owners #565/ci: migrate release publish to shipper #566/fix: make internal test-helper deps path-only in workspace.dependencies #569/ci: revert publish workflow to cargo xtask publish (shipper#173 blocker) #570) touched workspace dependency wiring and CI; rebase conflicts most likely surface in Cargo.toml.
• Rust toolchain drift: a new stable Rust release between now and merge could surface additional findings under the activated lints (especially needless_type_cast and duration_suboptimal_units).

Acceptance criteria

• policy: activate Clippy 1.94/1.95 ratchets #505 merged to main.
• cargo xtask check-lint-policy reports 8 lints as active (with disallowed_fields and manual_pop_if remaining tracked separately).
• No CI regressions on main post-merge.
• Workspace [workspace.lints.clippy] block reflects the activated entries; policy/clippy-lints.toml [[planned]] reduced accordingly.

Not in scope

This is the tracking issue and plan. The actual lint flip happens in PR #505 once unblocked; this issue does not modify any source files. disallowed_fields (HELD) and manual_pop_if (DEFERRED to MSRV 1.96) remain out of scope for #505 and this issue.