Fix coding mode Git safety enforcement

[cursor]

Bug and impact

• Coding mode could execute disabled capabilities if a model emitted an unadvertised tool call/XML invoke while another coding tool category kept tool dispatch active.
• The generic coding_run_command shell path allowed git push --force / force refspecs, bypassing the dedicated push tool's force-push protection and risking remote history loss.
• Authenticated Git clone URL validation accepted http://, allowing a saved PAT to be sent over cleartext HTTP.

Root cause

• Coding tool settings were only used when building advertised tool definitions, not enforced inside run_coding_tool.
• Git safety checks were applied to the dedicated remote push helper but not to shell-invoked Git commands.
• The HTTPS validator allowed both https:// and http:// despite PAT-backed Git operations requiring HTTPS.

Fix

• Enforce coding tool category settings at execution time.
• Block force-push flags/refspecs and global/system/worktree Git config from coding_run_command Git invocations.
• Require Git remote URLs to start with https://.
• Added regression tests for the safety policies.

Validation

• cargo +stable test --manifest-path src-tauri/Cargo.toml validate_
• cargo +stable test --manifest-path src-tauri/Cargo.toml coding_tools_fail_closed_without_settings
• cargo +stable test --manifest-path src-tauri/Cargo.toml