all: use cargo check --release instead of cargo build --release

Based on feedback from @lutter that release builds are really slow,
switch to cargo check --release which can catch conditional compilation
issues while being much faster than a full release build.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: fubhy

CLAUDE.md

@@ -120,14 +120,14 @@ cargo fmt --all
 # 🚨 MANDATORY: Check code for warnings and errors - MUST have zero warnings
 cargo check
 
-# 🚨 MANDATORY: Build in release mode to catch linking/optimization issues that cargo check misses
-cargo build --release
+# 🚨 MANDATORY: Check in release mode to catch conditional compilation issues
+cargo check --release
 ```
 
 🚨 **CRITICAL REQUIREMENTS for ANY implementation**:
 - **🚨 MANDATORY**: `cargo fmt --all` MUST be run before any commit
 - **🚨 MANDATORY**: `cargo check` MUST show zero warnings before any commit
-- **🚨 MANDATORY**: `cargo build --release` MUST complete successfully before any commit
+- **🚨 MANDATORY**: `cargo check --release` MUST complete successfully before any commit
 - **🚨 MANDATORY**: The unit test suite MUST pass before any commit
 
 Forgetting any of these means you failed to follow instructions. Before any commit or PR, ALL of the above MUST be satisfied! No exceptions!