{"agent":"claude","input":"A Sentry alert fired for this Rust CLI; its payload follows this prompt. Use the Sentry connection to read the issue, its latest event, the panic or error message, the frames with their file and line, and the tags that carry the command line and the shell. In a crate shaped like ajeetdsouza/zoxide, find the function the frames point at under src/cmd/, src/db/, src/config.rs or src/util.rs, or the shell template under templates/ when the shell integration misbehaved. Write a test in the style the module already has: an rstest case in src/db/stream.rs or src/shell.rs, a tempdir-based test in src/db/mod.rs, or an assert_cmd test against the built binary with _ZO_DATA_DIR pointed at a temporary directory. Confirm it fails with the same message as the event, then fix the cause in that one function or template without catching the panic or hiding the error. Run cargo clippy --all-features --all-targets -- -Dwarnings, cargo fmt --all --check, cargo msrv verify and cargo test --all-features --no-fail-fast, installing any shell a new shell test needs. Open a pull request that links the Sentry issue, quotes the message and frames and the failing test output, and explains the cause. If it does not reproduce, stop and report what you tried.\n\nAlert payload:\n{payload}","resources":[{"url":"https://github.com/your-org/your-app"}],"connections":["sentry"]}