Hi @jbgriesner, the migration is mechanically correct across all 14 files and the motivation is solid: one fewer external dependency, aligned with the standard library since Rust 1.80.

Two things needed before merge:

1. std::sync::LazyLock stabilized in Rust 1.80 (July 2024). Please add rust-version = "1.80" to Cargo.toml so anyone on an older toolchain gets a clear error instead of a cryptic compile failure.

2. CI shows 0/0 checks. Could you check why the workflow isn't triggering? We need cargo fmt --all && cargo clippy --all-targets && cargo test to pass before merge.

Minor note: next_cmd.rs and playwright_cmd.rs keep the statics inside function bodies. This is valid Rust but inconsistent with every other module in the codebase after this PR. Worth moving to module level for uniformity, though it's not a blocker.

Hey @jbgriesner, heads up: PR #349 (TOML filter DSL) uses lazy_static\! in src/toml_filter.rs. If your LazyLock migration merges first, we'll switch to LazyLock directly — cleaner result. No action needed from you, just FYI.

2. CI shows 0/0 checks. Could you check why the workflow isn't triggering? We need cargo fmt --all && cargo clippy --all-targets && cargo test to pass before merge.

The 0/0 CI checks are a GitHub limitation with fork PRs: workflows run from the fork's own .github/workflows/ directory, not from the upstream repo. Since my fork doesn't replicate the upstream CI setup, no checks trigger automatically.

I've verified locally that all three gates pass: cargo fmt --all && cargo clippy --all-targets && cargo test
430 tests pass, no clippy errors.