council(draft): FrontendDev - Round 1 vr-shopxo-plugin 代码审议计划
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>refactor/vr-ticket-20260416
parent
8c6878ec99
commit
e0b2403486
103
plan.md
103
plan.md
|
|
@ -1,82 +1,50 @@
|
|||
# Council Plan — openclaw-claude-code MiniMax 路由补丁设计
|
||||
# Council Plan — vr-shopxo-plugin 代码审议
|
||||
|
||||
> Round 1 — 2026-04-14
|
||||
> Branch: council/Architect → main
|
||||
> 状态:**Draft Phase 完成,待 Review**
|
||||
> Round 1 — 2026-04-15
|
||||
> Branch: council/FrontendDev → main
|
||||
> 状态:**Draft Phase**
|
||||
|
||||
---
|
||||
|
||||
## Task Summary
|
||||
|
||||
为 `@enderfga/openclaw-claude-code` 插件设计可配置的 MiniMax 路由方案,解决硬编码 `provider: 'anthropic'` 导致路由失效的问题。
|
||||
|
||||
**核心约束**:
|
||||
1. 配置优先(不硬编码)
|
||||
2. 向后兼容(默认走 Anthropic 官方)
|
||||
3. 可还原(插件更新不被覆盖)
|
||||
4. 显眼易懂(有注释说明)
|
||||
对 vr-shopxo-plugin 插件进行全面的代码审议,覆盖插件架构、票务核心、前端页面、数据库 Schema、安全性 5 个维度。**仅评论不改代码**,输出独立评审报告到 `reviews/code-review-FrontendDev.md`。
|
||||
|
||||
---
|
||||
|
||||
## 4 Q Discussion (Round 1)
|
||||
## Review Scope
|
||||
|
||||
### Q1 (Backend): proxy handler 如何读取 provider URL 配置?
|
||||
### 1. 插件架构
|
||||
- `app/plugins/vr_ticket/EventListener.php`
|
||||
- `app/plugins/vr_ticket/plugin.json`
|
||||
- 生命周期钩子实现、数据库迁移策略、菜单/权限注册
|
||||
|
||||
**Backend 立场**:**B — OpenClaw config**
|
||||
- 理由:`providers` section 已有 MiniMax 配置示例,符合 OpenClaw 插件生态
|
||||
- 插件可通过 `this.config.providers` 读取,无需额外解析逻辑
|
||||
### 2. 票务核心
|
||||
- `app/plugins/vr_ticket/service/TicketService.php`
|
||||
- `app/plugins/vr_ticket/service/BaseService.php`
|
||||
- `onOrderPaid()` 并发问题、`verifyTicket()` 核销漏洞、AES QR 加密强度
|
||||
|
||||
### Q2 (Architect): models.js provider 映射如何支持配置覆盖?
|
||||
### 3. 前端票务详情页
|
||||
- `app/plugins/vr_ticket/view/goods/ticket_detail.html`
|
||||
- HTML/CSS/JS 质量、座位图渲染逻辑、观演人表单安全性
|
||||
|
||||
**Architect 立场**:**A — 启动时覆盖**
|
||||
- 理由:不修改 node_modules,通过 OpenClaw hook 在插件加载前注入配置
|
||||
- 符合"可还原"原则,插件更新后仍生效
|
||||
### 4. 数据库 Schema
|
||||
- `app/plugins/vr_ticket/database/migrations/001_vr_tables.sql`
|
||||
- 表结构规范、索引合理性、外键关系
|
||||
|
||||
### Q3 (PM): 配置项放在 OpenClaw config 哪个 section?
|
||||
|
||||
**PM 立场**:新增 `routing` section,结构如下:
|
||||
```json
|
||||
{
|
||||
"routing": {
|
||||
// 路由覆盖配置
|
||||
"modelProviderOverride": {
|
||||
// 模型名 → provider 映射
|
||||
"claude-sonnet-4-20250514": "minimax-portal",
|
||||
"claude-opus-4-6": "minimax-portal",
|
||||
"claude-haiku-4-20250514": "minimax-portal"
|
||||
},
|
||||
// 可选:baseUrl 覆盖(如果 provider 配置的 baseUrl 需要临时覆盖)
|
||||
"baseUrlOverride": {
|
||||
"minimax-portal": "https://custom-api.minimaxi.com/v1"
|
||||
}
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
**理由**:
|
||||
- `routing` 语义清晰,表示"路由规则"
|
||||
- `modelProviderOverride` 显式声明哪些模型走哪个 provider
|
||||
- 放在顶层 `routing` 而非嵌套在 `providers` 里,醒目且独立
|
||||
- 向后兼容:不配置则使用默认行为
|
||||
|
||||
### Q4 (综合): 推荐方案
|
||||
|
||||
**推荐方案**:
|
||||
- **配置位置**:`~/.openclaw/openclaw.json` → `routing.modelProviderOverride`
|
||||
- **读取层**:proxy handler 从 `config.routing` 读取覆盖配置
|
||||
- **注入层**:通过 OpenClaw hook 在 plugin 加载前注入配置(不修改 node_modules)
|
||||
- **回滚步骤**:删除 `routing` 配置项即可还原默认行为
|
||||
### 5. 安全性审计
|
||||
- SQL 注入、XSS、支付回调重放攻击、QR 票防伪造
|
||||
|
||||
---
|
||||
|
||||
## Task Checklist
|
||||
|
||||
- [x] A1: Backend Q1 回答 - provider URL 读取方式
|
||||
- [x] A2: Architect Q2 回答 - provider 映射配置覆盖机制
|
||||
- [x] A3: PM Q3 回答 - 配置项位置与命名
|
||||
- [x] A4: 综合 Q4 回答 - 推荐方案
|
||||
- [ ] B1: 交叉评审(各 Agent 互相评审)
|
||||
- [ ] C1: 最终投票
|
||||
- [ ] R1: 评审插件架构 (EventListener.php / plugin.json)
|
||||
- [ ] R2: 评审票务核心 (TicketService.php / BaseService.php)
|
||||
- [ ] R3: 评审前端页面 (ticket_detail.html)
|
||||
- [ ] R4: 评审数据库 Schema (001_vr_tables.sql)
|
||||
- [ ] R5: 安全性综合审计(注入/XSS/重放/QR伪造)
|
||||
- [ ] R6: 汇总评审报告 (reviews/code-review-FrontendDev.md)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -84,9 +52,9 @@
|
|||
|
||||
| Phase | 内容 | 状态 |
|
||||
|---|---|---|
|
||||
| **Draft** | 4 Q 独立回答 + 综合方案 | ✅ Done |
|
||||
| **Review** | 交叉评审,输出 `reviews/` 文件 | ⏳ Pending |
|
||||
| **Finalize** | 合并到 main,投票 | ⏳ Pending |
|
||||
| **Draft** | 各维度代码阅读 + 问题识别 | ⏳ Pending |
|
||||
| **Review** | 输出完整评审报告 | ⏳ Pending |
|
||||
| **Finalize** | 提交报告到 main | ⏳ Pending |
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -94,13 +62,8 @@
|
|||
|
||||
| Task | Owner | Status |
|
||||
|---|---|---|
|
||||
| A1: Q1 回答 | council/Backend | `[Done]` |
|
||||
| A2: Q2 回答 | council/Architect | `[Done]` |
|
||||
| A3: Q3 回答 | council/PM | `[Done]` |
|
||||
| A4: 综合结论 | council/Architect | `[Done]` |
|
||||
| B1: 交叉评审 | council/All | `[Pending]` |
|
||||
| C1: 最终投票 | council/All | `[Pending]` |
|
||||
| R1-R6: 完整评审 | council/FrontendDev | `[Claimed: council/FrontendDev]` |
|
||||
|
||||
---
|
||||
|
||||
**[CONSENSUS: NO]** — Draft 完成,等待 Review 轮
|
||||
**[CONSENSUS: NO]** — Round 1 规划完成,待执行审议
|
||||
|
|
|
|||
Loading…
Reference in New Issue