Merge pull request #1 from knqiufan/feat/rust-build-test-optimization

build: Rust 构建与测试效率优化（P0/P2）

Author: knqiufan

.github/workflows/ci.yml

@@ -65,6 +65,8 @@ jobs:
         with:
           workspaces: src-tauri
 
+      - uses: taiki-e/install-action@nextest
+
       - name: Check formatting
         working-directory: src-tauri
         run: cargo fmt --check
@@ -75,7 +77,13 @@ jobs:
 
       - name: Run tests
         working-directory: src-tauri
-        run: cargo test --all-features
+        env:
+          # GitHub Linux runners can crash GNU ld when linking many large Tauri
+          # integration test binaries concurrently. Keep test compilation serial
+          # and omit debug info to reduce linker pressure.
+          CARGO_BUILD_JOBS: 1
+          CARGO_PROFILE_TEST_DEBUG: 0
+        run: cargo nextest run --all-features --profile ci
 
       - name: Build check
         working-directory: src-tauri

.gitignore

@@ -1,6 +1,6 @@
 # ===== Rust =====
 src-tauri/target/
-.cargo/
+/.cargo/
 
 # ===== Node / Frontend =====
 node_modules/

AGENTS.md

@@ -95,40 +95,35 @@ If dependency APIs change across minors, prefer checking the manifest first, the
 # Frontend only
 npm run dev          # Vite dev server on :1420
 
-# Full app (frontend + Rust backend): clean Rust artifacts first, then dev
-cd src-tauri
-cargo clean
-cd ..
+# Full app (frontend + Rust backend)
 npm run tauri dev    # Tauri dev mode
 
 # Build
 npm run build        # Frontend production build
-
-# Full app build: clean Rust artifacts first
-cd src-tauri
-cargo clean
-cd ..
 npm run tauri build  # Full app build
 
 # Python sidecar
 cd agent
 python -m uvicorn app.main:app --port 9527
 
-# Rust checks (always from src-tauri/): clean before any cargo workflow
+# Rust checks (from src-tauri/; use incremental compile — do not cargo clean routinely)
 cd src-tauri
-cargo clean
 cargo check          # Fast compile check
-
-cd src-tauri
-cargo clean
-cargo test           # Run tests
-
-cd src-tauri
-cargo clean
+cargo test --test crypto_tests   # Targeted test during daily work (see mapping in docs/guides/rust-build-test-optimization.md §4.2)
+cargo nextest run --test crypto_tests   # Same, faster parallel runner (requires: cargo install cargo-nextest)
+cargo test --features test-private --test chat_commands_tests   # Commands tests that need test-private
+cargo nextest run --all-features --profile ci   # Full suite (preferred before commit)
+cargo test           # Full suite fallback if nextest not installed
 cargo build          # Standalone Rust build when not using npm wrapper
 ```
 
-**Cargo hygiene:** Before `cargo check`, `cargo test`, `cargo build`, or npm scripts that invoke the Tauri/Rust build (`tauri dev`, `tauri build`), run `cargo clean` inside `src-tauri/` so stale `target/` artifacts do not accumulate across iterations.
+**Optional P2 tooling** (see [`docs/guides/rust-build-test-optimization.md`](docs/guides/rust-build-test-optimization.md) §5):
+
+- `cargo install cargo-nextest --locked` — parallel test runner; config in `src-tauri/.config/nextest.toml`
+- `cargo install sccache` — compile cache; then uncomment `rustc-wrapper = "sccache"` in `src-tauri/.cargo/config.toml`
+- Build tuning defaults live in `src-tauri/.cargo/config.toml` (`dev` dependency `opt-level`, optional `sccache` / linker)
+
+**Cargo hygiene:** Do **not** run `cargo clean` before routine `cargo check`, `cargo test`, `cargo build`, `tauri dev`, or `tauri build` — incremental compile is intentional and much faster. Run `cargo clean` in `src-tauri/` only when troubleshooting: link errors, metadata mismatch, unexplained failures after a branch switch, or Rust toolchain / major dependency upgrades. See [`docs/guides/rust-build-test-optimization.md`](docs/guides/rust-build-test-optimization.md).
 
 ## Environment Setup
 

CLAUDE.md

@@ -95,40 +95,35 @@ If dependency APIs change across minors, prefer checking the manifest first, the
 # Frontend only
 npm run dev          # Vite dev server on :1420
 
-# Full app (frontend + Rust backend): clean Rust artifacts first, then dev
-cd src-tauri
-cargo clean
-cd ..
+# Full app (frontend + Rust backend)
 npm run tauri dev    # Tauri dev mode
 
 # Build
 npm run build        # Frontend production build
-
-# Full app build: clean Rust artifacts first
-cd src-tauri
-cargo clean
-cd ..
 npm run tauri build  # Full app build
 
 # Python sidecar
 cd agent
 python -m uvicorn app.main:app --port 9527
 
-# Rust checks (always from src-tauri/): clean before any cargo workflow
+# Rust checks (from src-tauri/; use incremental compile — do not cargo clean routinely)
 cd src-tauri
-cargo clean
 cargo check          # Fast compile check
-
-cd src-tauri
-cargo clean
-cargo test           # Run tests
-
-cd src-tauri
-cargo clean
+cargo test --test crypto_tests   # Targeted test during daily work (see mapping in docs/guides/rust-build-test-optimization.md §4.2)
+cargo nextest run --test crypto_tests   # Same, faster parallel runner (requires: cargo install cargo-nextest)
+cargo test --features test-private --test chat_commands_tests   # Commands tests that need test-private
+cargo nextest run --all-features --profile ci   # Full suite (preferred before commit)
+cargo test           # Full suite fallback if nextest not installed
 cargo build          # Standalone Rust build when not using npm wrapper
 ```
 
