增加稳定版arm支持

修复稳定版面板显示屏蔽协议状态不一致问题
2026-09-28 15:46:38 +08:00 · 2025-11-25 09:43:32 +08:00 · 2025-11-25 09:21:36 +08:00 · 2025-11-25 09:18:40 +08:00
564 changed files with 21836 additions and 103172 deletions
@@ -1,84 +0,0 @@
-{
-  "hooks": {
-    "PostToolUse": [
-      {
-        "matcher": "Task",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code post-task"
-          }
-        ]
-      },
-      {
-        "matcher": "TodoWrite",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code post-todo"
-          }
-        ]
-      }
-    ],
-    "PreToolUse": [
-      {
-        "matcher": "Task",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code pre-task"
-          }
-        ]
-      }
-    ],
-    "SessionEnd": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code session-end"
-          }
-        ]
-      }
-    ],
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code session-start"
-          }
-        ]
-      }
-    ],
-    "Stop": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code stop"
-          }
-        ]
-      }
-    ],
-    "UserPromptSubmit": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "entire hooks claude-code user-prompt-submit"
-          }
-        ]
-      }
-    ]
-  },
-  "permissions": {
-    "deny": [
-      "Read(./.entire/metadata/**)"
-    ]
-  }
-}
@@ -1,24 +0,0 @@
-# Session Context
-
-Session ID: ses_34dfc44d5ffedfgo4G9wPONyXC
-Commit Message: 在agent.md里规定，每次计划都必须写一个计划文档，md格式，按序号增加和以计划的总结命名，每次完成一个任务做好标记
-
-## Prompts
-
-### Prompt 1
-
-在agent.md里规定，每次计划都必须写一个计划文档，md格式，按序号增加和以计划的总结命名，每次完成一个任务做好标记
-
-## Summary
-
-已按你的要求更新完成。
-
-我在 `AGENTS.md` 里新增了 `## PLAN DOCUMENT RULE` 章节，内容包括：
-
- 每次新实现计划都必须有独立 Markdown 计划文档  
- 计划文档统一放在 `plans/` 目录  
- 文件名采用递增序号 + 计划摘要：`NNN-<plan-summary>.md`  
- 序号必须每次 +1  
- 文档内使用任务清单，并在每个任务完成后立即打勾标记  
-
-修改位置：`AGENTS.md`
@@ -1 +0,0 @@
-在agent.md里规定，每次计划都必须写一个计划文档，md格式，按序号增加和以计划的总结命名，每次完成一个任务做好标记
@@ -1,11 +0,0 @@
-已按你的要求更新完成。
-
-我在 `AGENTS.md` 里新增了 `## PLAN DOCUMENT RULE` 章节，内容包括：
-
- 每次新实现计划都必须有独立 Markdown 计划文档  
- 计划文档统一放在 `plans/` 目录  
- 文件名采用递增序号 + 计划摘要：`NNN-<plan-summary>.md`  
- 序号必须每次 +1  
- 文档内使用任务清单，并在每个任务完成后立即打勾标记  
-
-修改位置：`AGENTS.md`
@@ -1,71 +0,0 @@
-# Session Context
-
-Session ID: ses_34dfda207ffeiBV2rCgJW708ip
-Commit Message: 配置下发也没兼容，请全量检查一下，哪些功能需要一起改造
-
-## Prompts
-
-### Prompt 1
-
-211 任务的没有完全完成1. 选择IP后诊断还会诊断默认IP
-2. 选择隧道出口IP后，入口还是会链接默认IP，没有链接选择的IP
-请分析后制定修复计划
-
-### Prompt 2
-
-配置下发也没兼容，请全量检查一下，哪些功能需要一起改造
-
-## Summary
-
-你提得很对，我按“配置下发全链路”重新过了一遍（只读分析）。结论是：**需要一起改造的不是一个点，而是“诊断链路 + 重部署链路 + 回归测试链路”**。
-
-目前状态可以分成三类：
-
- **已兼容（创建/更新时下发）**
-  - 隧道创建/更新时，`connectIp` 已进入运行时下发选择逻辑（`selectTunnelDialHost`）。
-  - 本地/联邦 runtime apply 都会吃 `target.ConnectIP`（前提是 state 里有值）。
-  - 参考：`go-backend/internal/http/handler/mutations.go:2588`, `go-backend/internal/http/handler/mutations.go:2348`
-
- **未兼容（你反馈的核心问题）**
-  - 诊断链路未传 `connectIp`，导致总走默认IP。
-  - 参考：`go-backend/internal/http/handler/control_plane.go:75`, `go-backend/internal/http/handler/control_plane.go:1102`
-
- **半兼容（配置重建时丢字段）**
-  - 重部署时从 DB 重建 runtime state，**没把 `ConnectIP` 带回去**，所以 redeploy 后会回退默认IP。
-  - 参考：`go-backend/internal/http/handler/mutations.go:883`, `go-backend/internal/http/handler/mutations.go:897`
-
---
-
-**需要一起改造的功能范围（建议一次性做完）**
-
- `诊断（非流式 + 流式）`
-  - 隧道诊断、转发诊断都要改（共用 `prepare*Diagnosis` + `appendChainHopDiagnosis`）。
-  - 流式 start 预览项也要改，否则 UI 一开始仍显示默认IP。
-  - 目标文件：`go-backend/internal/http/handler/control_plane.go`, `go-backend/internal/http/handler/diagnosis_stream.go`
-
- `配置下发（重部署路径）`
-  - 单条重部署、批量重部署都依赖 `reconstructTunnelState`，必须补 `ConnectIP` 回填。
-  - 目标文件：`go-backend/internal/http/handler/mutations.go`
-
- `联邦节点运行时下发一致性`
-  - 逻辑本身已支持 `ConnectIP`，但受上一步 state 丢字段影响；修复后自动恢复一致。
-  - 重点验证：remote middle hop `ApplyRole.Targets` 的 Host 选取。
-
- `回归测试`
-  - 新增诊断用例：选了 `connectIp` 后，`targetIp` 必须是选中值（tunnel/forward + stream start/item）。
-  - 新增重部署用例：redeploy 后仍使用 `connectIp`，不回退默认IP。
-  - 目标文件建议：`go-backend/tests/contract/diagnosis_contract_test.go`，补 handler 级或 contract 级 redeploy 用例。
-
---
-
-**实施计划（修复包）**
-
-1. 修 `diagnosis` 调用链：所有 `resolveChainProbeTarget` 调用传入 `workItem.toNode.ConnectIP`。  
-2. 修 `reconstructTunnelState`：出口节点和中继节点都回填 `ConnectIP`。  
-3. 补测试：覆盖“诊断用选中IP”“重部署不丢IP”“connectIp为空仍走默认”的三组场景。  
-4. 联调验证：创建/更新、诊断、单重部署、批量重部署、联邦节点场景各跑一遍。
-
---
-
-我建议按这个范围做成一次完整修复（避免只修诊断后你再次遇到“重部署又回退”的问题）。  
-如果你同意，我下一步就按这个“全量改造范围”进入实施。
@@ -1,7 +0,0 @@
-211 任务的没有完全完成1. 选择IP后诊断还会诊断默认IP
-2. 选择隧道出口IP后，入口还是会链接默认IP，没有链接选择的IP
-请分析后制定修复计划
-
---
-
-配置下发也没兼容，请全量检查一下，哪些功能需要一起改造
@@ -1,52 +0,0 @@
-你提得很对，我按“配置下发全链路”重新过了一遍（只读分析）。结论是：**需要一起改造的不是一个点，而是“诊断链路 + 重部署链路 + 回归测试链路”**。
-
-目前状态可以分成三类：
-
- **已兼容（创建/更新时下发）**
-  - 隧道创建/更新时，`connectIp` 已进入运行时下发选择逻辑（`selectTunnelDialHost`）。
-  - 本地/联邦 runtime apply 都会吃 `target.ConnectIP`（前提是 state 里有值）。
-  - 参考：`go-backend/internal/http/handler/mutations.go:2588`, `go-backend/internal/http/handler/mutations.go:2348`
-
- **未兼容（你反馈的核心问题）**
-  - 诊断链路未传 `connectIp`，导致总走默认IP。
-  - 参考：`go-backend/internal/http/handler/control_plane.go:75`, `go-backend/internal/http/handler/control_plane.go:1102`
-
- **半兼容（配置重建时丢字段）**
-  - 重部署时从 DB 重建 runtime state，**没把 `ConnectIP` 带回去**，所以 redeploy 后会回退默认IP。
-  - 参考：`go-backend/internal/http/handler/mutations.go:883`, `go-backend/internal/http/handler/mutations.go:897`
-
---
-
-**需要一起改造的功能范围（建议一次性做完）**
-
- `诊断（非流式 + 流式）`
-  - 隧道诊断、转发诊断都要改（共用 `prepare*Diagnosis` + `appendChainHopDiagnosis`）。
-  - 流式 start 预览项也要改，否则 UI 一开始仍显示默认IP。
-  - 目标文件：`go-backend/internal/http/handler/control_plane.go`, `go-backend/internal/http/handler/diagnosis_stream.go`
-
- `配置下发（重部署路径）`
-  - 单条重部署、批量重部署都依赖 `reconstructTunnelState`，必须补 `ConnectIP` 回填。
-  - 目标文件：`go-backend/internal/http/handler/mutations.go`
-
- `联邦节点运行时下发一致性`
-  - 逻辑本身已支持 `ConnectIP`，但受上一步 state 丢字段影响；修复后自动恢复一致。
-  - 重点验证：remote middle hop `ApplyRole.Targets` 的 Host 选取。
-
- `回归测试`
-  - 新增诊断用例：选了 `connectIp` 后，`targetIp` 必须是选中值（tunnel/forward + stream start/item）。
-  - 新增重部署用例：redeploy 后仍使用 `connectIp`，不回退默认IP。
-  - 目标文件建议：`go-backend/tests/contract/diagnosis_contract_test.go`，补 handler 级或 contract 级 redeploy 用例。
-
---
-
-**实施计划（修复包）**
-
-1. 修 `diagnosis` 调用链：所有 `resolveChainProbeTarget` 调用传入 `workItem.toNode.ConnectIP`。  
-2. 修 `reconstructTunnelState`：出口节点和中继节点都回填 `ConnectIP`。  
-3. 补测试：覆盖“诊断用选中IP”“重部署不丢IP”“connectIp为空仍走默认”的三组场景。  
-4. 联调验证：创建/更新、诊断、单重部署、批量重部署、联邦节点场景各跑一遍。
-
---
-
-我建议按这个范围做成一次完整修复（避免只修诊断后你再次遇到“重部署又回退”的问题）。  
-如果你同意，我下一步就按这个“全量改造范围”进入实施。
@@ -1 +0,0 @@
-提交全部变更并且push，创建pr合并，发布新tag，alpha版本
@@ -1,10 +0,0 @@
-已完成：
-
-1. **提交**: `fix: apply custom IP binding to forward and tunnel chain services` (e383359)
-2. **PR**: [#247](https://github.com/Sagit-chu/flvx/pull/247) - 已合并
-3. **Tag**: `2.1.7-alpha7` 已创建并推送
-
-新功能：
- 自定义 IP 绑定支持（节点、隧道、转发）
- 转发列表紧凑模式与隧道组折叠/排序
- 迁移测试增强
@@ -1,40 +0,0 @@
-# Session Context
-
-Session ID: ses_34e68d081ffeyr3uWQwm5venHp
-Commit Message: 实施
-
-## Prompts
-
-### Prompt 1
-
-211任务中，如果选择了指定的入口IP或者出口IP，在节点上应该只监听这个IP地址，而不再是[::]，请检查
-
-### Prompt 2
-
-connectIp 同时用于“上游拨号目标 + 本节点监听绑定”
-
-### Prompt 3
-
-实施
-
-## Summary
-
-已实施完成，并且按你确认的语义实现为：`connectIp` 同时用于“上游拨号目标 + 本节点监听绑定”。
-
- 转发服务下发现在会优先使用 `forward_port.in_ip` 作为监听地址，不再固定用节点默认 `[::]`。
- 隧道服务下发现在会优先使用 `connectIp` 作为监听地址；为空时才回退到节点默认监听地址。
- IPv6 监听地址统一通过 `processServerAddress(...)` 处理，确保带方括号格式正确。
-
-改动位置：
- `go-backend/internal/http/handler/control_plane.go:284`
- `go-backend/internal/http/handler/control_plane.go:1306`
- `go-backend/internal/http/handler/mutations.go:2646`
-
-新增测试：
- `go-backend/internal/http/handler/control_plane_test.go:69`
- `go-backend/internal/http/handler/control_plane_test.go:86`
- `go-backend/internal/http/handler/dual_stack_test.go:33`
- `go-backend/internal/http/handler/dual_stack_test.go:49`
-
-验证结果：
- 已运行 `go test ./internal/http/handler/...`，全部通过。
@@ -1,9 +0,0 @@
-211任务中，如果选择了指定的入口IP或者出口IP，在节点上应该只监听这个IP地址，而不再是[::]，请检查
-
---
-
-connectIp 同时用于“上游拨号目标 + 本节点监听绑定”
-
---
-
-实施
@@ -1,19 +0,0 @@
-已实施完成，并且按你确认的语义实现为：`connectIp` 同时用于“上游拨号目标 + 本节点监听绑定”。
-
- 转发服务下发现在会优先使用 `forward_port.in_ip` 作为监听地址，不再固定用节点默认 `[::]`。
- 隧道服务下发现在会优先使用 `connectIp` 作为监听地址；为空时才回退到节点默认监听地址。
- IPv6 监听地址统一通过 `processServerAddress(...)` 处理，确保带方括号格式正确。
-
-改动位置：
- `go-backend/internal/http/handler/control_plane.go:284`
- `go-backend/internal/http/handler/control_plane.go:1306`
- `go-backend/internal/http/handler/mutations.go:2646`
-
-新增测试：
- `go-backend/internal/http/handler/control_plane_test.go:69`
- `go-backend/internal/http/handler/control_plane_test.go:86`
- `go-backend/internal/http/handler/dual_stack_test.go:33`
- `go-backend/internal/http/handler/dual_stack_test.go:49`
-
-验证结果：
- 已运行 `go test ./internal/http/handler/...`，全部通过。
@@ -1 +0,0 @@
-提交全部变更并且push，创建pr合并，发布新tag，alpha版本
@@ -1,5 +0,0 @@
-✅ 完成！
-
- 提交: `9cf9f4f` (feat: add comprehensive migration test for legacy columns)
- PR: [#245](https://github.com/Sagit-chu/flvx/pull/245) 已合并
- 新 tag: `2.1.7-alpha6` 已发布
@@ -1,20 +0,0 @@
-# Session Context
-
-Session ID: ses_34ebc12c1ffePWN7yC0z9iz5Lw
-Commit Message: 合并pr，然后发布新tag，alpha版本
-
-## Prompts
-
-### Prompt 1
-
-提交全部变更并且push
-
-### Prompt 2
-
-合并pr，然后发布新tag，alpha版本
-
-## Summary
-
-已完成：
- PR #244 已合并到 main
- 新 tag `2.1.7-alpha5` 已创建并推送
@@ -1,5 +0,0 @@
-提交全部变更并且push
-
---
-
-合并pr，然后发布新tag，alpha版本
@@ -1,3 +0,0 @@
-已完成：
- PR #244 已合并到 main
- 新 tag `2.1.7-alpha5` 已创建并推送
@@ -1,44 +0,0 @@
-# Session Context
-
-Session ID: ses_34ec18cadffeoVVSjfPXGJaxBu
-Commit Message: 再做一轮“跨表全量列对比（model vs 旧库补列逻辑）
-
-## Prompts
-
-### Prompt 1
-
-211任务全量再逐一确认一下是否全部完成，并且功能完成
-
-### Prompt 2
-
-添加额外ip的时候报错：SQL logic error: no such column: extra_ips (1)
-
-### Prompt 3
-
-全量排查一下还有没有类似的bug
-
-### Prompt 4
-
-再做一轮“跨表全量列对比（model vs 旧库补列逻辑）
-
-## Summary
-
-已完成这一轮“跨表全量列对比（model vs 旧库补列逻辑）”，并做了可执行验证。
-
-我做了什么：
-
- 对比了 `model.Node` / `model.Tunnel` 字段与 `prepareSQLiteLegacyColumns` 的补列清单。
- 结论：
-  - `Node` 目前应补的历史增量列：`server_ip_v4`, `server_ip_v6`, `extra_ips`, `tcp_listen_addr`, `udp_listen_addr`, `inx`, `is_remote`, `remote_url`, `remote_token`, `remote_config`
-  - `Tunnel` 应补：`inx`, `ip_preference`
- 我已把这个对齐结果固化为回归测试，新增了一个“更老版本库”场景验证：
-  - 新测试：`TestOpenMigratesVeryLegacyNodeAndTunnelColumns`
-  - 文件：`go-backend/tests/contract/migration_contract_test.go`
-  - 该测试从极简旧表结构启动，验证上述所有列都会被自动补齐。
- 测试结果：通过
-  - `go test ./tests/contract -run "TestOpenMigratesLegacyNodeDualStackColumns|TestOpenMigratesVeryLegacyNodeAndTunnelColumns"`
-
-最终结论（本轮排查范围内）：
-
- **Node/Tunnel 这条旧库升级链路已对齐且有测试兜底**。
- 你这类 “no such column” 的同类风险，针对这两个核心表已经基本封住。
@@ -1,13 +0,0 @@
-211任务全量再逐一确认一下是否全部完成，并且功能完成
-
---
-
-添加额外ip的时候报错：SQL logic error: no such column: extra_ips (1)
-
---
-
-全量排查一下还有没有类似的bug
-
---
-
-再做一轮“跨表全量列对比（model vs 旧库补列逻辑）
@@ -1,19 +0,0 @@
-已完成这一轮“跨表全量列对比（model vs 旧库补列逻辑）”，并做了可执行验证。
-
-我做了什么：
-
- 对比了 `model.Node` / `model.Tunnel` 字段与 `prepareSQLiteLegacyColumns` 的补列清单。
- 结论：
-  - `Node` 目前应补的历史增量列：`server_ip_v4`, `server_ip_v6`, `extra_ips`, `tcp_listen_addr`, `udp_listen_addr`, `inx`, `is_remote`, `remote_url`, `remote_token`, `remote_config`
-  - `Tunnel` 应补：`inx`, `ip_preference`
- 我已把这个对齐结果固化为回归测试，新增了一个“更老版本库”场景验证：
-  - 新测试：`TestOpenMigratesVeryLegacyNodeAndTunnelColumns`
-  - 文件：`go-backend/tests/contract/migration_contract_test.go`
-  - 该测试从极简旧表结构启动，验证上述所有列都会被自动补齐。
- 测试结果：通过
-  - `go test ./tests/contract -run "TestOpenMigratesLegacyNodeDualStackColumns|TestOpenMigratesVeryLegacyNodeAndTunnelColumns"`
-
-最终结论（本轮排查范围内）：
-
- **Node/Tunnel 这条旧库升级链路已对齐且有测试兜底**。
- 你这类 “no such column” 的同类风险，针对这两个核心表已经基本封住。
@@ -1,14 +0,0 @@
-# Session Context
-
-Session ID: ses_34eec2495ffeJvDq7SlEs8mRoH
-Commit Message: 提交全部变更并且push，创建pr
-
-## Prompts
-
-### Prompt 1
-
-提交全部变更并且push，创建pr
-
-## Summary
-
-已提交并推送，PR已创建: https://github.com/Sagit-chu/flvx/pull/new/opencode/mighty-nebula
@@ -1 +0,0 @@
-提交全部变更并且push，创建pr
@@ -1 +0,0 @@
-已提交并推送，PR已创建: https://github.com/Sagit-chu/flvx/pull/new/opencode/mighty-nebula
@@ -1,14 +0,0 @@
-# Session Context
-
-Session ID: ses_34f0fe1d2ffeH3PJRyokYati7T
-Commit Message: 把main更新到本分支
-
-## Prompts
-
-### Prompt 1
-
-把main更新到本分支
-
-## Summary
-
-已完成 `origin/main` 合并到当前分支（Fast-forward）。之前的更改已恢复，`forward.tsx` 自动合并成功。
@@ -1 +0,0 @@
-把main更新到本分支
@@ -1 +0,0 @@
-已完成 `origin/main` 合并到当前分支（Fast-forward）。之前的更改已恢复，`forward.tsx` 自动合并成功。
@@ -1,11 +0,0 @@
-探索节点API和数据访问层的完整实现：
-
-1. 在 `go-backend/internal/store/repo/` 查找节点创建/更新的函数
-2. 查找节点数据如何返回给前端（JSON序列化）
-3. 查找 `nodeRecord` 结构体的定义和使用
-4. 理解 ServerIP/ServerIPV4/ServerIPV6 字段如何被处理
-
-返回：
- 节点CRUD相关的Repository方法
- 节点数据返回给前端的格式
- 扩展节点IP字段需要改动的位置
@@ -1,215 +0,0 @@
-Based on my thorough exploration, here's a comprehensive analysis of the node API and data access layer:
-
---
-
-## 节点API和数据访问层完整分析
-
-### 1. 节点CRUD相关Repository方法
-
-#### 核心方法 (`go-backend/internal/store/repo/`)
-
-| 方法 | 文件位置 | 功能 |
-|------|----------|------|
-| `CreateNode()` | `repository_mutations.go:199` | 创建节点，处理 serverIP/serverIPV4/serverIPV6 |
-| `UpdateNode()` | `repository_mutations.go:241` | 更新节点，包含所有IP字段 |
-| `DeleteNodeCascade()` | `repository_mutations.go:299` | 级联删除节点（关联 ForwardPort、ChainTunnel、FederationTunnelBinding） |
-| `GetNodeByID()` | `repository.go:555` | 通过ID获取节点 |
-| `GetNodeBySecret()` | `repository.go:540` | 通过Secret获取节点 |
-| `GetNodeStatusFields()` | `repository_mutations.go:229` | 获取节点状态字段 |
-| `GetNodeSecret()` | `repository_mutations.go:263` | 获取节点密钥 |
-| `GetNodeRemoteFields()` | `repository_mutations.go:317` | 获取远程节点字段 |
-| `GetNodePortRange()` | `repository_mutations.go:336` | 获取节点端口范围 |
-| `UpdateNodeOrder()` | `repository_mutations.go:287` | 更新节点排序 |
-| `UpdateNodeOnline()` | `repository.go:570` | 更新节点在线状态 |
-| `UpdateNodeStatus()` | `repository.go:580` | 更新节点状态 |
-| `ListNodes()` | `repository.go:625` | 列出所有节点（返回JSON map格式） |
-| `GetNodeRecord()` | `repository_control.go:131` | 获取 NodeRecord 视图对象 |
-| `CreateRemoteNode()` | `repository_federation.go:266` | 创建远程节点（联邦场景） |
-| `exportNodes()` | `repository.go:1660` | 导出节点数据（用于备份） |
-| `importNodes()` | `repository.go:2016` | 导入节点数据（用于恢复） |
-
---
-
-### 2. 节点数据结构定义
-
-#### GORM模型 (`model.Node` - 数据库存储)
-**文件:** `/go-backend/internal/store/model/model.go:59-82`
-```go
-type Node struct {
-    ID            int64          `gorm:"primaryKey;autoIncrement"`
-    Name          string         `gorm:"type:varchar(100);not null"`
-    Secret        string         `gorm:"type:varchar(100);not null"`
-    ServerIP      string         `gorm:"column:server_ip;type:varchar(100);not null"`
-    ServerIPV4    sql.NullString `gorm:"column:server_ip_v4;type:varchar(100)"`  // 注意：V大写
-    ServerIPV6    sql.NullString `gorm:"column:server_ip_v6;type:varchar(100)"`
-    // ... 其他字段
-}
-```
-
-#### 控制平面视图 (`model.NodeRecord`)
-**文件:** `/go-backend/internal/store/model/model.go:515-531`
-```go
-type NodeRecord struct {
-    ID            int64
-    Name          string
-    ServerIP      string
-    ServerIPv4    string   // 注意：v小写
-    ServerIPv6    string
-    Status        int
-    PortRange     string
-    // ... 其他字段
-}
-```
-
-#### JSON导出格式 (`model.NodeBackup`)
-**文件:** `/go-backend/internal/store/model/model.go:333-356`
-```go
-type NodeBackup struct {
-    ID            int64  `json:"id"`
-    Name          string `json:"name"`
-    ServerIP      string `json:"serverIp"`
-    ServerIPv4    string `json:"serverIpV4,omitempty"`
-    ServerIPv6    string `json:"serverIpV6,omitempty"`
-    // ... 其他字段
-}
-```
-
-#### Handler层别名
-**文件:** `/go-backend/internal/http/handler/control_plane.go:25`
-```go
-type nodeRecord = model.NodeRecord  // 类型别名
-```
-
---
-
-### 3. 节点数据返回给前端的格式
-
-#### ListNodes API (`repository.go:625-652`)
-```go
-// 返回 map[string]interface{} 格式
-items = append(items, map[string]interface{}{
-    "id": n.ID, "inx": n.Inx, "name": n.Name,
-    "ip": n.ServerIP, "serverIp": n.ServerIP,      // ip和serverIp都返回
-    "serverIpV4":    nullableString(n.ServerIPV4),
-    "serverIpV6":    nullableString(n.ServerIPV6),
-    "port":          n.Port,
-    "tcpListenAddr": n.TCPListenAddr,
-    "udpListenAddr": n.UDPListenAddr,
-    "version":       nullableString(n.Version),
-    "http":          n.HTTP, "tls": n.TLS, "socks": n.Socks,
-    "status": n.Status, "isRemote": n.IsRemote,
-    // ...
-})
-```
-
-#### API端点
-| 端点 | Handler | 功能 |
-|------|---------|------|
-| `POST /api/v1/node/list` | `h.nodeList` | 列出节点 |
-| `POST /api/v1/node/create` | `h.nodeCreate` | 创建节点 |
-| `POST /api/v1/node/update` | `h.nodeUpdate` | 更新节点 |
-| `POST /api/v1/node/delete` | `h.nodeDelete` | 删除节点 |
-
---
-
-### 4. ServerIP/ServerIPV4/ServerIPV6 字段处理逻辑
-
-#### 字段命名约定
-| 层级 | 字段名 | 数据库列名 |
-|------|--------|-----------|
-| `model.Node` | `ServerIPV4`, `ServerIPV6` | `server_ip_v4`, `server_ip_v6` |
-| `model.NodeRecord` | `ServerIPv4`, `ServerIPv6` | - (内存结构) |
-| `model.NodeBackup` | `ServerIPv4`, `ServerIPv6` | - (JSON) |
-| 前端JSON | `serverIpV4`, `serverIpV6` | - |
-
-#### 模型转换函数 (`repository_control.go:161-201`)
-```go
-func nodeRecordFromModel(n *model.Node) *model.NodeRecord {
-    rec := &model.NodeRecord{
-        ID:            n.ID,
-        Name:          n.Name,
-        ServerIP:      n.ServerIP,
-        // ...
-    }
-    if n.ServerIPV4.Valid {
-        rec.ServerIPv4 = strings.TrimSpace(n.ServerIPV4.String)
-    }
-    if n.ServerIPV6.Valid {
-        rec.ServerIPv6 = strings.TrimSpace(n.ServerIPV6.String)
-    }
-    // ...
-}
-```
-
-#### Dual-Stack辅助函数 (`mutations.go:2715-2772`)
-```go
-// 判断节点是否支持IPv4
-func nodeSupportsV4(node *nodeRecord) bool {
-    if strings.TrimSpace(node.ServerIPv4) != "" { return true }
-    if strings.TrimSpace(node.ServerIPv6) != "" { return false }
-    // 回退到 ServerIP 判断
-    legacy := strings.Trim(strings.TrimSpace(node.ServerIP), "[]")
-    if ip := net.ParseIP(legacy); ip != nil {
-        return ip.To4() != nil
-    }
-    return true
-}
-
-// 选择IPv4地址（优先显式字段，回退ServerIP）
-func pickNodeAddressV4(node *nodeRecord) string {
-    if v := strings.TrimSpace(node.ServerIPv4); v != "" { return v }
-    return strings.TrimSpace(node.ServerIP)
-}
-```
-
---
-
-### 5. 扩展节点IP字段需要改动的位置
-
-如果要添加新的IP字段（如 `ServerIPV4Alt`），需要修改以下位置：
-
-#### A. 模型层 (`go-backend/internal/store/model/model.go`)
-1. **`model.Node`** - 添加 GORM 字段定义（约第64行）
-2. **`model.NodeRecord`** - 添加视图字段（约第520行）
-3. **`model.NodeBackup`** - 添加JSON字段（约第338行）
-
-#### B. Repository层 (`go-backend/internal/store/repo/`)
-1. **`repository_mutations.go`**
-   - `CreateNode()` 参数和赋值（约第199-227行）
-   - `UpdateNode()` 参数和Updates map（约第241-261行）
-
-2. **`repository_control.go`**
-   - `nodeRecordFromModel()` 转换逻辑（约第161-201行）
-
-3. **`repository_federation.go`**
-   - `CreateRemoteNode()` 参数和赋值（约第266-294行）
-
-4. **`repository.go`**
-   - `ListNodes()` JSON返回格式（约第625-652行）
-   - `exportNodes()` 导出逻辑（约第1660-1700行）
-   - `importNodes()` 导入逻辑（约第2016-2057行）
-   - `prepareSQLiteLegacyColumns()` 迁移逻辑（约第263行）
-
-#### C. Handler层 (`go-backend/internal/http/handler/`)
-1. **`mutations.go`**
-   - `nodeCreate()` 请求参数解析（约第234-279行）
-   - `nodeUpdate()` 请求参数解析（约第281-336行）
-   - `nodeSupportsV4/V6()` 函数逻辑（约第2715-2772行）
-   - `pickNodeAddressV4/V6()` 函数逻辑
-
-#### D. 测试层 (`go-backend/tests/contract/`)
-所有 contract test 中的 `INSERT INTO node` 语句需要更新字段列表
-
---
-
-### 关键文件汇总
-
-| 文件 | 用途 |
-|------|------|
-| `/go-backend/internal/store/model/model.go` | 数据模型定义 |
-| `/go-backend/internal/store/repo/repository_mutations.go` | CRUD操作实现 |
-| `/go-backend/internal/store/repo/repository_control.go` | 控制平面查询+模型转换 |
-| `/go-backend/internal/store/repo/repository_federation.go` | 联邦节点操作 |
-| `/go-backend/internal/store/repo/repository.go` | 核心查询+导出导入 |
-| `/go-backend/internal/http/handler/mutations.go` | HTTP API处理器 |
-| `/go-backend/internal/http/handler/control_plane.go` | 控制平面API |
@@ -1,11 +0,0 @@
-探索隧道链路构建时下一跳连接地址的选择流程：
-
-1. 在 `control_plane.go` 中查找隧道链路构建逻辑
-2. 查找 `applyTunnelRuntime` 或类似函数如何向节点发送命令
-3. 理解 hop 节点如何连接到下一个节点（连接地址从哪里来）
-4. 查找 `ChainTunnel` 表的 `Port` 字段如何被使用
-
-返回：
- 隧道链路配置发送到节点的代码位置
- 下一跳连接地址是如何确定的
- 修改连接地址需要改动的关键位置
@@ -1,173 +0,0 @@
-根据我的分析，以下是隧道链路构建时下一跳连接地址选择流程的完整报告：
-
---
-
-## 隧道链路构建流程分析报告
-
-### 1. 隧道链路配置发送到节点的代码位置
-
-**主函数**: `applyTunnelRuntime()` 
- 文件: `go-backend/internal/http/handler/mutations.go`
- 行号: 2454-2521
-
-**核心流程**:
-
-```
-applyTunnelRuntime (L2454)
-├── 入口节点: 发送 AddChains 命令 (L2474)
-├── 跳转节点: 发送 AddChains (L2496) + AddService (L2502) 命令
-└── 出口节点: 发送 AddService 命令 (L2514)
-```
-
-**配置构建函数**:
-| 函数 | 位置 | 作用 |
-|------|------|------|
-| `buildTunnelChainConfig()` | L2567-2624 | 构建转发链配置 |
-| `buildTunnelChainServiceConfig()` | L2626-2652 | 构建服务配置 |
-| `selectTunnelDialHost()` | L2654-2699 | **选择下一跳连接地址** |
-
---
-
-### 2. 下一跳连接地址是如何确定的
-
-**地址选择核心函数**: `selectTunnelDialHost()` (L2654-2699)
-
-```go
-// 关键逻辑 (简化版)
-func selectTunnelDialHost(fromNode, toNode *nodeRecord, ipPreference string) (string, error) {
-    // 1. 检测源节点和目标节点的 IPv4/IPv6 支持
-    fromV4 := nodeSupportsV4(fromNode)
-    fromV6 := nodeSupportsV6(fromNode)
-    toV4 := nodeSupportsV4(toNode)
-    toV6 := nodeSupportsV6(toNode)
-    
-    // 2. 根据偏好选择地址
-    switch ipPreference {
-    case "v6":  // 优先 IPv6
-        if fromV6 && toV6 { return pickNodeAddressV6(toNode) }
-        if fromV4 && toV4 { return pickNodeAddressV4(toNode) }
-    case "v4":  // 优先 IPv4
-        if fromV4 && toV4 { return pickNodeAddressV4(toNode) }
-        if fromV6 && toV6 { return pickNodeAddressV6(toNode) }
-    default:    // 默认优先 IPv4
-        if fromV4 && toV4 { return pickNodeAddressV4(toNode) }
-        if fromV6 && toV6 { return pickNodeAddressV6(toNode) }
-    }
-    // 3. 不兼容时报错
-    return "", fmt.Errorf("节点链路不兼容")
-}
-```
-
-**地址选择优先级** (在 `pickNodeAddressV4/V6` 中, L2755-2773):
- **IPv4**: `ServerIPv4` > `ServerIP` (旧字段)
- **IPv6**: `ServerIPv6` > `ServerIP` (旧字段)
-
-**端口来源** (在 `buildTunnelChainConfig` 中, L2585-2588):
-```go
-port := target.Port  // 来自 ChainTunnel.Port 字段
-if port <= 0 {
-    return nil, errors.New("节点端口不能为空")
-}
-```
-
---
-
-### 3. ChainTunnel.Port 字段的使用流程
-
-**数据模型** (`model.go` L127-138):
-```go
-type ChainTunnel struct {
-    ID        int64
-    TunnelID  int64
-    ChainType string      // "1"=入口, "2"=跳转, "3"=出口
-    NodeID    int64
-    Port      sql.NullInt64  // ★ 连接端口
-    Strategy  sql.NullString
-    Inx       sql.NullInt64  // 跳转序号
-    Protocol  sql.NullString
-}
-```
-
-**Port 字段流转**:
-
-```
-创建隧道时
-    │
-    ▼
-prepareTunnelCreateState (L1970)
-├── 出口节点: 从请求读取 port，若为空则调用 PickNodePortTx 自动分配
-├── 跳转节点: 从请求读取 port，若为空则调用 PickNodePortTx 自动分配
-    │
-    ▼
-replaceTunnelChainsTx (L2775) 
-└── CreateChainTunnelTx 写入数据库 (L2809, L2837)
-    │
-    ▼
-读取/重建状态时
-    │
-    ▼
-ListChainNodesForTunnel (repository_control.go L280)
-└── 从 chain_tunnel 表读取 Port 字段 (L295)
-    │
-    ▼
-reconstructTunnelState (L845)
-└── 将 Port 复制到 tunnelRuntimeNode.Port (L887, L901)
-    │
-    ▼
-buildTunnelChainConfig (L2567)
-└── 使用 target.Port 构建连接地址 (L2585)
-```
-
---
-
-### 4. 修改连接地址需要改动的关键位置
-
-如果要修改下一跳连接地址的选择逻辑，需要关注以下位置：
-
-| 修改目标 | 文件 | 行号 | 函数 |
-|---------|------|------|------|
-| **IP地址选择策略** | `mutations.go` | L2654-2699 | `selectTunnelDialHost()` |
-| **IPv4地址提取** | `mutations.go` | L2755-2763 | `pickNodeAddressV4()` |
-| **IPv6地址提取** | `mutations.go` | L2765-2773 | `pickNodeAddressV6()` |
-| **端口获取** | `mutations.go` | L2585-2588 | `buildTunnelChainConfig()` |
-| **端口分配逻辑** | `repository_mutations.go` | ~L459 | `PickNodePortTx()` |
-| **端口写入数据库** | `repository_mutations.go` | L398-406 | `CreateChainTunnelTx()` |
-| **端口从数据库读取** | `repository_control.go` | L280-343 | `ListChainNodesForTunnel()` |
-
-**关键配置结构**:
-```go
-// mutations.go L1950-1957
-type tunnelRuntimeNode struct {
-    NodeID    int64
-    Protocol  string   // 连接协议
-    Strategy  string   // 选择策略
-    Inx       int      // 跳转序号
-    ChainType int      // 1=入口, 2=跳转, 3=出口
-    Port      int      // ★ 连接端口
-}
-```
-
---
-
-### 5. 调用链总结
-
-```
-用户创建隧道请求
-    │
-    ▼
-tunnelAdd (mutations.go L450)
-    │
-    ├── prepareTunnelCreateState() ──► 分配端口，构建 state
-    │
-    ├── replaceTunnelChainsTx() ──► 写入 chain_tunnel 表
-    │
-    └── applyTunnelRuntime()
-            │
-            ├── buildTunnelChainConfig()
-            │       │
-            │       ├── selectTunnelDialHost() ──► 选择 IP 地址
-            │       │
-            │       └── 使用 target.Port ──► 端口
-            │
-            └── sendNodeCommand("AddChains/AddService") ──► 发送到节点
-```
@@ -1,11 +0,0 @@
-探索转发创建时入口IP的生成流程：
-
-1. 查找 `buildTunnelInIP` 函数的完整实现
-2. 查找 `resolveForwardIngress` 函数的完整实现
-3. 理解 `forward_port` 表如何与节点IP关联
-4. 查找转发创建API（createForward）如何处理入口端口分配
-
-返回：
- 关键代码片段和行号
- 入口IP是如何从节点信息中提取的
- 修改入口IP需要改动的关键位置
@@ -1,185 +0,0 @@
-现在我已经找到了完整的入口IP生成流程。让我整理并返回关键信息：
-
---
-
-## 入口IP生成流程分析
-
-### 1. `buildTunnelInIP` 函数 (创建/更新隧道时)
-
-**位置**: `go-backend/internal/http/handler/mutations.go:2112-2152`
-
-```go
-func buildTunnelInIP(inNodes []tunnelRuntimeNode, nodes map[int64]*nodeRecord, ipPreference string) string {
-    set := make(map[string]struct{})
-    ordered := make([]string, 0)
-    preferV6 := strings.TrimSpace(ipPreference) == "v6"
-    for _, inNode := range inNodes {
-        node := nodes[inNode.NodeID]
-        if node == nil {
-            continue
-        }
-        v4 := strings.TrimSpace(node.ServerIPv4)   // 从节点获取 IPv4
-        v6 := strings.TrimSpace(node.ServerIPv6)   // 从节点获取 IPv6
-        var addrs []string
-        if preferV6 {
-            if v6 != "" { addrs = append(addrs, v6) }
-            if v4 != "" { addrs = append(addrs, v4) }
-        } else {
-            if v4 != "" { addrs = append(addrs, v4) }
-            if v6 != "" { addrs = append(addrs, v6) }
-        }
-        if len(addrs) == 0 {
-            if v := strings.TrimSpace(node.ServerIP); v != "" {  // fallback 到 ServerIP
-                addrs = append(addrs, v)
-            }
-        }
-        // ... 去重后拼接
-    }
-    return strings.Join(ordered, ",")
-}
-```
-
-**调用位置**:
- 隧道创建: `mutations.go:496`
- 隧道更新: `mutations.go:693`
-
---
-
-### 2. `resolveForwardIngress` 函数 (查询转发时)
-
-**位置**: `go-backend/internal/store/repo/repository.go:2727-2796`
-
-```go
-func resolveForwardIngress(db *gorm.DB, forwardID int64, tunnelID int64) (string, sql.NullInt64, error) {
-    // 1. 首先从 tunnel 表获取 in_ip (由 buildTunnelInIP 生成)
-    var tunnelInIP sql.NullString
-    db.Model(&model.Tunnel{}).Select("in_ip").Where("id = ?", tunnelID).Limit(1).Scan(&tunnelInIP)
-
-    // 2. 从 forward_port + node 表获取端口和节点IP
-    type fpRow struct {
-        Port     sql.NullInt64
-        ServerIP sql.NullString
-    }
-    var fpRows []fpRow
-    err := db.Model(&model.ForwardPort{}).
-        Select("forward_port.port, node.server_ip").
-        Joins("LEFT JOIN node ON node.id = forward_port.node_id").
-        Where("forward_port.forward_id = ?", forwardID).
-        Order("forward_port.id ASC").
-        Find(&fpRows).Error
-
-    // 3. 组装入口地址
-    // - 如果 tunnel.in_ip 存在: "ip1:port,ip2:port..."
-    // - 否则使用 forward_port 关联的 node.server_ip: "ip:port"
-    // ...
-}
-```
-
-**调用位置**:
- `repository.go:495` - 用户转发列表
- `repository.go:730` - 管理员转发列表
-
---
-
-### 3. `forward_port` 表与节点IP关联
-
-**模型定义**: `go-backend/internal/store/model/model.go:50-57`
-
-```go
-type ForwardPort struct {
-    ID        int64 `gorm:"primaryKey;autoIncrement"`
-    ForwardID int64 `gorm:"column:forward_id;not null"`
-    NodeID    int64 `gorm:"column:node_id;not null"`   // 关联到 node.id
-    Port      int   `gorm:"not null"`
-}
-```
-
-**关联查询** (在 `resolveForwardIngress` 中):
-```sql
-SELECT forward_port.port, node.server_ip
-FROM forward_port
-LEFT JOIN node ON node.id = forward_port.node_id
-WHERE forward_port.forward_id = ?
-ORDER BY forward_port.id ASC
-```
-
---
-
-### 4. 转发创建API入口分配流程
-
-**入口函数**: `go-backend/internal/http/handler/mutations.go:1108-1194`
-
-```go
-func (h *Handler) forwardCreate(w http.ResponseWriter, r *http.Request) {
-    // 1. 获取隧道入口节点IDs
-    entryNodes, _ := h.tunnelEntryNodeIDs(tunnelID)  // line 1162
-    
-    // 2. 获取或选择入口端口
-    port := asInt(req["inPort"], 0)
-    if port <= 0 {
-        port = h.pickTunnelPort(tunnelID)  // 自动分配端口 (line 1157)
-    }
-    
-    // 3. 创建转发记录 + forward_port 记录
-    forwardID, err := h.repo.CreateForwardTx(..., entryNodes, port, ...)  // line 1179
-}
-```
-
-**`CreateForwardTx`**: `go-backend/internal/store/repo/repository_mutations.go:1171-1209`
-```go
-func (r *Repository) CreateForwardTx(..., entryNodeIDs []int64, port int, ...) (int64, error) {
-    // 创建 forward 记录
-    // 为每个入口节点创建 forward_port 记录
-    for _, nodeID := range entryNodeIDs {
-        fp := model.ForwardPort{
-            ForwardID: forwardID,
-            NodeID:    nodeID,    // 入口节点ID
-            Port:      port,      // 入口端口
-        }
-        tx.Create(&fp)
-    }
-}
-```
-
-**入口节点获取**: `repository_mutations.go:535-548`
-```go
-func (r *Repository) TunnelEntryNodeIDs(tunnelID int64) ([]int64, error) {
-    // 从 chain_tunnel 表查询 chain_type = 1 (入口) 的节点
-    r.db.Model(&model.ChainTunnel{}).
-        Where("tunnel_id = ? AND chain_type = ?", tunnelID, "1").
-        Order("inx ASC, id ASC").
-        Pluck("node_id", &ids)
-}
-```
-
---
-
-## 关键修改位置
-
-| 需求 | 修改文件 | 行号 | 说明 |
-|------|----------|------|------|
-| **修改隧道入口IP生成逻辑** | `mutations.go` | 2112-2152 | `buildTunnelInIP` 函数，控制IPv4/IPv6优先级和组合 |
-| **修改转发入口IP解析** | `repository.go` | 2727-2796 | `resolveForwardIngress`，控制入口地址格式 |
-| **修改端口自动分配** | `mutations.go` | 2901-2964 | `pickTunnelPort`，控制端口范围选择 |
-| **修改入口节点关联** | `repository_mutations.go` | 1196-1205 | `CreateForwardTx` 中的 forward_port 创建 |
-| **节点IP来源** | `model.go` | 516-531 | `NodeRecord` 结构体 |
-| **节点IP存储** | `model.go` | 59-65 | `Node` 模型: `ServerIP`, `ServerIPV4`, `ServerIPV6` |
-
---
-
-## 入口IP数据流
-
-```
-1. 节点注册 → Node表存储 server_ip, server_ip_v4, server_ip_v6
-
-2. 创建隧道:
-   chain_tunnel (入口节点) → buildTunnelInIP() → tunnel.in_ip 字段
-
-3. 创建转发:
-   隧道入口节点IDs → forward_port(forward_id, node_id, port)
-
-4. 查询转发入口:
-   forward_port JOIN node → resolveForwardIngress()
-   ├─ 优先使用 tunnel.in_ip (多IP组合)
-   └─ 否则用 forward_port 关联的 node.server_ip
-```
@@ -1,16 +0,0 @@
-Explore the codebase to understand how forwarding/tunnel configuration works. I need to find:
-
-1. Frontend: The forwarding edit/create dialog component (likely in vite-frontend/src/)
-2. Backend: The forwarding data model and API handlers (likely in go-backend/)
-3. How the current "入口端口" (entry port) is handled
-
-Look for:
- Files related to "forward" or "转发" or "tunnel" or "隧道"
- Data models for forwarding rules
- API handlers for creating/editing forwards
-
-Return:
- Key file paths and their purposes
- Current data model structure for forwards
- How the entry listener is currently configured
- Any existing IP-related fields in the model
@@ -1,316 +0,0 @@
-              // List in frontend display isPort.)?
-
-
-      if (in_ip !== in.re.selected) {
-tunnel ip !== node in_tunnel.port_range value
-              select(v4 or IPv6, and
-              .chainType = chainType === 1 ( then chain_node !== node to check if `in_ip` is still used:
-              "chain_node_id" for `chainTunnels.node_id = nodeId, && `chainType != "hop" fields
-
-              //
-              }
-            }
-            }
-
-              <Select
-                <div className="flex flex-col gap-4 mt-6">
-              <Select
-                isFilterModalOpen={false}
-                setFilterUserId, filterTunnelId(tunnelId)}
-              }}
-              <form.in_port}
-                :form.in_port !== null,
-            }}
-          } else {
-setFilterTunnelId}
-              }
-            }}
-            // handleEntryNodeIDs
- hop - entry port assignment
-              const { entryNodeID, entryPort, entry_ip, resolvedFor forwardIn_ip based on
- forward data view:
-          In entity links the node,entry, remote_addr and`]
- tdCompose groups
-
- remote nodes by hostname.
- `target_addr` is multiple ones, the `targetAddr`/ `name` || `strategy: data in the form, uses the latest text.
-
- `line text: `grid gap-3 group` leading to border. from UI styles 
-  `.sort order`actions`: data
- ? `no-frontend for/not directly modify forward model
- so it doesn't have `inPort` in model.For forward creation.```
-
-        const forwardPort = entryNodeIDs with port = 0
- are - but tunnels and tunnels have
- after:. Based on.
-
- to reach the entry from. specified port-based" entry_ip, `addr_text` field or tunnel IP-based tunnel values with data not used this rules
- step pattern is`node-based:`peer` or a`IP_preference` + `ip_preference` header.
-
- "IP_preference from}
-        `grep<include="*.tsx"" path="/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/vite-frontend/src/pages/forward.tsx" />
- "peer_share" and "federation" share" APIs.
-        data models
-        />
-    < Frontend> `in_ip` comes from the tunnel, and not the node model.In Go-gost.
-
-. I will specifically look at `port` and `forward_port` data stored in `forward_port` table (`                      // When editing, forward, the UI keeps the current port value in the `inPort` state is checked for duplicates (`
- forwards list ( addresses with multiple addresses.
-
-          </div
-        }
-      </div>
-        }
-      }
-    }
-  }
-        className="flex flex-col gap-4">
-          {/* form fields - in edit mode */}
-          </4-form.inPort in field and handleClick save
- validation and numbers? `handleEdit` adds the `inPort` to the and `inPort` state.
-          // handleDragEnd ref={handleDragEnd} to scroll into view}
-          if (prev.forwardPorts.length === 0) {
-            // Create new forward
- entry with not auto expanded
-          const inPort records = || const{index` === 0` ? record and `forward_ports` table
-            const inPort = records = or can be rendered when the to pickTunnelPort:           the empty { inPort = null ?} => to persistent if port === 0 ( automatic assignment).
-          } else {
-            toast.error("请选择关联隧道")
-          }
-          const minPort =
-              const ports = oldPorts.map((p) => p)) // values from request
-          // value === 0 means "端口不能为空，  else if (!port) {
-            const inPort = tunnelPorts.map((t) => {
-              const inIP = tunnel = in_ip
- || t.IP === the default) 'auto' (available, tunnel.ip_preference` || `:` if` in_ip` and `in_port` values ( listenAddr] which`tcp`/udp` addresses are the respectively
-            `forward` now supports select/un/selected tunnel. when not found ( a single ` address can be shown, and simplified overview.= `tunnel` but has `in_ip` display name="人口入口IP` and "端口转发" when tunnel is port-forward, the model oftrafficRatio` floats with `type` and `protocol` fields.
-
-          // `protocol`: 'tls' | 'wss' | 'mtls' | 'mtcp'
- for `type` === 1: 繀 端口转发, 2: 隧道转发, and `type` determines the listeners on which forward ( protocol, and exit node ( configuration. Let `traffic_ratio` be on in/out, and the name` tunnelName, in the `UserTunnel` table
-    var chainType = chainType === "entry" ? # chainType === 2, value for represents entry node id for chain_type === "hop", fields indicate which hop number (1-based, `strategy` on the current value)
-
-                    ? newErrors.inPort = "端口必须在1-65535之间";
-                  form.inPort = optional
- required validation in  if filled, values to 0 or null, then the port is is auto-assigned
-                      } ValidateForm()
-                      if (validateForm()) {
-        setErrors(newErrors);
-      }
-    }
-  };
-  const handleTunnelChange = (tunnelId: string) => {
-    setForm((prev) => ({ ...prev, tunnelId}));
-    : if (prev.inPort !== null && prev.inPort !== old, in port assignment will not assign the new port  auto
-                });
-                }
-              );
-            } else {
-              inPort = null
-            : options.speedId = speedLimit }
-              onChange={(selectedKey) => {
-                setFilter((prev) => ({ ...prev, speedId, speedName }));
-            }
-          });
-        });
-              setBatchChangeTunnelModalOpen(false);
-              setBatchChangeTunnelModalOpen(false);
-            }
-          </div>
-          </div>
-        );
-      <input
-inport}
- */
-.tsx
-      <Input
-              description="指定入口端口，留空则从节点可用端口中自动分配"
-              placeholder="留空则自动分配可用端口"
-              type="number"
-              variant="bordered"
-              onChange={(e) => {
-                const value = e.target.value ? ""
-                  : parseInt(value) || null)
-                  setForm((prev) => ({ ...prev, inPort: null}));
-              </div>
-          </div>
-          <ModalContent>
-            <ModalHeader className="flex flex-col gap-1">
-              <h2 className="text-xl font-bold">
-                {isEdit ? "编辑转发" : "新增转发"}
-                </h2>
-                <p className="text-small text-default-500 mt-4">
-                  {isEdit ? "修改现有转发配置的信息" : "创建新的转发配置"}
-                </p>
-              <ModalBody>
-                <div className="space-y-4 pb-4">
-                  <Input
-                    errorMessage={errors.name}
-                    isInvalid={!!errors.name}
-                    label="转发名称"
-                    placeholder="请输入转发名称"
-                    value={form.name}
-                    variant="bordered"
-                    onChange={(e) =>
-                      setForm((prev) => ({ ...prev, name: e.target.value }))
-                    }
-                  />
-
-                  {/* Limit速规则选择 */}
-                  <Select
-                    description="限速规则"
-                    placeholder="不限速"
-                    selectedKeys={
-                      selectedSpeedId !== null ? ?[selectedSpeedId.toString()] : []
-                    }
-                    variant="bordered"
-                    onSelectionChange={(keys) => {
-                      const selectedKey = Array.from(keys)[0] as string | undefined;
-                      setForm((prev) => ({
-                        ...prev,
-                        speedId: selectedKey ? Number(selectedKey) : null,
-                      });
-                    }}
-                  />
-
-                  {/*隧道选择 */}
-                  <Select
-                    description={
-                      isEdit
-                        ? "更改隧道将释放原端口并在新隧道分配端口"
-                        : "更改隧道后重新分配端口并同步到节点"
-                  }
-                    }
-                    errorMessage={errors.tunnelId}
-                    isInvalid={!!errors.tunnelId}
-                    label="选择隧道"
-                    placeholder="请选择关联的隧道"
-                    selectedKeys={
-                      form.tunnelId ? [form.tunnelId.toString()] : []
-                    }
-                    variant="bordered"
-                    onSelectionChange={(keys) => {
-                      const selectedKey = Array.from(keys)[0] as string;
-                      if (selectedKey) {
-                        handleTunnelChange(selectedKey);
-                      }
-                    }
-                  />
-
-                  {/*入口端口 */}
-                  <Input
-                    description="指定入口端口，留空则从节点可用端口中自动分配"
-                    errorMessage={errors.inPort}
-                    isInvalid={!!errors.inPort}
-                    label="入口端口"
-                    placeholder="留空则自动分配可用端口"
-                    type="number"
-                    value={form.inPort !== null ? form.inPort.toString() : ""}
-                    variant="bordered"
-                    onChange={(e) => {
-                      const value = e.target.value;
-                      setForm((prev) => ({ ...prev, inPort: value ? parseInt(value) : null }));
-                    }
-                  />
-                </div>
-          </ModalBody>
-        </ModalContent>
-      </Modal>
-    </Modal>
-  );
-};
-
-  // ===================== Summary of findings ===================
-
-## Key File Paths and their purposes:
-
-### Frontend: Forward Edit/create dialog component
- **Main file:** `/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/vite-frontend/src/pages/forward.tsx`
-  - Displays the forwarding list and handles all create/edit/delete/forwards
- Has `inIp` and `inPort` fields
- Shows entry port and dialog/form with validation
- Uses React-hook-form with state management
- Calls `createForward`, `updateForward`, `deleteForward`, `pauseForwardService`, `resumeForwardService`, APIs
-
- Imports API functions from `@/api`
-
-### Backend: Forwarding data model and API handlers
- **Main model file:** `/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/go-backend/internal/store/model/model.go`
-  - GORM model definition for `Forward` struct does basic forwarding configuration
-  - Related models: `ForwardPort`, `Tunnel`, `UserForwardDetail` (view struct)
-
-  - **API handlers:** `/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/go-backend/internal/http/handler/mutations.go`
-  - Create/update/delete operations
-  - Entry port handling via `inPort` field
-
- **Repository layer:** `/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/go-backend/internal/store/repo/repository_mutations.go`
-  - CRUD operations for  - `resolveForwardIngress` function in `/Users/sagit/.local/share/opencode/worktree/13650be91caa3a9e08a2e63127fef62757658384/mighty-nebula/go-backend/internal/store/repo/repository.go`
-  - Computes `inIp` and `inPort` from joins
-
-### Current data model structure for forwards
-
-From `go-backend/internal/store/model/model.go`:
-
-```go
-// Forward maps to the "forward" table.
-type Forward struct {
-    ID          int64         `gorm:"primaryKey;autoIncrement"`
-    UserID      int64         `gorm:"column:user_id;not null"`
-    UserName    string        `gorm:"column:user_name;type:varchar(100);not null"`
-    Name        string        `gorm:"type:varchar(100);not null"`
-    TunnelID    int64         `gorm:"column:tunnel_id;not null"`
-    RemoteAddr  string        `gorm:"column:remote_addr;type:text;not null"`
-    Strategy    string        `gorm:"type:varchar(100);not null;default:'fifo'"`
-    InFlow      int64         `gorm:"not null;default:0"`
-    OutFlow     int64         `gorm:"column:out_flow;not null;default:0"`
-    CreatedTime int64         `gorm:"column:created_time;not null"`
-    UpdatedTime int64         `gorm:"column:updated_time;not null"`
-    Status      int           `gorm:"not null"`
-    Inx         int           `gorm:"not null;default:0"`
-    SpeedID     sql.NullInt64 `gorm:"column:speed_id"`
-}
-```
-
-```go
-// ForwardPort maps to the "forward_port" table - stores port assignments per entry node
-type ForwardPort struct {
-    ID        int64 `gorm:"primaryKey;autoIncrement"`
-    ForwardID int64 `gorm:"column:forward_id;not null"`
-    NodeID    int64 `gorm:"column:node_id;not null"`
-    Port      int   `gorm:"not null"`
-}
-```
-
-```go
-// Tunnel maps to the "tunnel" table - has entry IP configuration
-type Tunnel struct {
-    ID           int64          `gorm:"primaryKey;autoIncrement"`
-    Name         string         `gorm:"type:varchar(100);not null"`
-    TrafficRatio float64        `gorm:"column:traffic_ratio;not null;default:1.0"`
-    Type         int            `gorm:"not null"`
-    Protocol     string         `gorm:"type:varchar(10);not null;default:'tls'"`
-    Flow         int64          `gorm:"not null"`
-    CreatedTime  int64          `gorm:"column:created_time;not null"`
-    UpdatedTime  int64          `gorm:"column:updated_time;not null"`
-    Status       int            `gorm:"not null"`
-    InIP         sql.NullString `gorm:"column:in_ip;type:text"`       // Optional entry IP hint
-    Inx          int            `gorm:"not null;default:0"`
-    IPPreference string         `gorm:"column:ip_preference;type:varchar(10);not null;default:''"`
-}
-```
-
-### How entry listener is currently configured:
-
-1. **Port Storage**: `ForwardPort` table stores the mapping from `forward_id` -> `node_id` -> `port`
-   - Port is assigned by the handler or passed via `inPort` parameter ( or auto-picked)
-   - Entry nodes are determined by `tunnelEntryNodeIDs()` in handler
-
-3. **Entry IP Resolution**: The `resolveForwardIngress()` function resolves `inIp` and `inPort` by:
-   - Joining `forward_port` with `node` table
-   - `inIp` comes from `tunnel.in_ip` if set (takes precedence over node.server_ip)
-   - For multi-entry-node forwards, comma-separated IPs and ports are returned
-
-4. **Current IP-related fields**:
-   - `Forward` model: No `inIp` field (port is stored in `forward_port` table)
-   - `Tunnel` model: Has `InIP` field (nullable, - allows specifying of a preferred entry IP hint
-   - `UserForwardDetail` view struct ( joins tunnel table and includes `InIP` and `InPort`
-5. **No explicit entry IP selection UI in current dialog** - The port field is a text input, and form validates range but but UI doesn't allow setting specific IP addresses
@@ -1,10 +0,0 @@
-总结一下这个issue，结合当前代码，尽量设计简约实现issue的目标
-https://github.com/Sagit-chu/flvx/issues/211
-
---
-
-应该在节点上的高级里面允许添加多个IP
-
---
-
-继续，允许在节点管理里填写多个地址，然后在组成隧道或者转发的时候选择节点的时候允许选择具体的ip，请开始设计，允许使用并行subagent
@@ -1,76 +0,0 @@
-明白了！更新设计：
-
---
-
-## 最终设计方案
-
-### 核心需求
-
-| 场景 | 配置位置 | 选择内容 |
-|------|----------|----------|
-| 转发 | 转发创建/编辑 | 入口监听IP（从入口节点IP列表选择） |
-| 隧道 | 隧道配置 | 出口节点连接IP（从出口节点IP列表选择） |
-
---
-
-### 数据模型变更（3处）
-
-```
-Node.ExtraIPs      sql.NullString  `gorm:"column:extra_ips;type:text"`     // 逗号分隔
-ForwardPort.InIP   sql.NullString  `gorm:"column:in_ip;type:text"`         // 指定监听IP
-ChainTunnel.ConnectIP sql.NullString `gorm:"column:connect_ip;type:text"`  // 出口连接IP
-```
-
---
-
-### 改动清单
-
-#### 后端 (约200行)
-
-| 文件 | 改动 |
-|------|------|
-| `model/model.go` | Node/ForwardPort/ChainTunnel 增加3个字段 |
-| `repository_mutations.go` | CreateNode/UpdateNode 处理 extraIPs 参数 |
-| `repository_control.go` | GetNodeRecord/ListNodeAllIPs 辅助函数 |
-| `repository.go` | resolveForwardIngress 使用 forward_port.in_ip |
-| `handler/mutations.go` | selectTunnelDialHost 优先使用 connectIP |
-
-#### 前端 (约150行)
-
-| 页面 | 改动 |
-|------|------|
-| 节点编辑 | 高级配置增加"额外IP" Input（逗号分隔） |
-| 转发编辑 | 入口端口旁增加"监听IP" Select（从入口节点IP选择） |
-| 隧道配置 | 出口节点行增加"连接IP" Select（从出口节点IP选择） |
-
---
-
-### UI 示意
-
-**节点编辑 - 高级配置**
-```
-额外IP地址
-┌──────────────────────────────────────────┐
-│ 192.168.1.100, 10.0.0.5                  │
-└──────────────────────────────────────────┘
-用于多IP服务器，逗号分隔
-```
-
-**转发创建**
-```
-入口端口: [ 8080 ]     监听IP: [ 192.168.1.100 ▼ ]
-                                ├─ 203.0.113.10 (默认)
-                                ├─ 192.168.1.100
-                                └─ 10.0.0.5
-```
-
-**隧道配置 - 出口节点**
-```
-出口节点: [ node-1 ▼ ]  端口: [ 8443 ]  连接IP: [ 10.0.0.5 ▼ ]
-                                                ├─ 203.0.113.10 (默认)
-                                                └─ 10.0.0.5
-```
-
---
-
-这个方案简约清晰，是否可以开始实现？
@@ -1,4 +0,0 @@
-{
-  "enabled": true,
-  "telemetry": false
-}
@@ -1,107 +0,0 @@
-name: CI Build Check
-
-on:
-  push:
-    branches: ['**']
-  pull_request:
-    branches: ['**']
-
-jobs:
-  frontend:
-    name: Build Frontend
-    runs-on: ubuntu-latest
-    defaults:
-      run:
-        working-directory: vite-frontend
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20.19.0'
-
-      - name: Install dependencies
-        run: npm install --legacy-peer-deps
-
-      - name: Build
-        run: npm run build
-
-  backend:
-    name: Build Go Backend
-    runs-on: ubuntu-latest
-    defaults:
-      run:
-        working-directory: go-backend
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Go
-        uses: actions/setup-go@v5
-        with:
-          go-version: '1.23'
-          cache-dependency-path: go-backend/go.sum
-
-      - name: Download dependencies
-        run: go mod download
-
-      - name: Build
-        run: go build -v ./...
-
-  backend-postgres-contract:
-    name: Go Backend PostgreSQL Contract
-    runs-on: ubuntu-latest
-    services:
-      postgres:
-        image: postgres:17
-        env:
-          POSTGRES_USER: flux_test
-          POSTGRES_PASSWORD: flux_test_pass
-          POSTGRES_DB: flux_test
-        ports:
-          - 5432:5432
-        options: >-
-          --health-cmd "pg_isready -U flux_test -d flux_test"
-          --health-interval 10s
-          --health-timeout 5s
-          --health-retries 10
-    defaults:
-      run:
-        working-directory: go-backend
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Go
-        uses: actions/setup-go@v5
-        with:
-          go-version: '1.23'
-          cache-dependency-path: go-backend/go.sum
-
-      - name: Download dependencies
-        run: go mod download
-
-      - name: Run PostgreSQL contract test
-        env:
-          FLVX_POSTGRES_TEST_DSN: 'postgres://flux_test:flux_test_pass@127.0.0.1:5432/flux_test?sslmode=disable'
-        run: go test ./tests/contract -run TestPostgresNodeCreateRepairsMissingIDDefaultContract -count=1
-
-  agent:
-    name: Build Agent
-    runs-on: ubuntu-latest
-    defaults:
-      run:
-        working-directory: go-gost
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Go
-        uses: actions/setup-go@v5
-        with:
-          go-version: '1.23'
-          cache-dependency-path: go-gost/go.sum
-
-      - name: Download dependencies
-        run: go mod download
-
-      - name: Build
-        run: go build -v .
@@ -1,43 +0,0 @@
-name: Deploy Docs
-on:
-  push:
-    branches:
-      - main
-      - master
-      - beta
-    paths:
-      - 'doc/**'
-      - 'mkdocs.yml'
-
-permissions:
-  contents: write
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Configure Git Credentials
-        run: |
-          git config user.name github-actions[bot]
-          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
-
-      - uses: actions/setup-python@v5
-        with:
-          python-version: 3.x
-
-      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV 
-
-      - uses: actions/cache@v4
-        with:
-          key: mkdocs-material-${{ env.cache_id }}
-          path: .cache
-          restore-keys: |
-            mkdocs-material-
-
-      - name: Install MkDocs and Material Theme
-        run: pip install mkdocs-material
-
-      - name: Build and Deploy
-        run: mkdocs gh-deploy --force
@@ -1,71 +1,55 @@
-name: Build and Push Images
+name: Build and Push Images Based on Version

+# 在这里定义统一版本号
 env:
-  VERSION: "2.0.7-beta"  # 分支推送时使用的默认版本
-  REGISTRY: ghcr.io
+  VERSION: "1.4.3"

 on:
  push:
-    tags:
-      - '[0-9]*'  # 匹配 2.0.8, 2.0.8-beta 等格式
+    branches:
+      - main
+      - beta

 jobs:
  check-version:
    name: Check Version and Decide Build
    runs-on: ubuntu-latest
    outputs:
-      version: ${{ steps.version.outputs.version }}
-      should_build: ${{ steps.version.outputs.should_build }}
-      should_build_gost: ${{ steps.version.outputs.should_build_gost }}
-      is_tag: ${{ steps.version.outputs.is_tag }}
-      image_owner: ${{ steps.version.outputs.image_owner }}
+      version: ${{ env.VERSION }}
+      should_build: ${{ steps.check-tag.outputs.should_build }}
+      should_build_gost: ${{ steps.check-tag.outputs.should_build_gost }}
+      tag_exists: ${{ steps.check-tag.outputs.tag_exists }}
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
        with:
          fetch-depth: 0

-      - name: Determine version and build strategy
-        id: version
+      - name: Display version
        run: |
-          # 镜像 owner 需要小写
-          IMAGE_OWNER=$(echo "${{ github.repository_owner }}" | tr '[:upper:]' '[:lower:]')
-          echo "image_owner=$IMAGE_OWNER" >> $GITHUB_OUTPUT
+          echo "Current version: ${{ env.VERSION }}"

-          if [[ "${{ github.ref_type }}" == "tag" ]]; then
-            # Tag 触发：直接使用 tag 名作为版本，全量构建
-            VERSION="${{ github.ref_name }}"
-            echo "🏷️ Tag trigger detected: $VERSION"
-            echo "version=$VERSION" >> $GITHUB_OUTPUT
-            echo "is_tag=true" >> $GITHUB_OUTPUT
-            echo "should_build=true" >> $GITHUB_OUTPUT
-            echo "should_build_gost=true" >> $GITHUB_OUTPUT
-          else
-            # 分支触发：使用 env.VERSION，检查是否需要构建
-            VERSION="${{ env.VERSION }}"
-            echo "🌿 Branch trigger detected, using version: $VERSION"
-            echo "version=$VERSION" >> $GITHUB_OUTPUT
-            echo "is_tag=false" >> $GITHUB_OUTPUT
-
-            # 检查 tag 是否已存在
-            if git rev-parse "$VERSION" >/dev/null 2>&1; then
-              echo "Tag $VERSION already exists"
-              echo "should_build=false" >> $GITHUB_OUTPUT
-
-              # 检查 go-gost 目录是否有变化
-              TAG_COMMIT=$(git rev-list -n 1 "$VERSION")
-              if git diff --quiet --ignore-all-space --ignore-blank-lines $TAG_COMMIT HEAD -- go-gost/ 2>/dev/null; then
-                echo "✅ GOST files unchanged since tag"
-                echo "should_build_gost=false" >> $GITHUB_OUTPUT
-              else
-                echo "🔄 Detected changes in go-gost directory"
-                git diff --stat $TAG_COMMIT HEAD -- go-gost/ || true
-                echo "should_build_gost=true" >> $GITHUB_OUTPUT
-              fi
+      - name: Check if tag exists and detect changes
+        id: check-tag
+        run: |
+          if git rev-parse "${{ env.VERSION }}" >/dev/null 2>&1; then
+            echo "Tag ${{ env.VERSION }} already exists"
+            echo "tag_exists=true" >> $GITHUB_OUTPUT
+            echo "should_build=false" >> $GITHUB_OUTPUT
+            
+            # 检查从tag到现在，go-gost目录下的文件是否有变化
+            TAG_COMMIT=$(git rev-list -n 1 "${{ env.VERSION }}")
+            if git diff --quiet $TAG_COMMIT HEAD -- go-gost/; then
+              echo "✅ GOST files unchanged since tag"
+              echo "should_build_gost=false" >> $GITHUB_OUTPUT
            else
-              echo "Tag $VERSION does not exist, will build all components"
-              echo "should_build=true" >> $GITHUB_OUTPUT
+              echo "🔄 GOST files changed since tag, will rebuild GOST binary"
              echo "should_build_gost=true" >> $GITHUB_OUTPUT
            fi
+          else
+            echo "Tag ${{ env.VERSION }} does not exist, will build all components"
+            echo "should_build=true" >> $GITHUB_OUTPUT
+            echo "should_build_gost=true" >> $GITHUB_OUTPUT
+            echo "tag_exists=false" >> $GITHUB_OUTPUT
          fi

  build-gost:
@@ -74,49 +58,49 @@ jobs:
    if: needs.check-version.outputs.should_build_gost == 'true'
    runs-on: ubuntu-latest
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3

      - name: Set up Go
-        uses: actions/setup-go@v5
+        uses: actions/setup-go@v4
        with:
-          go-version: '1.23'
+          go-version: '1.21'

      - name: Cache Go modules
-        uses: actions/cache@v4
+        uses: actions/cache@v3
        with:
          path: |
            ~/.cache/go-build
            ~/go/pkg/mod
-          key: ${{ runner.os }}-go-${{ hashFiles('go-gost/go.sum') }}
+          key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
          restore-keys: |
            ${{ runner.os }}-go-

      - name: Install UPX
        run: |
-          wget -q https://github.com/upx/upx/releases/download/v4.2.1/upx-4.2.1-amd64_linux.tar.xz
+          wget https://github.com/upx/upx/releases/download/v4.2.1/upx-4.2.1-amd64_linux.tar.xz
          tar -xf upx-4.2.1-amd64_linux.tar.xz
          sudo mv upx-4.2.1-amd64_linux/upx /usr/local/bin/
          rm -rf upx-4.2.1-amd64_linux*

      - name: Build GOST binary (AMD64)
        working-directory: ./go-gost
-        run: CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags="-s -w -X main.version=${{ needs.check-version.outputs.version }}" -o gost-amd64
+        run: |
+          CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -ldflags="-s -w" -o gost-amd64

      - name: Build GOST binary (ARM64)
        working-directory: ./go-gost
-        run: CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -ldflags="-s -w -X main.version=${{ needs.check-version.outputs.version }}" -o gost-arm64
+        run: |
+          CGO_ENABLED=0 GOOS=linux GOARCH=arm64 go build -ldflags="-s -w" -o gost-arm64

-      - name: Compress with UPX
+      - name: Compress with UPX (AMD64)
        working-directory: ./go-gost
        run: |
          upx --best --lzma gost-amd64
-          upx --best --lzma gost-arm64

-      - name: Generate SHA256 checksums
+      - name: Compress with UPX (ARM64)
        working-directory: ./go-gost
        run: |
-          sha256sum gost-amd64 > gost-amd64.sha256
-          sha256sum gost-arm64 > gost-arm64.sha256
+          upx --best --lzma gost-arm64

      - name: Upload GOST AMD64 artifact
        uses: actions/upload-artifact@v4
@@ -130,119 +114,91 @@ jobs:
          name: gost-binary-arm64
          path: ./go-gost/gost-arm64

-      - name: Upload GOST AMD64 checksum artifact
-        uses: actions/upload-artifact@v4
-        with:
-          name: gost-checksum-amd64
-          path: ./go-gost/gost-amd64.sha256
-
-      - name: Upload GOST ARM64 checksum artifact
-        uses: actions/upload-artifact@v4
-        with:
-          name: gost-checksum-arm64
-          path: ./go-gost/gost-arm64.sha256
-
  build-vite:
    name: Build & Push Vite Frontend
    needs: check-version
    if: needs.check-version.outputs.should_build == 'true'
    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20

      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
+        uses: docker/setup-buildx-action@v2

-      - name: Log in to GitHub Container Registry
-        uses: docker/login-action@v3
+      - name: Log in to DockerHub
+        uses: docker/login-action@v2
        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
-
-      - name: Prepare build args
-        run: |
-          VERSION="${{ needs.check-version.outputs.version }}"
-          {
-            echo "VITE_GITHUB_REPO=https://github.com/${{ github.repository }}"
-            echo "VITE_APP_VERSION=$VERSION"
-          } > ./vite-frontend/.env.production
+          username: ${{ secrets.DOCKER_HUB_USERNAME }}
+          password: ${{ secrets.DOCKER_HUB_TOKEN }}

      - name: Build and push Vite Docker images
        run: |
          VERSION="${{ needs.check-version.outputs.version }}"
-          OWNER="${{ needs.check-version.outputs.image_owner }}"
-
          docker buildx build \
            --platform linux/amd64,linux/arm64 \
            --push \
-            -t ${{ env.REGISTRY }}/${OWNER}/vite-frontend:latest \
-            -t ${{ env.REGISTRY }}/${OWNER}/vite-frontend:${VERSION} \
+            -t bqlpfy/vite-frontend:latest \
+            -t bqlpfy/vite-frontend:${VERSION} \
            ./vite-frontend

-  build-go-backend:
-    name: Build & Push Go Backend
+  build-java:
+    name: Build & Push Spring Boot Backend
    needs: check-version
    if: needs.check-version.outputs.should_build == 'true'
    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3

-      - name: Set up Go
-        uses: actions/setup-go@v5
+      - name: Set up JDK and Maven
+        uses: actions/setup-java@v3
        with:
-          go-version: '1.23'
+          java-version: 21
+          distribution: 'temurin'

-      - name: Cache Go dependencies
-        uses: actions/cache@v4
+      - name: Cache Maven dependencies
+        uses: actions/cache@v3
        with:
-          path: |
-            ~/.cache/go-build
-            ~/go/pkg/mod
-          key: ${{ runner.os }}-go-backend-${{ hashFiles('go-backend/go.sum') }}
-          restore-keys: ${{ runner.os }}-go-backend-
+          path: ~/.m2
+          key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
+          restore-keys: ${{ runner.os }}-m2

-      - name: Download dependencies
-        working-directory: ./go-backend
-        run: go mod download
+      - name: Build Java JAR
+        working-directory: ./springboot-backend
+        run: mvn clean package -DskipTests

      - name: Set up Docker Buildx
-        uses: docker/setup-buildx-action@v3
+        uses: docker/setup-buildx-action@v2

-      - name: Log in to GitHub Container Registry
-        uses: docker/login-action@v3
+      - name: Log in to DockerHub
+        uses: docker/login-action@v2
        with:
-          registry: ${{ env.REGISTRY }}
-          username: ${{ github.actor }}
-          password: ${{ secrets.GITHUB_TOKEN }}
+          username: ${{ secrets.DOCKER_HUB_USERNAME }}
+          password: ${{ secrets.DOCKER_HUB_TOKEN }}

-      - name: Build and push Go backend Docker images
+      - name: Build and push Java Docker images
        run: |
          VERSION="${{ needs.check-version.outputs.version }}"
-          OWNER="${{ needs.check-version.outputs.image_owner }}"
-
          docker buildx build \
            --platform linux/amd64,linux/arm64 \
            --push \
-            -t ${{ env.REGISTRY }}/${OWNER}/flux-panel-backend:latest \
-            -t ${{ env.REGISTRY }}/${OWNER}/flux-panel-backend:${VERSION} \
-            ./go-backend
+            -t bqlpfy/springboot-backend:latest \
+            -t bqlpfy/springboot-backend:${VERSION} \
+            ./springboot-backend

  create-release:
-    name: Create Release (Tag Only)
-    needs: [check-version, build-gost, build-vite, build-go-backend]
-    if: needs.check-version.outputs.is_tag == 'true'
+    name: Create Release and Tag
+    needs: [check-version, build-gost, build-vite, build-java]
+    if: needs.check-version.outputs.should_build == 'true'
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3

      - name: Download GOST AMD64 binary
        uses: actions/download-artifact@v4
@@ -256,135 +212,60 @@ jobs:
          name: gost-binary-arm64
          path: ./artifacts/arm64

-      - name: Download GOST AMD64 checksum
-        uses: actions/download-artifact@v4
-        with:
-          name: gost-checksum-amd64
-          path: ./artifacts/
-
-      - name: Download GOST ARM64 checksum
-        uses: actions/download-artifact@v4
-        with:
-          name: gost-checksum-arm64
-          path: ./artifacts/
-
-      - name: Prepare release files
-
+      - name: Rename binaries
        run: |
-          VERSION="${{ needs.check-version.outputs.version }}"
-          OWNER="${{ needs.check-version.outputs.image_owner }}"
-          REPO="${{ github.repository }}"
-
-          # 移动二进制文件
          mv ./artifacts/amd64/gost-amd64 ./artifacts/gost-amd64
          mv ./artifacts/arm64/gost-arm64 ./artifacts/gost-arm64

-          # 复制并修改 docker-compose 文件
-          cp docker-compose-v4.yml ./artifacts/docker-compose-v4.yml
-          cp docker-compose-v6.yml ./artifacts/docker-compose-v6.yml
-
-          # 替换镜像地址为 GHCR
-          sed -i "s|image: .*flux-panel-backend:[^[:space:]]*|image: ${{ env.REGISTRY }}/${OWNER}/flux-panel-backend:${VERSION}|g" ./artifacts/docker-compose-v4.yml
-          sed -i "s|image: .*vite-frontend:[^[:space:]]*|image: ${{ env.REGISTRY }}/${OWNER}/vite-frontend:${VERSION}|g" ./artifacts/docker-compose-v4.yml
-          sed -i "s|image: .*flux-panel-backend:[^[:space:]]*|image: ${{ env.REGISTRY }}/${OWNER}/flux-panel-backend:${VERSION}|g" ./artifacts/docker-compose-v6.yml
-          sed -i "s|image: .*vite-frontend:[^[:space:]]*|image: ${{ env.REGISTRY }}/${OWNER}/vite-frontend:${VERSION}|g" ./artifacts/docker-compose-v6.yml
-
-          # 复制并修改安装脚本
-          cp install.sh ./artifacts/install.sh
-          cp panel_install.sh ./artifacts/panel_install.sh
-
-          # 替换仓库地址和版本号
-          sed -i "s|bqlpfy/flux-panel|${REPO}|g" ./artifacts/install.sh
-          sed -i "s|bqlpfy/flux-panel|${REPO}|g" ./artifacts/panel_install.sh
-          sed -i "s|2.0.7-beta|${VERSION}|g" ./artifacts/install.sh
-          sed -i "s|2.0.7-beta|${VERSION}|g" ./artifacts/panel_install.sh
-
-          # 注入固定版本号，使从 Release 页下载的脚本只安装该版本
-          sed -i "s|^PINNED_VERSION=\"\"|PINNED_VERSION=\"${VERSION}\"|" ./artifacts/install.sh
-          sed -i "s|^PINNED_VERSION=\"\"|PINNED_VERSION=\"${VERSION}\"|" ./artifacts/panel_install.sh
-
      - name: Create Release
        env:
          GH_TOKEN: ${{ github.token }}
        run: |
          VERSION="${{ needs.check-version.outputs.version }}"
-          OWNER="${{ needs.check-version.outputs.image_owner }}"
-
+          
+          # 创建并推送 tag
+          git tag "${VERSION}" ${{ github.sha }}
+          git push origin "${VERSION}"
+          
          # 获取 commit 信息
          COMMIT_MSG=$(git log -1 --pretty=format:"%s")
          COMMIT_AUTHOR=$(git log -1 --pretty=format:"%an")
          COMMIT_DATE=$(git log -1 --pretty=format:"%ai")
-
+          
          # 创建 release
          gh release create "${VERSION}" \
            --title "Release ${VERSION}" \
-            --notes "## 📝 Release Information
-
-          - **Version**: ${VERSION}
-          - **Commit**: [\`${GITHUB_SHA:0:7}\`](https://github.com/${{ github.repository }}/commit/${{ github.sha }})
+            --notes "## 📝 Commit Information
+          - **Message**: ${COMMIT_MSG}
          - **Author**: ${COMMIT_AUTHOR}
          - **Date**: ${COMMIT_DATE}
-          - **Message**: ${COMMIT_MSG}
-
-          ## 📦 Docker Images
-
-          \`\`\`bash
-          # Backend
-          docker pull ${{ env.REGISTRY }}/${OWNER}/flux-panel-backend:${VERSION}
-
-          # Frontend
-          docker pull ${{ env.REGISTRY }}/${OWNER}/vite-frontend:${VERSION}
-          \`\`\`
-
-          ## 🚀 Quick Install
-
-          **Panel (安装此版本 ${VERSION}):**
-          \`\`\`bash
-          curl -L https://github.com/${{ github.repository }}/releases/download/${VERSION}/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
-          \`\`\`
-
-          **Node (安装此版本 ${VERSION}):**
-          \`\`\`bash
-          curl -L https://github.com/${{ github.repository }}/releases/download/${VERSION}/install.sh -o install.sh && chmod +x install.sh && ./install.sh
-          \`\`\`
-
-          **安装最新版:**
-          \`\`\`bash
-          # 面板端
-          curl -L https://raw.githubusercontent.com/${{ github.repository }}/main/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
-          # 节点端
-          curl -L https://raw.githubusercontent.com/${{ github.repository }}/main/install.sh -o install.sh && chmod +x install.sh && ./install.sh
-          \`\`\`" \
+          - **Commit**: [\`${GITHUB_SHA:0:7}\`](https://github.com/${{ github.repository }}/commit/${{ github.sha }})" \
            --repo ${{ github.repository }}
-
+          
          # 上传所有文件到 release
          echo "📤 上传 GOST 二进制文件..."
          gh release upload "${VERSION}" ./artifacts/gost-amd64 --clobber
          gh release upload "${VERSION}" ./artifacts/gost-arm64 --clobber
-
-          echo "📤 上传 GOST 校验文件..."
-          gh release upload "${VERSION}" ./artifacts/gost-amd64.sha256 --clobber
-          gh release upload "${VERSION}" ./artifacts/gost-arm64.sha256 --clobber
-
+          
          echo "📤 上传安装脚本..."
-          gh release upload "${VERSION}" ./artifacts/install.sh --clobber
-          gh release upload "${VERSION}" ./artifacts/panel_install.sh --clobber
-
+          gh release upload "${VERSION}" ./install.sh --clobber
+          gh release upload "${VERSION}" ./panel_install.sh --clobber
+          
          echo "📤 上传 Docker Compose 配置文件..."
-          gh release upload "${VERSION}" ./artifacts/docker-compose-v4.yml --clobber
-          gh release upload "${VERSION}" ./artifacts/docker-compose-v6.yml --clobber
-
-          echo "✅ Release ${VERSION} 创建完成"
+          gh release upload "${VERSION}" ./docker-compose-v4.yml --clobber
+          gh release upload "${VERSION}" ./docker-compose-v6.yml --clobber
+          
+          echo "✅ 所有文件已上传到 Release ${VERSION}"

  update-release-gost:
    name: Update GOST Binaries in Release
    needs: [check-version, build-gost]
-    if: needs.check-version.outputs.is_tag == 'false' && needs.check-version.outputs.should_build == 'false' && needs.check-version.outputs.should_build_gost == 'true'
+    if: needs.check-version.outputs.should_build == 'false' && needs.check-version.outputs.should_build_gost == 'true'
    runs-on: ubuntu-latest
    permissions:
      contents: write
    steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3

      - name: Download GOST AMD64 binary
        uses: actions/download-artifact@v4
@@ -398,18 +279,6 @@ jobs:
          name: gost-binary-arm64
          path: ./artifacts/arm64

-      - name: Download GOST AMD64 checksum
-        uses: actions/download-artifact@v4
-        with:
-          name: gost-checksum-amd64
-          path: ./artifacts/
-
-      - name: Download GOST ARM64 checksum
-        uses: actions/download-artifact@v4
-        with:
-          name: gost-checksum-arm64
-          path: ./artifacts/
-
      - name: Rename binaries
        run: |
          mv ./artifacts/amd64/gost-amd64 ./artifacts/gost-amd64
@@ -420,15 +289,42 @@ jobs:
          GH_TOKEN: ${{ github.token }}
        run: |
          VERSION="${{ needs.check-version.outputs.version }}"
-
+          
          echo "🔄 更新 Release ${VERSION} 中的 GOST 二进制文件..."
-
+          
          gh release upload "${VERSION}" ./artifacts/gost-amd64 --clobber
          gh release upload "${VERSION}" ./artifacts/gost-arm64 --clobber
+          
+          echo "✅ GOST 二进制文件更新完成！"
+          echo "ℹ️ Docker 镜像未重新构建"

-          echo "📤 上传 GOST 校验文件..."
-          gh release upload "${VERSION}" ./artifacts/gost-amd64.sha256 --clobber
-          gh release upload "${VERSION}" ./artifacts/gost-arm64.sha256 --clobber
-
-          echo "✅ GOST 二进制文件更新完成"
+  update-release-files:
+    name: Update Release Files Only
+    needs: check-version
+    if: needs.check-version.outputs.tag_exists == 'true' && needs.check-version.outputs.should_build == 'false' && needs.check-version.outputs.should_build_gost == 'false'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v3

+      - name: Update Release Files
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          VERSION="${{ needs.check-version.outputs.version }}"
+          
+          echo "📤 更新 Release ${VERSION} 中的脚本和配置文件..."
+          
+          # 上传安装脚本（覆盖）
+          echo "📤 更新安装脚本..."
+          gh release upload "${VERSION}" ./install.sh --clobber
+          gh release upload "${VERSION}" ./panel_install.sh --clobber
+          
+          # 上传 Docker Compose 配置文件（覆盖）
+          echo "📤 更新 Docker Compose 配置文件..."
+          gh release upload "${VERSION}" ./docker-compose-v4.yml --clobber
+          gh release upload "${VERSION}" ./docker-compose-v6.yml --clobber
+          
+          echo "✅ 文件更新完成！Release ${VERSION} 中的脚本和配置已更新"
+          echo "ℹ️ Docker 镜像和 GOST 二进制未重新构建"
@@ -1,48 +0,0 @@
-name: Publish Skill to npm
-
-on:
-  push:
-    tags:
-      - 'v*'
-  workflow_dispatch:
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      id-token: write
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Get version from tag
-        id: version
-        run: |
-          if [ "${{ github.event_name }}" = "workflow_dispatch" ]; then
-            VERSION=$(node -p "require('./skills/flvx-api/package.json').version")
-          else
-            VERSION="${GITHUB_REF#refs/tags/v}"
-          fi
-          echo "version=$VERSION" >> $GITHUB_OUTPUT
-          echo "Publishing skill version: $VERSION"
-
-      - name: Publish to npm
-        working-directory: skills/flvx-api
-        run: npm publish --provenance --access public
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Create GitHub Release
-        if: github.event_name == 'push'
-        uses: softprops/action-gh-release@v1
-        with:
-          name: Skill v${{ steps.version.outputs.version }}
-          generate_release_notes: true
-          files: skills/flvx-api/package.json
@@ -176,8 +176,6 @@ build/
 *.so
 *.dylib
 your_app.exe
-go-backend/paneld
-go-gost/gost

 # Go 测试二进制文件
 *.test
@@ -258,16 +256,4 @@ gitee/
 *.cert
 doraemon.jks
 device.id
-commit.sh
-.opencode/
-analysis/
-sql/
-!go-backend/internal/store/sqlite/sql/
-!go-backend/internal/store/sqlite/sql/schema.sql
-!go-backend/internal/store/sqlite/sql/data.sql
-!go-backend/internal/store/postgres/sql/
-!go-backend/internal/store/postgres/sql/schema.sql
-!go-backend/internal/store/postgres/sql/data.sql
-go-backend/gost.db-shm
-.gitignore
-go-backend/gost.db-wal
+commit.sh
@@ -1,71 +0,0 @@
-# Plan: 搭建开发环境
-
-## 目标
-为 Flux Panel 项目安装所有缺失的开发依赖，使 3 个子项目都能本地开发和构建。
-
-## 当前状态
-
-### ✅ 已安装
-| 工具 | 版本 | 用途 |
-|------|------|------|
-| Node.js | v20.19.2 | vite-frontend |
-| npm | 9.2.0 | vite-frontend |
-| Go | 1.24.4 | go-gost |
-| Docker | 29.1.4 | 容器化部署 |
-
-### ❌ 缺失
-| 工具 | 需求版本 | 用途 |
-|------|----------|------|
-| Java | 21 | springboot-backend |
-| Maven | 3.x | 构建后端 |
-| Docker Compose | v2 | 容器编排 |
-
---
-
-## 执行任务
-
-### Task 1: 安装 Java 21
-```bash
-apt-get update && apt-get install -y openjdk-21-jdk
-```
-**验证**: `java -version` 应显示 openjdk 21
-
-### Task 2: 安装 Maven
-```bash
-apt-get install -y maven
-```
-**验证**: `mvn -v` 应显示 Maven 3.x
-
-### Task 3: 安装 Docker Compose Plugin
-```bash
-apt-get install -y docker-compose-plugin
-```
-**验证**: `docker compose version` 应显示版本号
-
-### Task 4: 安装前端依赖
-```bash
-cd /root/flux-panel/vite-frontend && npm install
-```
-**验证**: `node_modules/` 目录存在
-
-### Task 5: 验证后端可构建
-```bash
-cd /root/flux-panel/springboot-backend && mvn clean compile -q
-```
-**验证**: 编译成功无错误
-
-### Task 6: 验证 Go 模块
-```bash
-cd /root/flux-panel/go-gost && go mod download
-```
-**验证**: 依赖下载成功
-
---
-
-## 完成标准
- [ ] `java -version` → openjdk 21
- [ ] `mvn -v` → Maven 3.x
- [ ] `docker compose version` → v2.x
- [ ] 前端: `npm run dev` 可启动
- [ ] 后端: `mvn compile` 成功
- [ ] Go: `go build .` 成功
@@ -1,33 +0,0 @@
-# Issue #211: 转发自定义监听IP / 隧道指定连接IP
-
-## 需求总结
-1. **节点**: 高级配置增加"额外IP地址"字段（逗号分隔）
-2. **转发**: 创建/编辑时可指定入口监听IP
-3. **隧道**: 配置出口节点时可指定连接IP
-
---
-
-## 任务清单
-
-### 后端
- [x] 1. 数据模型扩展 - Node/ForwardPort/ChainTunnel 增加字段
- [x] 2. Repository - CreateNode/UpdateNode 处理 extraIPs
- [x] 3. Repository - resolveForwardIngress 使用 forward_port.in_ip
- [x] 4. Repository - GetNodeAllIPs 辅助函数（返回节点所有可用IP）
- [x] 5. Handler - 转发创建/更新处理 inIp 参数
- [x] 6. Handler - 隧道出口节点处理 connectIp 参数
- [x] 7. Handler - 节点API返回 extraIPs 字段
-
-### 前端
- [x] 8. 节点编辑页 - 高级配置增加"额外IP"输入
- [x] 9. 转发编辑弹窗 - 增加"监听IP"下拉选择
- [x] 10. 隧道配置页 - 出口节点增加"连接IP"输入
-
---
-
-## 完成进度
- 开始时间: 2026-03-02
- 完成时间: 2026-03-02
- 完成任务: 10/10
- 后端完成: ✅
- 前端完成: ✅
@@ -1,122 +0,0 @@
-# PROJECT KNOWLEDGE BASE
-
-**Generated:** Thu Feb 26 2026
-**Commit:** 21008cc
-**Branch:** main
-**Tag:** 2.1.5-rc15
-
-## OVERVIEW
-FLVX (formerly Flux Panel) is a traffic forwarding management system built on a forked GOST v3 stack. It ships as a Go-based admin API (SQLite/PostgreSQL) + Vite/React UI + Go forwarding agent, with optional mobile WebView wrappers.
-
-## STRUCTURE
-```
-./
-├── go-gost/               # Go forwarding agent (forked gost + local x/)
-│   └── x/                 # Local fork of github.com/go-gost/x (replace => ./x)
-├── go-backend/            # Go Admin API (GORM + SQLite/PostgreSQL, net/http)
-│   └── tests/contract/    # Integration/contract tests
-├── vite-frontend/         # React/Vite dashboard (shadcn bridge + Tailwind v4)
-│   └── src/shadcn-bridge/heroui/  # HeroUI-compatible facade
-├── docker-compose-v4.yml  # Panel deploy (IPv4-only bridge)
-├── docker-compose-v6.yml  # Panel deploy (IPv6-enabled bridge)
-├── panel_install.sh       # Panel installer/upgrader (downloads compose)
-├── install.sh             # Node installer/upgrader (downloads gost binary)
-└── .github/workflows/     # CI: build/test + Docker push + release artifacts
-```
-
-## WHERE TO LOOK
-| Task | Location | Notes |
-|------|----------|-------|
-| **Deploy (Docker)** | `docker-compose-v4.yml` | Env: `JWT_SECRET`, `BACKEND_PORT`, `FRONTEND_PORT` |
-| **Deploy (IPv6)** | `docker-compose-v6.yml` | Same as v4 + IPv6-enabled bridge |
-| **Panel install** | `panel_install.sh` | Picks v4/v6, generates `JWT_SECRET`, downloads compose |
-| **Node install** | `install.sh` | Installs `/etc/flux_agent/flux_agent` + writes `config.json`/`gost.json` + systemd `flux_agent.service` |
-| **Admin API** | `go-backend/` | Go Admin API (SQLite/PostgreSQL) |
-| **Web UI** | `vite-frontend/` | React/Vite dashboard (shadcn bridge + Tailwind v4) |
-| **UI Compatibility** | `vite-frontend/src/shadcn-bridge/heroui/` | HeroUI-compatible API wrappers backed by shadcn/radix |
-| **Theme Tokens** | `vite-frontend/src/styles/tailwind-theme.pcss` | Tailwind v4 `@theme inline` semantic color mapping |
-| **Go Agent** | `go-gost/` | Forwarding agent (forked gost + local x/) |
-| **Go Core** | `go-gost/x/` | Handlers/listeners/dialers + management API |
-| **Repository Layer** | `go-backend/internal/store/repo/` | GORM data access (repository.go 83k LOC) |
-| **Contract Tests** | `go-backend/tests/contract/` | Integration tests for auth, federation, tunnels |
-| **CI Workflows** | `.github/workflows/` | ci-build.yml, docker-build.yml, deploy-docs.yml |
-
-## CODE MAP
-| Symbol | Type | Location | Role |
-|--------|------|----------|------|
-| `flvx` | Project | `.` | Root directory |
-| `main` | Func | `go-backend/cmd/paneld/main.go` | Backend Entry |
-| `App` | Component | `vite-frontend/src/App.tsx` | Frontend Entry |
-| `main` | Func | `go-gost/main.go` | Agent Entry |
-| `Repository` | Struct | `go-backend/internal/store/repo/repository.go` | Data Access Layer |
-| `Handler` | Struct | `go-backend/internal/http/handler/handler.go` | HTTP Handlers |
-| `websocket_reporter` | Func | `go-gost/x/socket/websocket_reporter.go` | Panel Telemetry |
-
-## CONVENTIONS
- **Auth**: `Authorization` header carries the raw JWT token (no `Bearer` prefix) between `vite-frontend/` and `go-backend/`.
- **Module Fork**: `go-gost/` uses `replace github.com/go-gost/x => ./x` and `go-gost/x/` is also its own Go module.
- **Encryption**: Agent-to-panel communication uses AES encryption with node `secret` as PSK.
- **API Envelope**: All REST responses follow `{code, msg, data, ts}` structure (code 0 = success).
- **Frontend UI Layer**: Import UI primitives from `src/shadcn-bridge/heroui/*` (legacy-compatible facade), not direct `@heroui/*` packages.
- **Tailwind v4 Semantic Colors**: `src/styles/globals.css` must import `src/styles/tailwind-theme.pcss`; removing it breaks semantic classes like `bg-primary`, `text-foreground`, and `border-input`.
- **Go Versions**: `go-backend` uses Go 1.24, `go-gost` uses Go 1.23, `go-gost/x` uses Go 1.22.
-
-## ANTI-PATTERNS (THIS PROJECT)
- **DO NOT EDIT** generated protobuf output: `go-gost/x/internal/util/grpc/proto/*.pb.go`, `go-gost/x/internal/util/grpc/proto/*_grpc.pb.go`.
- **DO NOT ADD** `Bearer` prefix to Authorization header - expects raw JWT token.
- **DO NOT MODIFY** `install.sh` or `panel_install.sh` locally - CI overwrites these on release.
- **DO NOT** let backend handlers call `repo.DB()` directly — add a Repository method instead.
- **DO NOT ADD** frontend tests - project has no test infrastructure (Vitest/Jest not configured).
- **DO NOT REINTRODUCE** `@heroui/*` or `@nextui-org/*` dependencies; migration is now shadcn bridge-based.
- **DO NOT** use `type:jsonb` or `type:serial` in GORM tags (SQLite incompatible).
- **DO NOT** omit `TableName()` on new models — GORM pluralizes by default.
-
-## COMMANDS
-```bash
-# Panel (Docker)
-docker compose -f docker-compose-v4.yml up -d
-docker compose -f docker-compose-v6.yml up -d
-
-# Release-based install scripts
-./panel_install.sh
-./install.sh
-
-# Local dev (per subproject)
-(cd go-backend && make build)
-(cd vite-frontend && npm run dev)
-(cd go-gost && go run .)
-
-# Testing
-(cd go-backend && go test ./...)
-(cd go-backend && go test ./tests/contract/...)
-```
-
-## UNIQUE STYLES
- **Flat Monorepo**: Language-prefixed dirs (`go-backend`, `go-gost`, `vite-frontend`) instead of `apps/`/`libs/`.
- **Asymmetric Go Layout**: `go-backend` follows `cmd/<app>/main.go` while `go-gost` uses `root/main.go`.
- **Frontend Hybrid Mode**: `App.tsx` detects "H5 mode" (mobile WebView) vs desktop, dictating layout strategy.
- **Experimental Bundler**: `vite-frontend` uses `rolldown-vite` (Rust-based) instead of standard Vite.
- **Non-minified Builds**: `vite.config.ts` sets `minify: false`, `treeshake: false` for debugging.
-
-## NOTES
- LSP servers are not installed in this environment (gopls/typescript-language-server); rely on grep-based navigation.
- `vite-frontend/vite.config.ts` sets `minify: false` and disables treeshake; expect larger bundles.
- `vite-frontend` uses `rolldown-vite` (experimental Rust bundler) instead of standard Vite.
- Install scripts (`install.sh`, `panel_install.sh`) self-delete after execution - common pattern in one-liner installs.
- CI uses UPX compression (`--best --lzma`) on Go binaries before release.
- CI dynamically injects `PINNED_VERSION` into install scripts and docker-compose files during releases.
- `panel_install.sh` auto-detects IPv6 and modifies `/etc/docker/daemon.json` to enable IPv6 bridge.
- Download proxy `https://gcode.hostcentral.cc/` used for GitHub downloads in China/restricted environments.
- Backend has contract tests in `go-backend/tests/contract/` - frontend has no test infrastructure.
- `analysis/3x-ui/` contains a separate git repo for reference/comparison - not part of FLVX core.
- CI workflows: `ci-build.yml` (build check), `docker-build.yml` (multi-arch images + release), `deploy-docs.yml` (MkDocs).
- PostgreSQL migration supported via `panel_install.sh` menu option using pgloader.
- Repository layer is large: `repository.go` (83k LOC), `repository_mutations.go` (43k LOC).
- Button visual parity relies on `vite-frontend/src/shadcn-bridge/heroui/button.tsx` color mapping + `vite-frontend/src/styles/tailwind-theme.pcss` token export.
-
-## PLAN DOCUMENT RULE
- Every new implementation plan must have a dedicated Markdown plan document.
- Store plan documents under `plans/`.
- Use an incrementing numeric prefix and a short plan-summary name: `NNN-<plan-summary>.md` (for example, `001-auth-refactor.md`, `002-federation-api-cleanup.md`).
- The numeric prefix must increase by 1 for each new plan.
- In each plan document, keep a task checklist and mark each task as completed immediately after finishing it.
@@ -1,148 +0,0 @@
-# 限速功能重构实施计划
-
-## 一、需求概述
-
-**原始需求**: 限速功能当前绑定到具体隧道，需要改为不绑定隧道，创建限速后可以自由在隧道上限速，也可以在转发上限速。
-
-**核心变更**:
-1. 限速规则(SpeedLimit)与隧道的绑定关系改为可选
-2. 转发(Forward)支持独立的限速规则
-
---
-
-## 二、实施计划清单
-
-### 2.0 计划状态（审计更新：2026-02-26）
-
- 总体状态：**进行中（未验收通过）**
- 已完成：模型、仓储查询、限速 CRUD、控制面优先级、限速页与类型改造、编译与测试通过
- 未完成：**Forward 独立限速写入链路**（前端表单 -> API handler -> repository 落库 `forward.speed_id`）
-
-### 2.1 后端模型层 (Model)
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| M1 | SpeedLimit.TunnelID 改为 sql.NullInt64 (可空) | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-| M2 | SpeedLimit.TunnelName 改为 sql.NullString (可空) | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-| M3 | Forward 添加 SpeedID sql.NullInt64 字段 | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-| M4 | ForwardRecord 添加 SpeedID sql.NullInt64 字段 | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-| M5 | SpeedLimitBackup.TunnelID 改为指针类型 | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-| M6 | ForwardBackup 添加 SpeedID *int64 字段 | `go-backend/internal/store/model/model.go` | ✅ 完成 |
-
-### 2.2 后端仓储层 (Repository)
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| R1 | ListSpeedLimits() 返回可空 tunnelId/tunnelName | `go-backend/internal/store/repo/repository.go` | ✅ 完成 |
-| R2 | ListForwards() 返回 speedId 字段 | `go-backend/internal/store/repo/repository.go` | ✅ 完成 |
-| R3 | CreateSpeedLimit() 参数 tunnelID 改为 *int64 | `go-backend/internal/store/repo/repository_mutations.go` | ✅ 完成 |
-| R4 | UpdateSpeedLimit() 参数 tunnelID 改为 *int64 | `go-backend/internal/store/repo/repository_mutations.go` | ✅ 完成 |
-| R5 | GetSpeedLimitTunnelID() 返回 sql.NullInt64 | `go-backend/internal/store/repo/repository_mutations.go` | ✅ 完成 |
-| R6 | exportSpeedLimits() 处理可空字段 | `go-backend/internal/store/repo/repository.go` | ✅ 完成 |
-| R7 | importSpeedLimits() 处理可空字段 | `go-backend/internal/store/repo/repository.go` | ✅ 完成 |
-| R8 | GetSpeedLimitSpeed() 新增方法 | `go-backend/internal/store/repo/repository_flow.go` | ✅ 完成 |
-| R9 | ListForwardsByTunnel() 返回 SpeedID | `go-backend/internal/store/repo/repository_control.go` | ✅ 完成 |
-| R10 | ListActiveForwardsByUser() 返回 SpeedID | `go-backend/internal/store/repo/repository_flow.go` | ✅ 完成 |
-| R11 | ListActiveForwardsByUserTunnel() 返回 SpeedID | `go-backend/internal/store/repo/repository_flow.go` | ✅ 完成 |
-| R12 | GetForwardRecord() 返回 SpeedID | `go-backend/internal/store/repo/repository_flow.go` | ✅ 完成 |
-
-### 2.3 后端处理器层 (Handler)
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| H1 | speedLimitCreate 处理可选 tunnelId | `go-backend/internal/http/handler/mutations.go` | ✅ 完成 |
-| H2 | speedLimitUpdate 处理可选 tunnelId | `go-backend/internal/http/handler/mutations.go` | ✅ 完成 |
-| H3 | speedLimitDelete 处理可空 tunnelID | `go-backend/internal/http/handler/mutations.go` | ✅ 完成 |
-
-### 2.4 后端控制平面 (Control Plane)
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| C1 | syncForwardServices 优先使用 Forward.SpeedID | `go-backend/internal/http/handler/control_plane.go` | ✅ 完成 |
-| C2 | 回退到 UserTunnel 的 speed limit | `go-backend/internal/http/handler/control_plane.go` | ✅ 完成 |
-
-### 2.5 前端类型定义 (TypeScript Types)
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| T1 | SpeedLimitApiItem.tunnelId 改为可选 | `vite-frontend/src/api/types.ts` | ✅ 完成 |
-| T2 | ForwardApiItem 添加 speedId 字段 | `vite-frontend/src/api/types.ts` | ✅ 完成 |
-| T3 | ForwardMutationPayload 添加 speedId 字段 | `vite-frontend/src/api/types.ts` | ✅ 完成 |
-| T4 | SpeedLimitMutationPayload.tunnelId 改为可选 | `vite-frontend/src/api/types.ts` | ✅ 完成 |
-
-### 2.6 前端页面组件
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| F1 | SpeedLimitRule 接口更新 | `vite-frontend/src/pages/limit.tsx` | ✅ 完成 |
-| F2 | SpeedLimitForm 接口更新 | `vite-frontend/src/pages/limit.tsx` | ✅ 完成 |
-| F3 | validateForm 移除 tunnelId 必填校验 | `vite-frontend/src/pages/limit.tsx` | ✅ 完成 |
-| F4 | Select 组件改为可选 | `vite-frontend/src/pages/limit.tsx` | ✅ 完成 |
-| F5 | 显示"未绑定"状态 | `vite-frontend/src/pages/limit.tsx` | ✅ 完成 |
-
-### 2.7 编译验证
-
-| 序号 | 任务 | 状态 |
-|------|------|------|
-| B1 | Go 后端编译通过 | ✅ 完成 |
-| B2 | TypeScript 类型检查通过 | ✅ 完成 |
-| B3 | `go test ./...` 全量通过 | ✅ 完成 |
-| B4 | `go test ./tests/contract/... -run SpeedLimit` 通过 | ✅ 完成 |
-
-### 2.8 Forward 独立限速写入链路补全（新增）
-
-| 序号 | 任务 | 文件 | 状态 |
-|------|------|------|------|
-| N1 | forwardCreate 支持接收并校验可选 speedId，写入 Forward.SpeedID | `go-backend/internal/http/handler/mutations.go` | ✅ 完成 |
-| N2 | forwardUpdate 支持更新/清空 speedId，并触发服务重下发 | `go-backend/internal/http/handler/mutations.go` | ✅ 完成 |
-| N3 | CreateForwardTx 支持落库 speed_id | `go-backend/internal/store/repo/repository_mutations.go` | ✅ 完成 |
-| N4 | UpdateForward 支持更新 speed_id | `go-backend/internal/store/repo/repository_mutations.go` | ✅ 完成 |
-| N5 | Forward 页面新增限速选择并透传 speedId | `vite-frontend/src/pages/forward.tsx` | ✅ 完成 |
-| N6 | Forward 相关契约测试补充 speedId 写入/清空断言 | `go-backend/tests/contract/forward_contract_test.go` | ✅ 完成 |
-
---
-
-## 三、优先级说明
-
-限速规则应用优先级:
-1. **Forward.SpeedID** - 转发级别的限速 (最高优先)
-2. **UserTunnel.SpeedID** - 用户隧道权限级别的限速 (回退)
-
---
-
-## 四、数据库兼容性
-
- SpeedLimit 表: `tunnel_id` 和 `tunnel_name` 字段改为可空 (GORM AutoMigrate 自动处理)
- Forward 表: 新增 `speed_id` 可空字段 (GORM AutoMigrate 自动处理)
-
---
-
-## 五、验证检查项
-
-### 5.1 功能验证（审计后）
-
- [x] 创建不限速规则的限速 (不绑定隧道)
- [x] 创建绑定隧道的限速 (兼容旧逻辑)
- [x] 编辑限速规则，切换隧道绑定状态
- [ ] 删除限速规则
- [ ] 转发列表正确显示 speedId
-
-### 5.2 API 验证（审计后）
-
- [x] GET /api/speed-limit/list 返回可选 tunnelId
- [x] POST /api/speed-limit/create 接受可选 tunnelId
- [x] POST /api/speed-limit/update 接受可选 tunnelId
- [ ] GET /api/forward/list 返回 speedId
-
-### 5.3 兼容性验证（审计后）
-
- [x] 现有绑定隧道的限速规则继续正常工作
- [ ] 现有 UserTunnel 的限速继续正常工作
- [ ] 备份/恢复功能正常
-
-### 5.4 Forward 独立限速闭环验证（新增）
-
- [x] POST /api/forward/create 接受 speedId 并写入 `forward.speed_id`
- [x] POST /api/forward/update 可更新/清空 speedId
- [x] Forward 表单可选择限速并提交 speedId
- [ ] `syncForwardServices` 实际使用 Forward.SpeedID 而非仅回退 UserTunnel.SpeedID
@@ -1,674 +1,201 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 3, 29 June 2007
-
- Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-  The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works.  By contrast,
-the GNU General Public License is intended to guarantee your freedom to
-share and change all versions of a program--to make sure it remains free
-software for all its users.  We, the Free Software Foundation, use the
-GNU General Public License for most of our software; it applies also to
-any other work released this way by its authors.  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-  To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights.  Therefore, you have
-certain responsibilities if you distribute copies of the software, or if
-you modify it: responsibilities to respect the freedom of others.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received.  You must make sure that they, too, receive
-or can get the source code.  And you must show them these terms so they
-know their rights.
-
-  Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-  For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software.  For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-  Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the manufacturer
-can do so.  This is fundamentally incompatible with the aim of
-protecting users' freedom to change the software.  The systematic
-pattern of such abuse occurs in the area of products for individuals to
-use, which is precisely where it is most unacceptable.  Therefore, we
-have designed this version of the GPL to prohibit the practice for those
-products.  If such problems arise substantially in other domains, we
-stand ready to extend this provision to those domains in future versions
-of the GPL, as needed to protect the freedom of users.
-
-  Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish to
-avoid the special danger that patents applied to a free program could
-make it effectively proprietary.  To prevent this, the GPL assures that
-patents cannot be used to render the program non-free.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                       TERMS AND CONDITIONS
-
-  0. Definitions.
-
-  "This License" refers to version 3 of the GNU General Public License.
-
-  "Copyright" also means copyright-like laws that apply to other kinds of
-works, such as semiconductor masks.
-
-  "The Program" refers to any copyrightable work licensed under this
-License.  Each licensee is addressed as "you".  "Licensees" and
-"recipients" may be individuals or organizations.
-
-  To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of an
-exact copy.  The resulting work is called a "modified version" of the
-earlier work or a work "based on" the earlier work.
-
-  A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-  To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy.  Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-  To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies.  Mere interaction with a user through
-a computer network, with no transfer of a copy, is not conveying.
-
-  An interactive user interface displays "Appropriate Legal Notices"
-to the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License.  If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-  1. Source Code.
-
-  The "source code" for a work means the preferred form of the work
-for making modifications to it.  "Object code" means any non-source
-form of a work.
-
-  A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-  The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form.  A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-  The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities.  However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work.  For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-  The Corresponding Source need not include anything that users
-can regenerate automatically from other parts of the Corresponding
-Source.
-
-  The Corresponding Source for a work in source code form is that
-same work.
-
-  2. Basic Permissions.
-
-  All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met.  This License explicitly affirms your unlimited
-permission to run the unmodified Program.  The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work.  This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-  You may make, run and propagate covered works that you do not
-convey, without conditions so long as your license otherwise remains
-in force.  You may convey covered works to others for the sole purpose
-of having them make modifications exclusively for you, or provide you
-with facilities for running those works, provided that you comply with
-the terms of this License in conveying all material for which you do
-not control copyright.  Those thus making or running the covered works
-for you must do so exclusively on your behalf, under your direction
-and control, on terms that prohibit them from making any copies of
-your copyrighted material outside their relationship with you.
-
-  Conveying under any other circumstances is permitted solely under
-the conditions stated below.  Sublicensing is not allowed; section 10
-makes it unnecessary.
-
-  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-  No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-  When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such circumvention
-is effected by exercising rights under this License with respect to
-the covered work, and you disclaim any intention to limit operation or
-modification of the work as a means of enforcing, against the work's
-users, your or third parties' legal rights to forbid circumvention of
-technological measures.
-
-  4. Conveying Verbatim Copies.
-
-  You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-  You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-  5. Conveying Modified Source Versions.
-
-  You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these conditions:
-
-    a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
-
-    b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under section
-    7.  This requirement modifies the requirement in section 4 to
-    "keep intact all notices".
-
-    c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy.  This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged.  This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
-
-    d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-  A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit.  Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-  6. Conveying Non-Source Forms.
-
-  You may convey a covered work in object code form under the terms
-of sections 4 and 5, provided that you also convey the
-machine-readable Corresponding Source under the terms of this License,
-in one of these ways:
-
-    a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
-
-    b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the
-    Corresponding Source from a network server at no charge.
-
-    c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source.  This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
-
-    d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge.  You need not require recipients to copy the
-    Corresponding Source along with the object code.  If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source.  Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
-
-    e) Convey the object code using peer-to-peer transmission, provided
-    you inform other peers where the object code and Corresponding
-    Source of the work are being offered to the general public at no
-    charge under subsection 6d.
-
-  A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-  A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal, family,
-or household purposes, or (2) anything designed or sold for incorporation
-into a dwelling.  In determining whether a product is a consumer product,
-doubtful cases shall be resolved in favor of coverage.  For a particular
-product received by a particular user, "normally used" refers to a
-typical or common use of that class of product, regardless of the status
-of the particular user or of the way in which the particular user
-actually uses, or expects or is expected to use, the product.  A product
-is a consumer product regardless of whether the product has substantial
-commercial, industrial or non-consumer uses, unless such uses represent
-the only significant mode of use of the product.
-
-  "Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to install
-and execute modified versions of a covered work in that User Product from
-a modified version of its Corresponding Source.  The information must
-suffice to ensure that the continued functioning of the modified object
-code is in no case prevented or interfered with solely because
-modification has been made.
-
-  If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information.  But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-  The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or updates
-for a work that has been modified or installed by the recipient, or for
-the User Product in which it has been modified or installed.  Access to a
-network may be denied when the modification itself materially and
-adversely affects the operation of the network or violates the rules and
-protocols for communication across the network.
-
-  Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-  7. Additional Terms.
-
-  "Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law.  If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-  When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it.  (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.)  You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-  Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders of
-that material) supplement the terms of this License with terms:
-
-    a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
-
-    b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
-
-    c) Prohibiting misrepresentation of the origin of that material, or
-    requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
-
-    d) Limiting the use for publicity purposes of names of licensors or
-    authors of the material; or
-
-    e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
-
-    f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions of
-    it) with contractual assumptions of liability to the recipient, for
-    any liability that these contractual assumptions directly impose on
-    those licensors and authors.
-
-  All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10.  If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term.  If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-  If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-  Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions;
-the above requirements apply either way.
-
-  8. Termination.
-
-  You may not propagate or modify a covered work except as expressly
-provided under this License.  Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-  However, if you cease all violation of this License, then your
-license from a particular copyright holder is reinstated (a)
-provisionally, unless and until the copyright holder explicitly and
-finally terminates your license, and (b) permanently, if the copyright
-holder fails to notify you of the violation by some reasonable means
-prior to 60 days after the cessation.
-
-  Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-  Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License.  If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-  9. Acceptance Not Required for Having Copies.
-
-  You are not required to accept this License in order to receive or
-run a copy of the Program.  Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance.  However,
-nothing other than this License grants you permission to propagate or
-modify any covered work.  These actions infringe copyright if you do
-not accept this License.  Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-  10. Automatic Licensing of Downstream Recipients.
-
-  Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License.  You are not responsible
-for enforcing compliance by third parties with this License.
-
-  An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations.  If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-  You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License.  For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-  11. Patents.
-
-  A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based.  The
-work thus licensed is called the contributor's "contributor version".
-
-  A contributor's "essential patent claims" are all patent claims
-owned or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version.  For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-  Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer to sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-  In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement).  To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-  If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients.  "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-  If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-  A patent license is "discriminatory" if it does not include within
-the scope of its coverage, prohibits the exercise of, or is
-conditioned on the non-exercise of one or more of the rights that are
-specifically granted under this License.  You may not convey a covered
-work if you are a party to an arrangement with a third party that is
-in the business of distributing software, under which you make payment
-to the third party based on the extent of your activity of conveying
-the work, and under which the third party grants, to any of the
-parties who would receive the covered work from you, a discriminatory
-patent license (a) in connection with copies of the covered work
-conveyed by you (or copies made from those copies), or (b) primarily
-for and in connection with specific products or compilations that
-contain the covered work, unless you entered into that arrangement,
-or that patent license was granted, prior to 28 March 2007.
-
-  Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-  12. No Surrender of Others' Freedom.
-
-  If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you may
-not convey it at all.  For example, if you agree to terms that obligate you
-to collect a royalty for further conveying from those to whom you convey
-the Program, the only way you could satisfy both those terms and this
-License would be to refrain entirely from conveying the Program.
-
-  13. Use with the GNU Affero General Public License.
-
-  Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work.  The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-  14. Revised Versions of this License.
-
-  The Free Software Foundation may publish revised and/or new versions of
-the GNU General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-  Each version is given a distinguishing version number.  If the
-Program specifies that a certain numbered version of the GNU General
-Public License "or any later version" applies to it, you have the
-option of following the terms and conditions either of that numbered
-version or of any later version published by the Free Software
-Foundation.  If the Program does not specify a version number of the
-GNU General Public License, you may choose any version ever published
-by the Free Software Foundation.
-
-  If the Program specifies that a proxy can decide which future
-versions of the GNU General Public License can be used, that proxy's
-public statement of acceptance of a version permanently authorizes you
-to choose that version for the Program.
-
-  Later license versions may give you additional or different
-permissions.  However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-  15. Disclaimer of Warranty.
-
-  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
-OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
-THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
-PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
-IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
-ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
-
-  16. Limitation of Liability.
-
-  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
-THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
-GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
-USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
-DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
-PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
-EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
-SUCH DAMAGES.
-
-  17. Interpretation of Sections 15 and 16.
-
-  If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-state the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software: you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation, either version 3 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License
-    along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper mail.
-
-  If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-    <program>  Copyright (C) <year>  <name of author>
-    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, your program's commands
-might be different; for a GUI interface, you would use an "about box".
-
-  You should also get your employer (if you work as a programmer) or school,
-if any, to sign a "copyright disclaimer" for the program, if necessary.
-For more information on this, and how to apply and follow the GNU GPL, see
-<https://www.gnu.org/licenses/>.
-
-  The GNU General Public License does not permit incorporating your program
-into proprietary programs.  If your program is a subroutine library, you
-may consider it more useful to permit linking proprietary applications with
-the library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.  But first, please read
-<https://www.gnu.org/licenses/why-not-lgpl.html>.
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
@@ -1,19 +0,0 @@
-FLVX
-Copyright 2026 Sagit-chu
-
-This product includes software developed at
-flux-panel (https://github.com/bqlpfy/flux-panel)
-Copyright 2024-2026 bqlpfy
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-------------------------------------------------------------------------
-This project is a derivative work based on flux-panel.
-Modifications and new components (backend, agents, frontend updates) 
-are licensed under the GNU General Public License v3.0 (GPLv3).
-See the LICENSE file for the full GPLv3 text.
-------------------------------------------------------------------------
@@ -1,8 +1,25 @@
-# FLVX
+# flux-panel转发面板 哆啦A梦转发面板

-> **联系我们**: [Telegram群组](https://t.me/flvxpanel)
+# 赞助商
+<p align="center">
+  <a href="https://vps.town" style="margin: 0 20px; text-align:center;">
+    <img src="./doc/vpstown.png" width="300">
+  </a>
+
+  <a href="https://whmcs.as211392.com" style="margin: 0 20px; text-align:center;">
+    <img src="./doc/as211392.png" width="300">
+  </a>
+</p>


+
+
+使用1.x版本的请使用上面给出的脚本，不要使用最新的，最新的默认2.x
+嫌弃麻烦或者想稳定的我不推荐你升级到2.x版本 目前还在beta阶段，很多问题。
+
+
+本项目基于 [go-gost/gost](https://github.com/go-gost/gost) 和 [go-gost/x](https://github.com/go-gost/x) 两个开源库，实现了转发面板。
+---
 ## 特性

 - 支持按 **隧道账号级别** 管理流量转发数量，可用于用户/隧道配额控制
@@ -11,110 +28,32 @@
 - 可针对 **指定用户的指定隧道进行限速** 设置
 - 支持配置 **单向或双向流量计费方式**，灵活适配不同计费模型
 - 提供灵活的转发策略配置，适用于多种网络场景
- 面板分享，支持将节点分享给其他人，面板对接面板
- 支持分组权限管理，隧道分组、用户分组
- 支持批量功能，可以批量下发配置，启停等
- 支持隧道修改配置、转发修改隧道


 ## 部署流程
 ---
 ### Docker Compose部署
-#### 快速部署（安装最新版）
-面板端：
+#### 快速部署
+面板端(稳定版)：
 ```bash
-curl -L https://raw.githubusercontent.com/Sagit-chu/flux-panel/main/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
+curl -L https://raw.githubusercontent.com/bqlpfy/flux-panel/refs/heads/main/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
 ```
-节点端：
+节点端(稳定版)：
 ```bash
-curl -L https://raw.githubusercontent.com/Sagit-chu/flux-panel/main/install.sh -o install.sh && chmod +x install.sh && ./install.sh
+curl -L https://raw.githubusercontent.com/bqlpfy/flux-panel/refs/heads/main/install.sh -o install.sh && chmod +x install.sh && ./install.sh
+
 ```

-#### 安装特定版本
-从 [Releases](https://github.com/Sagit-chu/flux-panel/releases) 页面复制对应版本的安装命令，脚本会自动安装该版本而非最新版。
-
-面板端（以 2.1.0 为例）：
+面板端(开发版)：
 ```bash
-curl -L https://github.com/Sagit-chu/flux-panel/releases/download/2.1.0/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
+curl -L https://raw.githubusercontent.com/bqlpfy/flux-panel/refs/heads/beta/panel_install.sh -o panel_install.sh && chmod +x panel_install.sh && ./panel_install.sh
 ```
-节点端（以 2.1.0 为例）：
+节点端(开发版)：
 ```bash
-curl -L https://github.com/Sagit-chu/flux-panel/releases/download/2.1.0/install.sh -o install.sh && chmod +x install.sh && ./install.sh
+curl -L https://raw.githubusercontent.com/bqlpfy/flux-panel/refs/heads/beta/install.sh -o install.sh && chmod +x install.sh && ./install.sh
+
 ```

-#### PostgreSQL 部署（Docker Compose）
-
-安装脚本会根据环境自动下载对应的 Compose 配置并保存为 `docker-compose.yml`。默认仍使用 SQLite，切换到 PostgreSQL 只需要配置环境变量。
-
-1) 在 `docker-compose` 同目录创建或修改 `.env`：
-
-```bash
-JWT_SECRET=replace_with_your_secret
-BACKEND_PORT=6365
-FRONTEND_PORT=6366
-
-DB_TYPE=postgres
-DATABASE_URL=postgres://flux_panel:replace_with_strong_password@postgres:5432/flux_panel?sslmode=disable
-
-POSTGRES_DB=flux_panel
-POSTGRES_USER=flux_panel
-POSTGRES_PASSWORD=replace_with_strong_password
-```
-
-> 📌 使用安装脚本部署时，`POSTGRES_PASSWORD` 会自动随机生成并写入 `.env`。
-
-2) 启动服务：
-
-```bash
-docker compose up -d
-```
-
-3) 如果你想继续使用 SQLite，保留 `DB_TYPE=sqlite`（或不设置 `DB_TYPE`）即可。
-
-#### 从 SQLite 迁移到 PostgreSQL
-
-如果你是通过 `panel_install.sh` 安装面板，推荐直接使用脚本菜单一键迁移：
-
-```bash
-./panel_install.sh
-# 选择 4. 迁移到 PostgreSQL
-```
-
-脚本会自动完成 SQLite 备份、PostgreSQL 启动、`pgloader` 导入、`.env` 中 `DB_TYPE`/`DATABASE_URL` 更新，并重启服务。
-
-如果你希望手动迁移，以下示例基于 Docker Volume `sqlite_data`（项目默认配置）与 `pgloader`：
-
-1) 停止服务并备份 SQLite 数据：
-
-```bash
-docker compose down
-docker run --rm -v sqlite_data:/data -v "$(pwd)":/backup alpine sh -c "cp /data/gost.db /backup/gost.db.bak"
-```
-
-2) 仅启动 PostgreSQL：
-
-```bash
-docker compose up -d postgres
-```
-
-3) 使用 `pgloader` 迁移：
-
-```bash
-source .env
-docker run --rm --network gost-network -v sqlite_data:/sqlite dimitri/pgloader:latest pgloader /sqlite/gost.db "postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB}"
-```
-
-4) 切换后端到 PostgreSQL 并启动：
-
-```bash
-source .env
-export DB_TYPE=postgres
-export DATABASE_URL="postgresql://${POSTGRES_USER}:${POSTGRES_PASSWORD}@postgres:5432/${POSTGRES_DB}?sslmode=disable"
-docker compose up -d
-```
-
-5) 迁移完成后，登录面板检查用户、隧道、转发、节点数据是否正确。
-
 #### 默认管理员账号

 - **账号**: admin_user
@@ -122,38 +61,6 @@ docker compose up -d

 > ⚠️ 首次登录后请立即修改默认密码！

---
-## Original Project
- **Name**: flux-panel
- **Source**: https://github.com/bqlpfy/flux-panel
- **License**: Apache License 2.0
-
-## Modifications
-This fork (FLVX) is no longer a light patch on top of the upstream project. It has been deeply reworked, with both backend and frontend rebuilt around a Go-based architecture.
-
-### 1. Backend (Rewritten)
- **Removed**: The original `springboot-backend/` (Java/Spring Boot) implementation.
- **Added**: A fully rewritten `go-backend/` service (Go), including updated data and API handling for panel management.
-
-### 2. Frontend (Reworked)
- **Reworked**: `vite-frontend/` has been substantially rebuilt to match the new backend contract and current UI layer architecture.
- **Updated**: Dashboard pages/components and interaction flows for the current React/Vite stack.
-
-### 3. Forwarding Stack (Modified)
- **Modified**: `go-gost/` forwarding agent wrapper.
- **Modified**: `go-gost/x/` local fork of `github.com/go-gost/x`.
-
-### 4. Mobile Clients (Removed)
- **Removed**: `android-app/` source code.
- **Removed**: `ios-app/` source code.
-
-### 5. Deployment & Project Infrastructure
- **Updated**: Docker deployment templates and installer output flow (IPv4/IPv6 compose variants).
- **Updated**: Release installation scripts (`install.sh`, `panel_install.sh`) and supporting automation.
- **Added/Updated**: Project-level engineering documentation (for example `AGENTS.md`).
-
---
-

 ## 免责声明

@@ -177,14 +84,16 @@ This fork (FLVX) is no longer a light patch on top of the upstream project. It h
 作者对因使用本项目所造成的任何直接或间接损失概不负责，亦不提供任何形式的担保、承诺或技术支持。  


-请务必在合法、合规、安全的前提下使用本项目。
+请务必在合法、合规、安全的前提下使用本项目。  

 ---
 ## ⭐ 喝杯咖啡！（USDT）

 | 网络       | 地址                                                                 |
 |------------|----------------------------------------------------------------------|
-| BNB(BEP20) | `0xa608708fdc6279a2433fd4b82f0b72b8cbe97ed5`                          |
-| TRC20      | `TM8VYdU3s3gSX5PC8swjAJrAzZFCHKqG2k`                                  |
-| Aptos      | `0x49427bfcba1006a346447430689b2307ac156316bb34850d1d3029ff9d118da5`  |
-| polygon    |  `0xa608708fdc6279a2433fd4b82f0b72b8cbe97ed5`    |
+| BNB(BEP20) | `0x755492c03728851bbf855daa28a1e089f9aca4d1`                          |
+| TRC20      | `TYh2L3xxXpuJhAcBWnt3yiiADiCSJLgUm7`                                  |
+| Aptos      | `0xf2f9fb14749457748506a8281628d556e8540d1eb586d202cd8b02b99d369ef8`  |
+
+[![Star History Chart](https://api.star-history.com/svg?repos=bqlpfy/flux-panel&type=Date)](https://www.star-history.com/#bqlpfy/flux-panel&Date)
+
@@ -0,0 +1,15 @@
+*.iml
+.gradle
+/local.properties
+/.idea/caches
+/.idea/libraries
+/.idea/modules.xml
+/.idea/workspace.xml
+/.idea/navEditor.xml
+/.idea/assetWizardSettings.xml
+.DS_Store
+/build
+/captures
+.externalNativeBuild
+.cxx
+local.properties
@@ -0,0 +1 @@
+/build
@@ -0,0 +1,45 @@
+plugins {
+    id 'com.android.application'
+    id 'org.jetbrains.kotlin.android'
+}
+
+android {
+    namespace 'com.flux'
+    compileSdk 34
+
+    defaultConfig {
+        applicationId "com.flux"
+        minSdk 24
+        targetSdk 34
+        versionCode 1
+        versionName "1.0.1"
+
+        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
+    }
+
+    buildTypes {
+        release {
+            minifyEnabled false
+            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
+        }
+    }
+    compileOptions {
+        sourceCompatibility JavaVersion.VERSION_1_8
+        targetCompatibility JavaVersion.VERSION_1_8
+    }
+    kotlinOptions {
+        jvmTarget = '1.8'
+    }
+}
+
+dependencies {
+
+    implementation 'androidx.core:core-ktx:1.9.0'
+    implementation 'androidx.appcompat:appcompat:1.7.1'
+    implementation 'com.google.android.material:material:1.12.0'
+    implementation 'androidx.constraintlayout:constraintlayout:2.2.1'
+    implementation 'androidx.webkit:webkit:1.8.0'
+    testImplementation 'junit:junit:4.13.2'
+    androidTestImplementation 'androidx.test.ext:junit:1.3.0'
+    androidTestImplementation 'androidx.test.espresso:espresso-core:3.7.0'
+}
@@ -0,0 +1,21 @@
+# Add project specific ProGuard rules here.
+# You can control the set of applied configuration files using the
+# proguardFiles setting in build.gradle.
+#
+# For more details, see
+#   http://developer.android.com/guide/developing/tools/proguard.html
+
+# If your project uses WebView with JS, uncomment the following
+# and specify the fully qualified class name to the JavaScript interface
+# class:
+#-keepclassmembers class fqcn.of.javascript.interface.for.webview {
+#   public *;
+#}
+
+# Uncomment this to preserve the line number information for
+# debugging stack traces.
+#-keepattributes SourceFile,LineNumberTable
+
+# If you keep the line number information, uncomment this to
+# hide the original source file name.
+#-renamesourcefileattribute SourceFile
@@ -0,0 +1,20 @@
+{
+  "version": 3,
+  "artifactType": {
+    "type": "APK",
+    "kind": "Directory"
+  },
+  "applicationId": "com.flux",
+  "variantName": "release",
+  "elements": [
+    {
+      "type": "SINGLE",
+      "filters": [],
+      "attributes": [],
+      "versionCode": 1,
+      "versionName": "1.0.1",
+      "outputFile": "app-release.apk"
+    }
+  ],
+  "elementType": "File"
+}
@@ -0,0 +1,24 @@
+package com.flux
+
+import androidx.test.platform.app.InstrumentationRegistry
+import androidx.test.ext.junit.runners.AndroidJUnit4
+
+import org.junit.Test
+import org.junit.runner.RunWith
+
+import org.junit.Assert.*
+
+/**
+ * Instrumented test, which will execute on an Android device.
+ *
+ * See [testing documentation](http://d.android.com/tools/testing).
+ */
+@RunWith(AndroidJUnit4::class)
+class ExampleInstrumentedTest {
+    @Test
+    fun useAppContext() {
+        // Context of the app under test.
+        val appContext = InstrumentationRegistry.getInstrumentation().targetContext
+        assertEquals("com.flux", appContext.packageName)
+    }
+}
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="utf-8"?>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:tools="http://schemas.android.com/tools"
+    package="com.flux" >
+
+    <uses-permission android:name="android.permission.INTERNET" />
+    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
+
+    <application
+        android:allowBackup="true"
+        android:dataExtractionRules="@xml/data_extraction_rules"
+        android:fullBackupContent="@xml/backup_rules"
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/app_name"
+        android:roundIcon="@mipmap/ic_launcher_round"
+        android:supportsRtl="true"
+        android:theme="@style/Theme.Flux"
+        android:usesCleartextTraffic="true"
+        tools:targetApi="31" >
+        <activity
+            android:name="com.flux.MainActivity"
+            android:exported="true"
+            android:configChanges="uiMode|orientation|screenSize" >
+            <intent-filter>
+                <action android:name="android.intent.action.MAIN" />
+
+                <category android:name="android.intent.category.LAUNCHER" />
+            </intent-filter>
+        </activity>
+    </application>
+
+</manifest>
@@ -0,0 +1,214 @@
+package com.flux
+
+import androidx.core.content.edit
+import android.graphics.Color
+import android.os.Build
+import android.os.Bundle
+import android.view.View
+import android.view.WindowInsetsController
+import androidx.appcompat.app.AppCompatActivity
+import android.webkit.*
+import android.content.res.Configuration
+import org.json.JSONArray
+import org.json.JSONObject
+
+
+class MainActivity : AppCompatActivity() {
+
+    private lateinit var webView: WebView
+
+    override fun onCreate(savedInstanceState: Bundle?) {
+        super.onCreate(savedInstanceState)
+        setContentView(R.layout.activity_main)
+
+        webView = findViewById(R.id.webView)
+        WebView.setWebContentsDebuggingEnabled(true)
+        setupWebView()
+        loadUrl()
+
+        setupSystemBars()
+        setupRootBackground()
+    }
+
+    private fun setupWebView() {
+        val settings = webView.settings
+        settings.javaScriptEnabled = true
+        settings.domStorageEnabled = true
+        settings.databaseEnabled = true
+        settings.loadWithOverviewMode = true
+        settings.useWideViewPort = true
+        settings.setSupportZoom(true)
+        settings.builtInZoomControls = true
+        settings.displayZoomControls = false
+
+        // 隐藏滚动条但不影响滚动
+        webView.isVerticalScrollBarEnabled = false
+        webView.isHorizontalScrollBarEnabled = false
+        webView.scrollBarStyle = View.SCROLLBARS_INSIDE_OVERLAY
+        webView.overScrollMode = View.OVER_SCROLL_NEVER
+
+
+        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
+            settings.mixedContentMode = WebSettings.MIXED_CONTENT_ALWAYS_ALLOW
+        }
+
+        val isDarkTheme = resources.configuration.uiMode and
+                Configuration.UI_MODE_NIGHT_MASK ==
+                Configuration.UI_MODE_NIGHT_YES
+
+        webView.setBackgroundColor(if (isDarkTheme) Color.BLACK else Color.WHITE)
+
+
+        // 添加JavaScript接口
+        webView.addJavascriptInterface(object {
+
+            @android.webkit.JavascriptInterface
+            fun getPanelAddresses(callback: String) {
+                val sharedPrefs = getSharedPreferences("panel_config", MODE_PRIVATE)
+                val addresses = sharedPrefs.getString("panel_addresses", "[]")
+                webView.post {
+                    webView.evaluateJavascript("window.$callback($addresses);", null)
+                }
+            }
+
+            @android.webkit.JavascriptInterface
+            fun savePanelAddress(name: String, address: String) {
+                val json = JSONObject()
+                json.put("name", name)
+                json.put("address", address)
+                json.put("inx", false)
+                val sharedPrefs = getSharedPreferences("panel_config", MODE_PRIVATE)
+                val addresses = sharedPrefs.getString("panel_addresses", "[]")
+                val jsonArray = JSONArray(addresses)
+                jsonArray.put(json)
+                sharedPrefs.edit {
+                    putString("panel_addresses", jsonArray.toString())
+                }
+                webView.post {
+                    webView.evaluateJavascript("window.setPanelAddresses(${jsonArray.toString()});", null)
+                }
+            }
+
+            @android.webkit.JavascriptInterface
+            fun setCurrentPanelAddress(name: String) {
+
+                val sharedPrefs = getSharedPreferences("panel_config", MODE_PRIVATE)
+                val addresses = sharedPrefs.getString("panel_addresses", "[]")
+                val jsonArray = JSONArray(addresses)
+                for (i in 0 until jsonArray.length()) {
+                    val obj = jsonArray.getJSONObject(i)
+                    if (name == obj.getString("name")) {
+                        obj.put("inx", true)
+                    }else{
+                        obj.put("inx", false)
+                    }
+                }
+                sharedPrefs.edit {
+                    putString("panel_addresses", jsonArray.toString())
+                }
+                webView.post {
+                    webView.evaluateJavascript("window.setPanelAddresses(${jsonArray.toString()});", null)
+                }
+            }
+
+            @android.webkit.JavascriptInterface
+            fun deletePanelAddress(name: String) {
+                val jsonArray = JSONArray()
+                val sharedPrefs = getSharedPreferences("panel_config", MODE_PRIVATE)
+                val addresses = sharedPrefs.getString("panel_addresses", "[]")
+                val jsonArraya = JSONArray(addresses)
+                for (i in 0 until jsonArraya.length()) {
+                    val obj = jsonArraya.getJSONObject(i)
+                    if (name != obj.getString("name")) {
+                        jsonArray.put(obj)
+                    }
+                }
+                sharedPrefs.edit {
+                    putString("panel_addresses", jsonArray.toString())
+                }
+                webView.post {
+                    webView.evaluateJavascript("window.setPanelAddresses(${jsonArray.toString()});", null)
+                }
+            }
+        }, "JsInterface")
+
+    }
+
+    private fun loadUrl() {
+        //webView.loadUrl("http://192.168.100.9:3000")
+        webView.loadUrl("file:///android_asset/index.html")
+    }
+
+    private fun setupSystemBars() {
+        val isDarkTheme = resources.configuration.uiMode and
+                Configuration.UI_MODE_NIGHT_MASK ==
+                Configuration.UI_MODE_NIGHT_YES
+
+        if (isDarkTheme) {
+            window.statusBarColor = Color.BLACK
+            window.navigationBarColor = Color.BLACK
+            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
+                window.insetsController?.setSystemBarsAppearance(
+                    0,
+                    WindowInsetsController.APPEARANCE_LIGHT_STATUS_BARS or
+                            WindowInsetsController.APPEARANCE_LIGHT_NAVIGATION_BARS
+                )
+            } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
+                @Suppress("DEPRECATION")
+                window.decorView.systemUiVisibility =
+                    window.decorView.systemUiVisibility and View.SYSTEM_UI_FLAG_LIGHT_STATUS_BAR.inv()
+                if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
+                    @Suppress("DEPRECATION")
+                    window.decorView.systemUiVisibility =
+                        window.decorView.systemUiVisibility and View.SYSTEM_UI_FLAG_LIGHT_NAVIGATION_BAR.inv()
+                }
+            }
+        } else {
+            window.statusBarColor = Color.WHITE
+            window.navigationBarColor = Color.WHITE
+            if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
+                window.insetsController?.setSystemBarsAppearance(
+                    WindowInsetsController.APPEARANCE_LIGHT_STATUS_BARS or
+                            WindowInsetsController.APPEARANCE_LIGHT_NAVIGATION_BARS,
+                    WindowInsetsController.APPEARANCE_LIGHT_STATUS_BARS or
+                            WindowInsetsController.APPEARANCE_LIGHT_NAVIGATION_BARS
+                )
+            } else if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
+                @Suppress("DEPRECATION")
+                window.decorView.systemUiVisibility =
+                    window.decorView.systemUiVisibility or View.SYSTEM_UI_FLAG_LIGHT_STATUS_BAR
+                if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {
+                    @Suppress("DEPRECATION")
+                    window.decorView.systemUiVisibility =
+                        window.decorView.systemUiVisibility or View.SYSTEM_UI_FLAG_LIGHT_NAVIGATION_BAR
+                }
+            }
+        }
+    }
+
+    override fun onBackPressed() {
+        if (webView.canGoBack()) webView.goBack() else super.onBackPressed()
+    }
+
+    override fun onConfigurationChanged(newConfig: Configuration) {
+        super.onConfigurationChanged(newConfig)
+        setupSystemBars()
+        setupWebViewBackground()
+        setupRootBackground()
+    }
+
+    private fun setupWebViewBackground() {
+        val isDarkTheme = resources.configuration.uiMode and
+                Configuration.UI_MODE_NIGHT_MASK ==
+                Configuration.UI_MODE_NIGHT_YES
+        webView.setBackgroundColor(if (isDarkTheme) Color.BLACK else Color.WHITE)
+    }
+
+    private fun setupRootBackground() {
+        val isDarkTheme = resources.configuration.uiMode and
+                Configuration.UI_MODE_NIGHT_MASK ==
+                Configuration.UI_MODE_NIGHT_YES
+        val rootView = findViewById<View>(android.R.id.content)
+        rootView.setBackgroundColor(if (isDarkTheme) Color.BLACK else Color.WHITE)
+    }
+}
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="utf-8"?>
+<vector
+    android:height="108dp"
+    android:width="108dp"
+    android:viewportHeight="108"
+    android:viewportWidth="108"
+    xmlns:android="http://schemas.android.com/apk/res/android">
+    <path android:fillColor="#3DDC84"
+          android:pathData="M0,0h108v108h-108z"/>
+    <path android:fillColor="#00000000" android:pathData="M9,0L9,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,0L19,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M29,0L29,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M39,0L39,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M49,0L49,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M59,0L59,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M69,0L69,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M79,0L79,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M89,0L89,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M99,0L99,108"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,9L108,9"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,19L108,19"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,29L108,29"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,39L108,39"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,49L108,49"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,59L108,59"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,69L108,69"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,79L108,79"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,89L108,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M0,99L108,99"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,29L89,29"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,39L89,39"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,49L89,49"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,59L89,59"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,69L89,69"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M19,79L89,79"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M29,19L29,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M39,19L39,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M49,19L49,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M59,19L59,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M69,19L69,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+    <path android:fillColor="#00000000" android:pathData="M79,19L79,89"
+          android:strokeColor="#33FFFFFF" android:strokeWidth="0.8"/>
+</vector>
@@ -0,0 +1,30 @@
+<vector xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:aapt="http://schemas.android.com/aapt"
+    android:width="108dp"
+    android:height="108dp"
+    android:viewportWidth="108"
+    android:viewportHeight="108">
+    <path android:pathData="M31,63.928c0,0 6.4,-11 12.1,-13.1c7.2,-2.6 26,-1.4 26,-1.4l38.1,38.1L107,108.928l-32,-1L31,63.928z">
+        <aapt:attr name="android:fillColor">
+            <gradient
+                android:endX="85.84757"
+                android:endY="92.4963"
+                android:startX="42.9492"
+                android:startY="49.59793"
+                android:type="linear">
+                <item
+                    android:color="#44000000"
+                    android:offset="0.0" />
+                <item
+                    android:color="#00000000"
+                    android:offset="1.0" />
+            </gradient>
+        </aapt:attr>
+    </path>
+    <path
+        android:fillColor="#FFFFFF"
+        android:fillType="nonZero"
+        android:pathData="M65.3,45.828l3.8,-6.6c0.2,-0.4 0.1,-0.9 -0.3,-1.1c-0.4,-0.2 -0.9,-0.1 -1.1,0.3l-3.9,6.7c-6.3,-2.8 -13.4,-2.8 -19.7,0l-3.9,-6.7c-0.2,-0.4 -0.7,-0.5 -1.1,-0.3C38.8,38.328 38.7,38.828 38.9,39.228l3.8,6.6C36.2,49.428 31.7,56.028 31,63.928h46C76.3,56.028 71.8,49.428 65.3,45.828zM43.4,57.328c-0.8,0 -1.5,-0.5 -1.8,-1.2c-0.3,-0.7 -0.1,-1.5 0.4,-2.1c0.5,-0.5 1.4,-0.7 2.1,-0.4c0.7,0.3 1.2,1 1.2,1.8C45.3,56.528 44.5,57.328 43.4,57.328L43.4,57.328zM64.6,57.328c-0.8,0 -1.5,-0.5 -1.8,-1.2s-0.1,-1.5 0.4,-2.1c0.5,-0.5 1.4,-0.7 2.1,-0.4c0.7,0.3 1.2,1 1.2,1.8C66.5,56.528 65.6,57.328 64.6,57.328L64.6,57.328z"
+        android:strokeWidth="1"
+        android:strokeColor="#00000000" />
+</vector>
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?>
+<androidx.constraintlayout.widget.ConstraintLayout
+    xmlns:android="http://schemas.android.com/apk/res/android"
+    xmlns:tools="http://schemas.android.com/tools"
+    xmlns:app="http://schemas.android.com/apk/res-auto"
+    android:layout_width="match_parent"
+    android:layout_height="match_parent"
+    tools:context=".MainActivity">
+
+    <WebView
+        android:id="@+id/webView"
+        android:layout_width="0dp"
+        android:layout_height="0dp"
+        app:layout_constraintBottom_toBottomOf="parent"
+        app:layout_constraintStart_toStartOf="parent"
+        app:layout_constraintEnd_toEndOf="parent"
+        app:layout_constraintTop_toTopOf="parent" />
+
+</androidx.constraintlayout.widget.ConstraintLayout>
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="utf-8"?>
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+    <background android:drawable="@drawable/ic_launcher_background"/>
+    <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
+</adaptive-icon>
@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="utf-8"?>
+<adaptive-icon xmlns:android="http://schemas.android.com/apk/res/android">
+    <background android:drawable="@drawable/ic_launcher_background"/>
+    <foreground android:drawable="@mipmap/ic_launcher_foreground"/>
+</adaptive-icon>
@@ -0,0 +1,9 @@
+<resources xmlns:tools="http://schemas.android.com/tools">
+    <!-- Base application theme. -->
+    <style name="Base.Theme.Flux" parent="Theme.Material3.DayNight.NoActionBar">
+        <!-- Customize your dark theme here. -->
+        <!-- <item name="colorPrimary">@color/my_dark_primary</item> -->
+        <item name="android:statusBarColor">@android:color/transparent</item>
+        <item name="android:navigationBarColor">@android:color/transparent</item>
+    </style>
+</resources>
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="utf-8"?>
+<resources>
+    <color name="black">#FF000000</color>
+    <color name="white">#FFFFFFFF</color>
+
+</resources>
@@ -0,0 +1,3 @@
+<resources>
+    <string name="app_name">Flux</string>
+</resources>
@@ -0,0 +1,11 @@
+<resources xmlns:tools="http://schemas.android.com/tools">
+    <!-- Base application theme. -->
+    <style name="Base.Theme.Flux" parent="Theme.Material3.DayNight.NoActionBar">
+        <!-- Customize your light theme here. -->
+        <!-- <item name="colorPrimary">@color/my_light_primary</item> -->
+        <item name="android:statusBarColor">@android:color/transparent</item>
+        <item name="android:navigationBarColor">@android:color/transparent</item>
+    </style>
+
+    <style name="Theme.Flux" parent="Base.Theme.Flux" />
+</resources>
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="utf-8"?><!--
+   Sample backup rules file; uncomment and customize as necessary.
+   See https://developer.android.com/guide/topics/data/autobackup
+   for details.
+   Note: This file is ignored for devices older that API 31
+   See https://developer.android.com/about/versions/12/backup-restore
+-->
+<full-backup-content>
+    <!--
+   <include domain="sharedpref" path="."/>
+   <exclude domain="sharedpref" path="device.xml"/>
+-->
+</full-backup-content>
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="utf-8"?><!--
+   Sample data extraction rules file; uncomment and customize as necessary.
+   See https://developer.android.com/about/versions/12/backup-restore#xml-changes
+   for details.
+-->
+<data-extraction-rules>
+    <cloud-backup>
+        <!-- TODO: Use <include> and <exclude> to control what is backed up.
+        <include .../>
+        <exclude .../>
+        -->
+    </cloud-backup>
+    <!--
+    <device-transfer>
+        <include .../>
+        <exclude .../>
+    </device-transfer>
+    -->
+</data-extraction-rules>
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
qaq	a155bc64c0	增加稳定版arm支持	2025-11-25 09:43:32 +08:00
qaq	62bd8ea469	修复稳定版面板显示屏蔽协议状态不一致问题	2025-11-25 09:21:36 +08:00
qaq	f3a9684be4	修复稳定版面板显示屏蔽协议状态不一致问题	2025-11-25 09:18:40 +08:00
				`@@ -1 +0,0 @@`
				`在agent.md里规定，每次计划都必须写一个计划文档，md格式，按序号增加和以计划的总结命名，每次完成一个任务做好标记`
				`@@ -1 +0,0 @@`
				`提交全部变更并且push，创建pr合并，发布新tag，alpha版本`
				`@@ -1 +0,0 @@`
				`已提交并推送，PR已创建: https://github.com/Sagit-chu/flvx/pull/new/opencode/mighty-nebula`
				`@@ -1 +0,0 @@`
				已完成 `origin/main` 合并到当前分支（Fast-forward）。之前的更改已恢复，`forward.tsx` 自动合并成功。