1lck · 1lck · Aug 16, 2026 · Aug 14, 2026 · Aug 14, 2026 · Aug 14, 2026
@@ -30,11 +30,11 @@ framework conventions.
 | `Sources/Lithe/Core/` | Platform-neutral ports and typed Rust operations |
 | `Sources/Lithe/Platform/MacOS/` | macOS adapters and composition |
 | `rust/lithe-core/` | Deterministic shared commands, models, validation, and C ABI |
-| `windows/` | Native C++23, Win32 adapter, and Qt implementation |
+| `windows/` | React/Tauri Windows product and Rust platform adapters |
 | `shared/` | Cross-platform contracts and fixtures, not compiled implementation |
 | `third_party/` | Upstream code; leave unchanged unless the task explicitly targets it |
 
-macOS is the current reference product. Windows is an independent native
+macOS is the current reference product. Windows is an independent React/Tauri
 implementation and must not import Swift source or depend on macOS types.
 
 ## Preserve application boundaries
@@ -48,15 +48,16 @@ implementation and must not import Swift source or depend on macOS types.
   `Process`, `Pipe`, `FileManager`, `FileHandle`, watchers, persistence stores,
   or concrete `Mac*` adapters.
 - Core and application code must remain free of SwiftUI, AppKit, CoreServices,
-  Win32, Qt, and concrete platform implementations.
+  Tauri, WebView2, Win32, and concrete platform implementations.
 - `MacServiceContainer` is the macOS composition root. Platform capabilities
   belong in `Sources/Lithe/Platform/MacOS/`.
 - Deterministic behavior shared by both products belongs in `rust/lithe-core/`.
   Native filesystem, process, terminal, runtime, security, persistence, and UI
   behavior belongs in platform adapters.
-- Windows application algorithms and services must not depend on Win32 or Qt.
-  Qt code must not include `core_client.h` directly, and public ports must not
-  expose Win32 handle types.
+- Windows feature code must import `@/platform/tauri-core` instead of the Tauri
+  core API directly. Shared operations route through `lithe-core`; Windows-only
+  terminal, watcher, credential, process, and WebView behavior stays in the
+  Tauri host or a platform plugin.
 
 ## Keep shared contracts deterministic
 
@@ -103,15 +104,47 @@ the existing stack can reasonably avoid.
 - Add tests in the owning crate for changes to commands, parsing, validation,
   ordering, cancellation, or serialization.
 
-### Windows C++ and Qt
-
-- Use C++23 and the existing CMake target boundaries. Use the Qt version pinned
-  in `.github/workflows/ci-windows.yml`.
-- Keep Qt widget state in `windows/qt/`, application behavior in `windows/app/`,
-  Rust communication in `windows/core/`, and native behavior in
-  `windows/adapters/`.
-- Add CTest coverage under `windows/tests/` for application, DTO, algorithm,
-  persistence, or adapter behavior that can be tested without manual UI work.
+#### Rust Core comments
+
+Apply the following comment standard to first-party code under
+`rust/lithe-core/`. It does not require comment coverage in the database helpers,
+Windows/Tauri Rust crates, generated code, or third-party sources.
+
+- Write comments in English and keep them accurate when behavior changes.
+- Start each production module with a concise `//!` description of its
+  responsibility or architectural boundary.
+- Use `///` for exported APIs, shared request and response types, core domain
+  types, and C ABI functions. Document ownership and add `# Safety` for unsafe
+  entry points; describe errors only when the failure contract is not obvious.
+- Document enums, structs, variants, and fields whenever their names alone do
+  not make their semantics, allowed values, units, ownership, or protocol role
+  immediately clear. This requirement applies to internal types as well as
+  exported contracts.
+- Use `//` inside implementations to explain non-obvious decisions and
+  constraints involving compatibility, determinism, ordering, security,
+  performance, or cross-platform behavior.
+- In tests, comment the scenario, regression risk, or boundary being protected
+  when the test name and assertions do not make that intent clear.
+- Do not narrate statements, restate descriptive names, or add comments to
+  trivial accessors and straightforward control flow solely for coverage.
+- Run `./scripts/verify-rust-core-comments.sh` before slower Rust Core checks.
+  It enforces module documentation, exported Rustdoc, English comments, and
+  unsafe API safety sections without requiring documentation on every internal
+  helper. Still review changed internal types and implementations for the
+  semantic cases above, which a static check cannot judge reliably.
+
+### Windows React and Tauri
+
+- Use Bun for frontend scripts and Tauri 2 for the Windows host. Keep React
+  feature code in `windows/tauri/src/features`, reusable UI in
+  `windows/tauri/src/ui`, the invoke boundary in
+  `windows/tauri/src/platform`, and native Rust behavior in
+  `windows/tauri/src-tauri`.
+- Do not restore a parallel C++/Qt application layer or one Tauri command per
+  shared Core operation. Translate compatibility command names through the
+  central platform dispatcher.
+- Add frontend tests for product behavior and Rust tests in the owning crate.
+  Verify WebView2, ConPTY, installer, signing, and updater behavior on Windows.
 
 ## Avoid hardcoded environment details
 
