BUG preserve_key_order still method not found

**Describe the bug** Half a year later, I still cannot `cargo install qsv -...`. **To Reproduce** Steps to reproduce the behavior: 1. `cargo install qsv --locked --features feature_capable` **Expected behavior** It should produce a `qsv` binary. **Screenshots/Backtrace/Sample Data** ```text Compiling qsv v16.1.0 error[E0599]: no method named `preserve_key_order` found for struct `Json2Csv` in the current scope --> /home/home/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/qsv-16.1.0/src/cmd/json.rs:330:14 | 329 | / Json2Csv::new(flattener) 330 | | .preserve_key_order(true) | | -^^^^^^^^^^^^^^^^^^ method not found in `Json2Csv` | |_____________| | For more information about this error, try `rustc --explain E0599`. error: could not compile `qsv` (bin "qsv") due to 1 previous error error: failed to compile `qsv v16.1.0`, intermediate artifacts can be found at `/tmp/cargo-installohKHyA`. To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path. ``` **Desktop (please complete the following information):** - OS: Ubuntu 25.10 - qsv v16.1.0 **Additional context** You [said](https://github.com/dathere/qsv/issues/2819#issuecomment-3102267604): > If its not merged, I may ultimately make a renamed fork and publish it on crates.io as I've done with other unmaintained crates like dynfmt, docopt, vader_sentiment_analysis, etc. It's still not merged after so long, and that dependency is the one thing holding `cargo install` back. @vtselfa hasn't been active at all last year, so I don't think it will be merged. Please fork.