🎨 Palette: 优化配对按钮的状态过渡和对比度

[01luyicheng]

💡 What: 将配对按钮的内容包裹在 AnimatedContent 中，并为加载动画使用 LocalContentColor.current。
🎯 Why: 为了在默认状态和加载状态之间提供平滑的过渡，而不是生硬的视觉切换，并确保在禁用状态下有适当的颜色对比度。
📸 Before/After: 视觉过渡现在更加平滑，禁用状态下的颜色对比度更好。
♿ Accessibility: 在异步加载过程中提供更好的视觉反馈，并为视障用户提供更好的视觉对比度。

---

PR created automatically by Jules for task 2018085803704138550 started by @01luyicheng

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 896d7547-040e-420e-8e58-6e57c56f8560

📥 Commits

Reviewing files that changed from the base of the PR and between b217d54 and 55de24c.

📒 Files selected for processing (2)

• .Jules/palette.md
• android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt

📜 Recent review details

🧰 Additional context used

📓 Path-based instructions (3)

android/app/src/main/java/com/netproxy/gateway/**/*.kt

📄 CodeRabbit inference engine (CLAUDE.md)

android/app/src/main/java/com/netproxy/gateway/**/*.kt: Source of truth for runtime behavior is Kotlin code under android/app/src/main/java/com/netproxy/gateway/. If documentation conflicts with code, code is authoritative and documentation must be updated.
WiFi connection path uses traditional API limited on Android 10+.
MQTT security uses TLS 1.2 and certificate pinning when MQTT_TLS_PUBLIC_KEY_PINS is configured; falls back to default CA validation when empty.
Network egress control: cannot force Socket to use WiFi or mobile data; current protect() bypasses VPN but traffic may be routed to unintended interfaces in vendor scenarios (Link Turbo, dual WiFi acceleration).
Missing native Android multi-network APIs: code does not use Network.bindSocket(), excludeRoute(), or other APIs for true network interface binding.
Multi-network handling is incomplete: code only identifies single network type and cannot properly handle multiple simultaneous networks (dual WiFi, Bluetooth PAN, OTG wired) or network switching scenarios. See docs/TECH_DEBT.md C1 and C3.
Dependency risk: Paho MQTT client maintenance is inactive. New features and bug fixes may be delayed. See docs/ISSUES.md N15.
Deprecated API usage: large amounts of deprecated API usage including EncryptedSharedPreferences, WifiConfiguration, NioEventLoopGroup. See docs/ISSUES.md N13.
Test coverage gap: core business logic (processVpnTraffic, forwardViaSocks5) lacks test coverage. See docs/ISSUES.md N8.

Files:

• android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt

**/*.{kt,go}

📄 CodeRabbit inference engine (CLAUDE.md)

Critical defect: connection pool cleanup race condition - connection state may change between read and write locks. See docs/ISSUES.md H5.

Files:

• android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt

android/**

📄 CodeRabbit inference engine (CLAUDE.md)

Build validation gate: make android-build must pass.

Files:

• android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt

🔇 Additional comments (1)

android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt (1)

608-627: 📐 Maintainability & Code Quality

验证 Android 构建门禁。

请在合并前确认 make android-build 成功通过。

As per coding guidelines, android/**: make android-build must pass.

Source: Coding guidelines

---

📝 Walkthrough

Summary by CodeRabbit

• 功能优化

  • 配对按钮新增平滑的内容切换动画。
  • 配对处理中显示加载指示器，完成后显示“配对”文本，状态变化更加直观。

• 体验改进

  • 优化配对状态切换过程，减少界面内容突变和视觉冲突。

Walkthrough

配对按钮改用 AnimatedContent，根据 targetState 在加载指示器和“配对”文本之间切换。新增记录说明动画作用域内应使用 targetState 计算派生视图状态。

Changes

配对按钮动画过渡

Layer / File(s)	Summary
配对状态内容切换 android/app/src/main/java/com/netproxy/gateway/ui/screens/MainScreen.kt, .Jules/palette.md	配对按钮使用 AnimatedContent 根据 targetState 显示加载指示器或“配对”文本。学习记录补充了动画作用域内使用目标状态的准则。

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• 01luyicheng/NetProxyGateway#144：同样重构 MainScreen.kt，使用 AnimatedContent 和动画作用域内的 targetState。
• 01luyicheng/NetProxyGateway#191：同样修改配对按钮的 AnimatedContent 状态过渡。
• 01luyicheng/NetProxyGateway#195：同样将配对按钮切换为 AnimatedContent。

Suggested labels: 🕐 10-20 Minutes

Suggested reviewers: copilot

Poem

我是小兔，蹦过代码田，
配对按钮开始轻轻变。
targetState 指路不乱，
加载与文字平稳相见，
动画月光落在界面边。

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	标题准确概括了配对按钮的状态过渡和颜色对比度优化。
Description check	✅ Passed	描述说明了使用 AnimatedContent 和 LocalContentColor.current 的变更及其视觉和可访问性目标。
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands.}

[Luyicheng-Agent]

快速扫描结论：NO CRITICAL BUG

对 MainScreen.kt 中 PairingSection 的改动做了崩溃/状态丢失扫描。

核查项

• AnimatedContent(targetState = uiState.isPairingInProgress, ...)：targetState 为 Boolean，标准用法，无递归/无限动画循环风险；快速来回切换由 AnimatedContent 的过渡规约处理。
• LocalContentColor.current：在按钮内容中读取，由 Button 按 enabled/disabled 提供，非空 Color，无空指针；相较原硬编码 MaterialTheme.colorScheme.onPrimary，反而在按钮 disabled（配对进行中 enabled = ... && !uiState.isPairingInProgress）时对比度更正确。
• 无 force-unwrap / !!：isPairing 为非空 Boolean，分支内均为非空组合，无 NPE 路径。
• 状态丢失：uiState.isPairingInProgress 为单一驱动状态，AnimatedContent 自动管理过渡态，无状态丢失。
• 重组风暴：仅依赖 uiState.isPairingInProgress，未引入高频重组源。

一点小观察（非关键，纯视觉）

配对态与非配对态内容尺寸不同（文本 vs 进度条+间距+文本），AnimatedContent 默认过渡可能产生轻微布局跳动；如需更平滑可显式指定 SizeTransform，纯属体验优化，不影响正确性。

判定：未发现崩溃、空指针、无限动画循环或状态丢失，可合并。（PR #195 / #192 为近乎相同的改动，同样未发现关键问题。）