@@ -130,8 +163,8 @@ the existing stack can reasonably avoid.
 
 - Do not silently discard errors. Return, translate, or log them at the layer
   that has enough context to act on them.
-- Preserve stable contract error categories when crossing Rust, Swift, C++, or
-  process boundaries.
+- Preserve stable contract error categories when crossing Rust, Swift,
+  TypeScript, Tauri, or process boundaries.
 - User-facing failures should be actionable without exposing credentials,
   environment contents, or unnecessary internal details.
 - Comments should explain non-obvious constraints or decisions, not narrate the
@@ -151,7 +184,7 @@ before handoff.
 | Core feature behavior | `./scripts/verify-core.sh` |
 | Git graph behavior | `./scripts/verify-git-graph.sh` |
 | Windows boundaries from macOS/Linux | `./scripts/verify-windows-boundaries.sh` |
-| Windows implementation on Windows | `./scripts/build-windows.ps1 -Configuration Release -BuildQt`, then `ctest --test-dir windows/build-windows -C Release --output-on-failure` |
+| Windows implementation on Windows | `./scripts/build-windows.ps1 -Configuration Release`, then `cargo test --manifest-path windows/tauri/src-tauri/Cargo.toml` |
 
 Also run tests for directly affected crates or targets. If the current machine
 cannot run a platform-specific check, state that clearly; do not claim an

@@ -43,7 +43,7 @@ body:
     id: environment
     attributes:
       label: Environment / 环境信息
-      description: Include relevant JDK, Maven, JDT LS, Rust, or Qt versions. / 请填写相关的 JDK、Maven、JDT LS、Rust 或 Qt 版本。
+      description: Include relevant JDK, Maven, JDT LS, Rust, WebView2, or Tauri versions. / 请填写相关的 JDK、Maven、JDT LS、Rust、WebView2 或 Tauri 版本。
       placeholder: |
         JDK:
         Maven:

@@ -20,13 +20,19 @@ jobs:
     runs-on: ubuntu-latest
     outputs:
       full: ${{ steps.classify.outputs.full }}
+      comments: ${{ steps.classify.outputs.comments }}
+      metadata: ${{ steps.classify.outputs.metadata }}
 
     steps:
       - name: Check out source
         uses: actions/checkout@v7
         with:
           fetch-depth: 0
 
+      - name: Test CI change classifier
+        shell: bash
+        run: ./scripts/test-classify-ci-changes.sh
+
       - name: Classify changed paths
         id: classify
         env:
@@ -36,7 +42,11 @@ jobs:
         shell: bash
         run: |
           if [[ "$EVENT_NAME" == "workflow_dispatch" ]]; then
-            echo "full=true" >> "$GITHUB_OUTPUT"
+            {
+              echo "full=true"
+              echo "comments=false"
+              echo "metadata=false"
+            } >> "$GITHUB_OUTPUT"
             exit 0
           fi
 
@@ -45,22 +55,21 @@ jobs:
             base_sha="$PR_BASE_SHA"
           fi
 
