Add custom overwrite

Optimize windows ipc

Optimize windows arm64

Optimize some details

Update core

Author: chen08209

.claude/commands/i18n.md

@@ -0,0 +1,93 @@
+Scan `lib/` for hardcoded Chinese strings and internationalize them following the project's ARB conventions.
+
+## Instructions
+
+You are performing i18n extraction for a Flutter project that uses the Flutter Intl plugin with ARB files.
+
+### Project localization context
+
+- **ARB files**: `arb/intl_en.arb`, `arb/intl_zh_CN.arb`, `arb/intl_ja.arb`, `arb/intl_ru.arb`
+- **Key conventions**: camelCase, flat keys (no nesting, no `@` metadata), semantic naming
+  - Short labels: `rule`, `global`, `direct`, `edit`, `confirm`
+  - Descriptive suffix `Desc`: `themeDesc`, `tunDesc`, `logsDesc`
+  - Validation suffix: `profileNameNullValidationDesc`
+- **Generated code**: `lib/l10n/l10n.dart` (DO NOT edit generated files)
+- **Access patterns**:
+  - In widgets with BuildContext: `context.appLocalizations.key` (import `common.dart`)
+  - In controllers/providers/non-widget code: `currentAppLocalizations.key` (import `app_localizations.dart`)
+
+### Step 1: Find hardcoded Chinese strings
+
+Use Grep to search `lib/` for Chinese characters. The regex pattern for Chinese characters is `[\x{4e00}-\x{9fff}]`.
+
+Important filters:
+- **Exclude** `lib/l10n/` (generated localization files)
+- **Exclude** lines that already use `appLocalizations` or `currentAppLocalizations`
+- **Exclude** false positives that are NOT Chinese text:
+  - Arrow symbols: `↑` `↓` `←` `→` (Unicode arrows, not CJK)
+  - Middle dot: `·` (U+00B7, not CJK)
+  - Command symbol: `⌘` (U+2318, not CJK)
+  - Other CJK punctuation that is used as UI symbols, not translatable text
+
+For each match, read the surrounding context (5-10 lines) to understand:
+- What the string represents (label, error message, tooltip, dialog text, etc.)
+- Whether it's inside a widget (has `BuildContext` available) or non-widget code
+- Whether it appears in a `Text()`, `TextSpan()`, `title:`, `label:`, or other text position
+
+### Step 2: Generate ARB keys
+
+For each hardcoded Chinese string:
+
+1. **Choose a key name** following project conventions:
+   - Use the Chinese meaning to derive an English camelCase key
+   - Keep it concise: `createConfig` not `createAConfigurationForTheProfile`
+   - Use `Desc` suffix for descriptive/explanatory text
+   - Use existing similar keys as reference (check `arb/intl_en.arb` for patterns)
+
+2. **Determine the English translation** (the value for `intl_en.arb`)
+
+3. **Determine the Chinese translation** (the value for `intl_zh_CN.arb`) — this is the original hardcoded string
+
+4. **For ja and ru**: use the English translation as a placeholder (translators will fill these in later)
+
+### Step 3: Update ARB files
+
+For each new key, add it to all 4 ARB files. Read each ARB file first to find the right insertion point (alphabetical order is not required, but appending near the end is clean).
+
+Format: add a new line like `"keyName": "value",` before the closing `}`.
+
+### Step 4: Replace hardcoded strings in Dart files
+
+Replace each hardcoded Chinese string with the appropriate localization call:
+
+- If inside a widget BuildContext: `context.appLocalizations.keyName`
+- If in controller/provider code: `currentAppLocalizations.keyName`
+
+Ensure the correct import exists:
+- For `context.appLocalizations`: the file should import `common.dart` (check if it already does)
+- For `currentAppLocalizations`: the file should import `app_localizations.dart` (check if it already does)
+
+If the file uses string interpolation (e.g., `'创建 $name 配置'`), convert to the ARB parameterized format:
+- In ARB: `"keyName": "Create $name config"`
+- In Dart: `currentAppLocalizations.keyName(name)`
+
+### Step 5: Report changes
+
+After all modifications, output a summary:
+1. List each file modified and what changed
+2. List each new ARB key added with its translations
+3. Remind the user to run code generation if needed:
+   ```
+   dart run build_runner build --delete-conflicting-outputs
+   ```
+   or trigger Flutter Intl regeneration in their IDE.
+
+### Important notes
+
+- Only extract strings that are user-facing UI text. Do NOT extract:
+  - Comments (lines starting with `//`)
+  - Log messages (unless they appear in the UI)
+  - Variable names or identifiers
+  - String literals used as keys/identifiers (not displayed to users)
+- If a Chinese string is split across multiple lines or concatenations, merge them into a single ARB entry
+- If a string contains dynamic content (variables, URLs), use ARB parameter syntax `$variableName`

