review-checklist

To ensure database operations use atomic transactions during a pull request review, verify that multi-step database updates are wrapped in transactional blocks and that both postgres and libsql backends stay synchronized for any new Database trait methods.

SSRF-resistant URL validation in pre-merge code review confirms that user-facing URLs are checked to prevent server-side request forgery, ensuring sensitive parameters are redacted before logging and destructive tool actions require explicit approval before merging.

Rust string and path safety checks verify that external user strings are processed strictly at character boundaries and that extension, media, and path comparisons are case-insensitive where required, preventing truncation and mismatch errors before merge.

Yes, pre-merge checklist verification confirms that new LlmProvider trait methods are delegated through all wrappers and decorators, ensuring the entire provider chain is covered by tests before the code is merged.

Test hygiene requirements dictate that tests use tempfile for temp file handling, avoid real network requests by using mocks or test-net IPs, and maintain determinism to ensure reliable, repeatable test outcomes before merging.

Redacting sensitive parameters before logging or streaming prevents confidential data exposure during code execution, fulfilling security and data safety requirements needed to pass pre-merge checks and protect application integrity.