council(draft): arch-reviewer - create plan.md with architecture review
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
parent
e7d68ce3e8
commit
f6cb6f65b5
|
|
@ -0,0 +1,76 @@
|
|||
# Council Plan — Round 1
|
||||
|
||||
> Created by: arch-reviewer
|
||||
> Scope: ARCHITECTURE.md + docs/05_AI_PARTICIPATION.md
|
||||
|
||||
---
|
||||
|
||||
## Document Review Results (arch-reviewer)
|
||||
|
||||
### ARCHITECTURE.md — ✅ 通过(需补充)
|
||||
|
||||
**优点**:
|
||||
- 整体架构清晰:ShopXO PHP 后端 + shopxo-uniapp 前端,插件隔离
|
||||
- 数据模型覆盖完整:复用表 + 插件独立表,边界清晰
|
||||
- 购票流程覆盖全链路:后台→前端→支付→核销
|
||||
- 技术栈选择合理,PHP 8 / ThinkPHP 8 / MySQL / phpqrcode 内置
|
||||
- 发现了 7 个 ShopXO 核心技术点(CustomView Ace/30+钩子/按类型替换模板等)
|
||||
|
||||
**⚠️ 需补充**:
|
||||
1. **Plugin/ShopXO 边界模糊**:`plugins_view_goods_detail_base_sku_top` 钩子注入后,票务选座 UI 如何与 ShopXO 原生规格选择共存?两者优先级和切换逻辑未明确
|
||||
2. **item_type 扩展机制缺失**:文档提到修改 `Goods.php Index()` 加 1 行判断,但这等于修改 ShopXO 核心代码,与「不修改核心代码」原则矛盾
|
||||
3. **CustomView 与票务选座的联动**:CustomView 生成静态页面,但票务选座页是动态交互页面(选座/观演人/实时库存),CustomView 无法满足,两者的使用场景边界未定义
|
||||
4. **支付回调链路不完整**:TicketService::OnOrderPaid() 触发后,QR 票发送到哪个渠道(微信服务通知/短信/票夹页)?ShopXO 支付回调机制如何接入未说明
|
||||
5. **vr_tickets 表 QR 数据结构未定义**:QR 包含哪些字段?QR 内容加密方式?
|
||||
|
||||
### docs/05_AI_PARTICIPATION.md — ✅ 通过
|
||||
|
||||
**优点**:
|
||||
- 清晰区分了三类页面:DIY 拖拽(❌)/代码页(✅)/CustomView(✅✅)
|
||||
- DIY JSON 不可逆向的判断正确,有具体证据
|
||||
- AI 参与路线图分三阶段合理
|
||||
- CustomView 作为 AI 黄金入口的判断有说服力
|
||||
|
||||
**⚠️ 需补充**:
|
||||
1. **CustomView 的局限性未说明**:CustomView 适合静态/轻交互页面,票务选座(动态座位图、实时库存)不适合 CustomView,应明确排除
|
||||
2. **AI 生成 CustomView 内容的具体方式未给出**:AI 是生成 HTML 字符串写入数据库哪个字段?需要字段路径
|
||||
|
||||
---
|
||||
|
||||
## Phase Breakdown
|
||||
|
||||
### Phase 1 — Draft(当前)
|
||||
- [ ] arch-reviewer: 完成 ARCHITECTURE.md + 05_AI_PARTICIPATION.md 评审
|
||||
- [ ] backend-reviewer: 完成 01_SHOPXO_TECHNICAL_RESEARCH.md 评审
|
||||
- [ ] ticket-reviewer: 完成 03_VERIFICATION_SYSTEM.md + ARCHITECTURE.md 评审
|
||||
- [ ] pm-reviewer: 完成 04_IMPLEMENTATION_ROADMAP.md + DEPLOYMENT.md + 05_AI_PARTICIPATION.md 评审
|
||||
|
||||
### Phase 2 — Review
|
||||
- [ ] 各 agent 汇总所有文档的评审意见
|
||||
- [ ] 确定是否可以开始编码,或需要哪些补充
|
||||
|
||||
### Phase 3 — Finalize
|
||||
- [ ] 投票决定是否开始编码
|
||||
- [ ] 补充文档合并到 main
|
||||
|
||||
---
|
||||
|
||||
## Claim Status
|
||||
|
||||
| Task | Owner | Status |
|
||||
|---|---|---|
|
||||
| ARCHITECTURE.md 评审 | arch-reviewer | [Done: arch-reviewer] |
|
||||
| 05_AI_PARTICIPATION.md 评审 | arch-reviewer | [Done: arch-reviewer] |
|
||||
| 01_SHOPXO_TECHNICAL_RESEARCH.md 评审 | backend-reviewer | [Pending] |
|
||||
| 03_VERIFICATION_SYSTEM.md 评审 | ticket-reviewer | [Pending] |
|
||||
| 04_IMPLEMENTATION_ROADMAP.md 评审 | pm-reviewer | [Pending] |
|
||||
| DEPLOYMENT.md 评审 | pm-reviewer | [Pending] |
|
||||
|
||||
---
|
||||
|
||||
## Critical Open Questions for Coding
|
||||
|
||||
1. **边界冲突**:Goods.php 修改 vs 不修改核心代码,两者矛盾需要决策
|
||||
2. **CustomView 使用范围**:票务核心交互页(选座/观演人)不应使用 CustomView,需明确排除
|
||||
3. **支付回调接入点**:ShopXO 支付成功回调的钩子名称和调用方式
|
||||
4. **QR 数据结构**:vr_tickets 表结构需要明确定义
|
||||
Loading…
Reference in New Issue