.github/workflows/build.yaml

@@ -8,7 +8,33 @@ env:
   IS_STABLE: ${{ !contains(github.ref, '-') }}
 
 jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          submodules: recursive
+
+      - name: Setup Flutter
+        uses: subosito/flutter-action@v2
+        with:
+          channel: stable
+          flutter-version: 3.41.9
+          cache: true
+
+      - name: Install dependencies
+        run: flutter pub get
+
+      - name: Analyze
+        run: flutter analyze --no-fatal-infos
+
+      - name: Run tests
+        run: flutter test --reporter expanded
+
   build:
+    needs: [ test ]
     runs-on: ${{ matrix.os }}
     strategy:
       matrix:
@@ -27,9 +53,9 @@ jobs:
           - platform: macos
             os: macos-latest
             arch: arm64
-          #          - platform: windows
-          #            os: windows-11-arm
-          #            arch: arm64
+          - platform: windows
+            os: windows-11-arm
+            arch: arm64
           - platform: linux
             os: ubuntu-24.04-arm
             arch: arm64
@@ -64,19 +90,23 @@ jobs:
           cache-dependency-path: |
             core/go.sum
 
+      - name: Enable git long paths (Windows)
+        if: startsWith(matrix.os, 'windows')
+        run: git config --global core.longpaths true
+
       - name: Setup Flutter
         if: ${{ !(startsWith(matrix.os, 'windows-11-arm') || startsWith(matrix.os, 'ubuntu-24.04-arm')) }}
         uses: subosito/flutter-action@v2
         with:
           channel: stable
-          flutter-version: 3.35.7
+          flutter-version: 3.41.9
           cache: true
       - name: Setup Flutter With Other
         if: startsWith(matrix.os, 'windows-11-arm') || startsWith(matrix.os, 'ubuntu-24.04-arm')
         uses: subosito/flutter-action@v2
         with:
           channel: master
-          flutter-version: 3.35.7
+          flutter-version: 3.44.0-0.1.pre
           cache: true
 
       - name: Get Flutter Dependency

.gitignore

@@ -41,9 +41,8 @@ app.*.symbols
 # Obfuscation related
 app.*.map.json
 
-#AI generated
-CLAUDE.md
-/.claude
+# Claude Code - ignore user-specific settings only
+.claude/settings.local.json
 
 
 # Android Studio will place build artifacts here

CLAUDE.md

