ProxyWarden/.agent/checklists/change-safety.md

Change Safety Checklist

Use this before and after non-trivial changes.

Scope

• I identified whether this touches backend, UI, security, Windows service, subscription/routing, testing/release.
• I read the matching skill file.
• I avoided unrelated rewrites.
• I did not introduce a second source of truth.

Tauri boundary

• New/changed Rust command has matching TypeScript wrapper.
• DTOs are synchronized between Rust and TypeScript.
• Error shape is structured and actionable.
• Blocking work is not run on async runtime thread.

UX

• User-visible actions are explicit.
• Disabled states have reasons.
• Pending changes are visible before apply.
• Secrets are redacted.

Validation

• Relevant frontend build/test was run or explicitly not run with reason.
• Relevant Rust fmt/clippy/test was run or explicitly not run with reason.
• Windows-specific behavior was not claimed unless tested on Windows.