-**Cargo hygiene:** Before `cargo check`, `cargo test`, `cargo build`, or npm scripts that invoke the Tauri/Rust build (`tauri dev`, `tauri build`), run `cargo clean` inside `src-tauri/` so stale `target/` artifacts do not accumulate across iterations.
+**Optional P2 tooling** (see [`docs/guides/rust-build-test-optimization.md`](docs/guides/rust-build-test-optimization.md) §5):
+
+- `cargo install cargo-nextest --locked` — parallel test runner; config in `src-tauri/.config/nextest.toml`
+- `cargo install sccache` — compile cache; then uncomment `rustc-wrapper = "sccache"` in `src-tauri/.cargo/config.toml`
+- Build tuning defaults live in `src-tauri/.cargo/config.toml` (`dev` dependency `opt-level`, optional `sccache` / linker)
+
+**Cargo hygiene:** Do **not** run `cargo clean` before routine `cargo check`, `cargo test`, `cargo build`, `tauri dev`, or `tauri build` — incremental compile is intentional and much faster. Run `cargo clean` in `src-tauri/` only when troubleshooting: link errors, metadata mismatch, unexplained failures after a branch switch, or Rust toolchain / major dependency upgrades. See [`docs/guides/rust-build-test-optimization.md`](docs/guides/rust-build-test-optimization.md).
 
 ## Environment Setup
 

README.md

@@ -116,9 +116,6 @@ pip install -r requirements.txt
 
 ```bash
 # 完整桌面应用（推荐）
-cd src-tauri
-cargo clean
-cd ..
 npm run tauri dev
 
 # 仅前端（浏览器调试，无 Tauri IPC）
@@ -138,11 +135,14 @@ npm run build          # 前端生产构建
 npm test               # 前端 Vitest
 
 cd src-tauri
-cargo clean
-cargo check            # Rust 编译检查
-cargo test             # Rust 集成测试
+cargo check            # Rust 编译检查（日常依赖增量编译，勿先 cargo clean）
+cargo test --test crypto_tests   # 日常：按改动模块跑精准测试（映射表见优化指南 §4.2）
+cargo nextest run --all-features --profile ci   # 提交前：全量测试（推荐，需 cargo install cargo-nextest）
+cargo test             # 提交前：全量测试（未装 nextest 时的后备）
 ```
 
+若 Rust 编译出现链接错误、metadata 异常或切分支后无法解释的失败，再在 `src-tauri/` 下按需执行 `cargo clean` 后重试。详见 [`docs/guides/rust-build-test-optimization.md`](docs/guides/rust-build-test-optimization.md)。
+
 ## 目录结构
 
 ```