@@ -0,0 +1,182 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+FlClash is a multi-platform proxy client based on ClashMeta (mihomo), built with Flutter. Supports Android, Windows,
+macOS, and Linux. Material You design with Surfboard-like UI.
+
+## Common Development Commands
+
+### Building
+
+```bash
+# Update submodules first (ClashMeta Go core lives in core/Clash.Meta/)
+git submodule update --init --recursive
+
+# Build core + Flutter app via setup.dart
+dart ./setup.dart android --arch arm64
+dart ./setup.dart android --arch arm --arch-name armeabi-v7a
+dart ./setup.dart android --arch amd64 --arch-name x86_64
+dart ./setup.dart macos --arch arm64
+dart ./setup.dart macos --arch amd64
+dart ./setup.dart linux --arch amd64
+dart ./setup.dart windows --arch amd64
+
+# Build only the Go core (skip Flutter packaging)
+dart ./setup.dart android --arch arm64 --out core
+dart ./setup.dart macos --arch arm64 --out core
+```
+
+### Flutter Development
+
+```bash
+flutter pub get
+flutter run        # Run on connected device/desktop
+flutter test        # Run all tests (use flutter test, not dart test — models pull in Flutter types)
+```
+
+### Code Generation
+
+Required after modifying models, providers, or database schema:
+
+```bash
+dart run build_runner build --delete-conflicting-outputs
+dart run build_runner watch  # Continuous regeneration
+```
+
+Code generation covers: Riverpod providers (`riverpod_generator`), models (`freezed`, `json_serializable`), and database
+tables (`drift_dev`).
+
+### Testing
+
+Tests use `package:test/test.dart` for pure Dart logic (common utils, models) and `flutter_test` for provider/widget tests.
+`mocktail` is the mocking framework.
+
+```bash
+flutter test test/models/      # Model serialization & extension round-trip tests
+flutter test test/core/        # CoreController tests (mocked CoreHandlerInterface)
+flutter test test/providers/   # Riverpod provider tests (config & app state notifiers)
+flutter test test/common/      # Utility function tests (utils, string, iterable, fixed, etc.)
+flutter test test/database/    # Database type converter tests
+```
+
+**Mocking `CoreHandlerInterface`:** Use `CoreController.test(mock)` to inject a mock interface. Call
+`CoreController.resetInstance()` in `tearDown` to clean up the singleton between tests. Remember to
+`registerFallbackValue()` for freezed params used with `any()` matchers.
+
+**Provider tests:** Use `ProviderContainer` directly (no widget tree needed for simple notifiers). The Riverpod
+generated `update()` method takes a callback: `notifier.update((state) => newValue)`.
+
+**Model round-trip tests:** Always go through `jsonEncode`/`jsonDecode` when testing freezed models with
+nested objects — `toJson()` stores child objects directly (not as maps), so direct `fromJson(toJson())`
+fails for nested freezed types.
+
+### Build Dependencies
+
+**Linux:** `sudo apt-get install libayatana-appindicator3-dev libkeybinder-3.0-dev`
+
+**Windows:** GCC and Inno Setup. `ANDROID_NDK` env var for Android builds.
+
+**macOS:** `npm install -g appdmg` for DMG creation.
+
+## Architecture
+
+### Core Integration (Go ClashMeta <-> Flutter)
+
+This is the most important architectural concept. The Go proxy core (`core/`) operates in two modes:
+
+- **Android (lib mode):** Go core compiled as C shared library (`libclash.so`) via `go build -buildmode=c-shared` with
+  CGO. Flutter calls it via FFI through the `service` plugin. Dart-side: `lib/core/lib.dart` (`CoreLib` class).
+
+- **Desktop (core mode):** Go core runs as a separate process with `CGO_ENABLED=0`. Flutter communicates via
+  JSON-over-socket (Unix socket on macOS/Linux, TCP on Windows). Dart-side: `lib/core/service.dart` (`CoreService`
+  class).
+
+`lib/core/controller.dart` (`CoreController`) selects the implementation based on platform. `lib/core/interface.dart`
+defines the shared `CoreHandlerInterface`.
+
+Go core key files: `core/hub.go` (handler functions), `core/action.go` (dispatch), `core/lib.go` (CGO exports),
+`core/server.go` (socket server).
+
+### State Management (Riverpod)
+
+Provider files in `lib/providers/`:
+
+- `app.dart` - Runtime/UI state (logs, traffic, delays, loading, navigation)
+- `config.dart` - Persistent config providers (app settings, theme, VPN, proxy style)
+- `state.dart` - Derived/computed providers (navigation, proxy, tray, color scheme)
+- `action.dart` - Business logic notifiers (setup, backup, core lifecycle, proxy selection)
+- `database.dart` - Drift database provider wrappers
+
+`globalState` (`lib/state.dart`) is a singleton holding app lifecycle, timers, theme, and the start/stop state.
+Providers are generated into `lib/providers/generated/`.
+
+### Database (Drift/SQLite)
+
+Type-safe SQLite via Drift in `lib/database/`. Tables: `Profiles`, `Scripts`, `ProxyGroups`, `GlobalRules`,
+`ProfileAddedRules`, `ProfileCustomRules`, `ProfileDisabledRuleIds`, `Icons`, `Links`. Uses fractional indexing for
+ordering.
+
+### Manager Stack (Widget Tree)
+
+Managers are nested InheritedWidgets/StatefulWidgets in `lib/application.dart`:
+
+```
+AppEnvManager > StatusManager > ThemeManager
+  > [Desktop: WindowManager > TrayManager > HotKeyManager > ProxyManager]
+  > ConnectivityManager > CoreManager > AppStateManager
+  > [Mobile: AndroidManager > VpnManager | Desktop: WindowHeaderContainer]
+```
+
+Each manager in `lib/manager/` handles a specific platform concern. Desktop-only managers are conditionally inserted.
+
+### Core Controller + Actions
+
+`lib/core/controller.dart` (`CoreController`) is a singleton facade over `CoreHandlerInterface`. All 25+ public methods
+delegate to the platform-specific interface (Android FFI or desktop socket). Has `@visibleForTesting` constructor and
+`resetInstance()` for test injection.
+
+Business logic lives in Riverpod notifier classes in `lib/providers/action.dart` (~960 lines, should be split):
+
+- `CommonAction` — update check, common UI operations
+- `SetupAction` — config setup, TUN management
+- `BackupAction` — backup/restore with WebDAV sync
+- `CoreAction` — core lifecycle (init, connect, restart, shutdown)
+- `SystemAction` — system integration (tray, exit, brightness)
+- `StoreAction` — profile storage operations
+- `ThemeAction` — theme state updates
+- `ProxiesAction` — group management, proxy selection
+- `ProfilesAction` — profile CRUD, auto-update, import
+
+### Platform Managers (`lib/manager/`)
+
+Desktop: `WindowManager`, `TrayManager`, `HotKeyManager`, `ProxyManager`
+Mobile: `AndroidManager`, `TileManager`, `VpnManager`
+Shared: `ConnectivityManager`, `CoreManager`, `AppStateManager`, `StatusManager`, `ThemeManager`
+
+### Local Plugins (`plugins/`)
+
+- `proxy` - System proxy configuration
+- `rust_api` - Flutter Rust Bridge FFI plugin (named pipe / local socket communication)
+- `tray_manager` - System tray (forked/custom)
+- `wifi_ssid` - Wi-Fi SSID detection
+- `window_ext` - Window extensions
+- `flutter_distributor` - App packaging/distribution
+
+### Rust Helper Service (`services/helper/`)
+
+Windows-only privileged helper for starting the core as admin and managing TUN. Built with
+`cargo build --release --features windows-service`. Token-based auth with Flutter app.
+
+### Localization
+
+ARB files in `arb/`. Generated via `flutter_intl` into `lib/l10n/`. Use `AppLocalizations.of(context)!` for strings.
+
+**Supported locales:** `en`, `zh_CN`, `ja`, `ru`
+
+**Access patterns:**
+
+- In widgets with BuildContext: `context.appLocalizations.key` (import `common.dart`)
+- In controllers/providers/non-widget code: `currentAppLocalizations.key` (import `app_localizations.dart`)