-          full=false
-          while IFS= read -r path; do
-            case "$path" in
-              README.md|README.zh-CN.md|docs/*|Casks/*)
-                ;;
-              *)
-                full=true
-                break
-                ;;
-            esac
-          done < <(git diff --name-only "$base_sha" "$GITHUB_SHA")
-
-          echo "full=$full" >> "$GITHUB_OUTPUT"
-
-      - name: Validate lightweight changes
-        if: steps.classify.outputs.full == 'false'
+          ./scripts/classify-ci-changes.sh "$base_sha" "$GITHUB_SHA" >> "$GITHUB_OUTPUT"
+
+      - name: Set up Rust for comment verification
+        if: steps.classify.outputs.full == 'false' && steps.classify.outputs.comments == 'true'
+        uses: dtolnay/rust-toolchain@stable
+
+      - name: Validate text-only changes
+        if: steps.classify.outputs.full == 'false' && steps.classify.outputs.comments == 'true'
+        shell: bash
+        run: |
+          git diff --check "${{ github.event.pull_request.base.sha || github.event.before }}" "$GITHUB_SHA"
+          ./scripts/verify-rust-core-comments.sh
+
+      - name: Validate lightweight metadata changes
+        if: steps.classify.outputs.full == 'false' && steps.classify.outputs.metadata == 'true'
         shell: bash
         run: |
           git diff --check "${{ github.event.pull_request.base.sha || github.event.before }}" "$GITHUB_SHA"

@@ -7,6 +7,8 @@ on:
       - "rust/**"
       - "shared/**"
       - "scripts/build-windows.ps1"
+      - "scripts/classify-ci-changes.sh"
+      - "scripts/test-classify-ci-changes.sh"
       - "scripts/verify-windows-boundaries.ps1"
       - ".github/workflows/ci-windows.yml"
   push:
@@ -17,6 +19,8 @@ on:
       - "rust/**"
       - "shared/**"
       - "scripts/build-windows.ps1"
+      - "scripts/classify-ci-changes.sh"
+      - "scripts/test-classify-ci-changes.sh"
       - "scripts/verify-windows-boundaries.ps1"
       - ".github/workflows/ci-windows.yml"
   workflow_dispatch:
@@ -25,8 +29,46 @@ permissions:
   contents: read
 
 jobs:
+  changes:
+    name: Classify changes
+    runs-on: ubuntu-latest
+    outputs:
+      full: ${{ steps.classify.outputs.full }}
+
+    steps:
+      - name: Check out source
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Test CI change classifier
+        shell: bash
+        run: ./scripts/test-classify-ci-changes.sh
+
+      - name: Classify changed content
+        id: classify
+        env:
+          EVENT_NAME: ${{ github.event_name }}
+          PR_BASE_SHA: ${{ github.event.pull_request.base.sha }}
+          PUSH_BASE_SHA: ${{ github.event.before }}
+        shell: bash
+        run: |
+          if [[ "$EVENT_NAME" == "workflow_dispatch" ]]; then
+            echo "full=true" >> "$GITHUB_OUTPUT"
+            exit 0
+          fi
+
+          base_sha="$PUSH_BASE_SHA"
+          if [[ "$EVENT_NAME" == "pull_request" ]]; then
+            base_sha="$PR_BASE_SHA"
+          fi
+
+          ./scripts/classify-ci-changes.sh "$base_sha" "$GITHUB_SHA" >> "$GITHUB_OUTPUT"
+
   build:
     name: Build and test Windows implementation
+    needs: changes
+    if: needs.changes.outputs.full == 'true'
     runs-on: windows-latest
 
     steps:
@@ -38,26 +80,21 @@ jobs:
         with:
           targets: x86_64-pc-windows-msvc
 
-      - name: Set up Qt
-        uses: jurplel/install-qt-action@v4
+      - name: Set up Bun
+        uses: oven-sh/setup-bun@v2
         with:
-          version: "6.8.2"
-          arch: win64_msvc2022_64
-          archives: qtbase
-          cache: true
+          bun-version: "1.3.12"
 
-      - name: Build Rust core and C++ targets
+      - name: Build Windows Tauri application
         shell: pwsh
-        run: ./scripts/build-windows.ps1 -Configuration Release -BuildQt
+        run: ./scripts/build-windows.ps1 -Configuration Release
 
       - name: Verify Windows boundaries
         shell: pwsh
         run: ./scripts/verify-windows-boundaries.ps1
 
-      - name: Run C++ tests
-        shell: pwsh
-        run: ctest --test-dir windows/build-windows -C Release --output-on-failure
-
       - name: Run Rust tests
         shell: pwsh
-        run: cargo test --manifest-path rust/Cargo.toml
+        run: |
+          cargo test --manifest-path rust/Cargo.toml
+          cargo test --manifest-path windows/tauri/src-tauri/Cargo.toml
@@ -121,6 +121,15 @@ jobs:
           /usr/libexec/PlistBuddy \
             -c "Print :CFBundleVersion" \
             "$app_path/Contents/Info.plist"
+          for build_key in \
+            LitheBuildGitRevision \
+            LitheBuildGitBranch \
+            LitheBuildGitDirty \
+            LitheBuildTimestamp; do
+            /usr/libexec/PlistBuddy \
+              -c "Print :${build_key}" \
+              "$app_path/Contents/Info.plist"
+          done
           lipo "$app_path/Contents/MacOS/Lithe" -verify_arch "$LITHE_ARCH"
           hdiutil imageinfo "$dmg_path" > /dev/null
           test -s "$dmg_path"

@@ -31,17 +31,10 @@ jobs:
         with:
           targets: x86_64-pc-windows-msvc
 
-      - name: Set up Qt
-        uses: jurplel/install-qt-action@v4
+      - name: Set up Bun
+        uses: oven-sh/setup-bun@v2
         with:
-          version: "6.8.2"
-          arch: win64_msvc2022_64
-          modules: qtbase
-          cache: true
-
-      - name: Install NSIS
-        shell: pwsh
-        run: choco install nsis --no-progress --yes
+          bun-version: "1.3.12"
 
       - name: Resolve release version
         id: version
@@ -61,9 +54,9 @@ jobs:
           "version=$version" >> $env:GITHUB_OUTPUT
           "tag=v$version" >> $env:GITHUB_OUTPUT
 
-      - name: Build Rust core and Qt workbench
+      - name: Build Windows Tauri application
         shell: pwsh
-        run: ./scripts/build-windows.ps1 -Configuration Release -BuildQt
+        run: ./scripts/build-windows.ps1 -Configuration Release
 
       - name: Import Authenticode certificate
         shell: pwsh

@@ -2,4 +2,5 @@
 
 Before any work in this repository, load and follow the `develop-lithe` skill
 at `.agents/skills/develop-lithe/SKILL.md`. That Skill is the single source of
-truth for AI coding and verification rules.
+truth for AI coding and verification rules, including the required Rust Core
+comment standard.