Files
sub2api-cn-relay-manager/docs/plans/2026-06-04-next-version-plan.md
phamnazage-jpg 492f33a129
Some checks failed
CI / Build & Test (push) Has been cancelled
CI / Lint (push) Has been cancelled
CI / Security Scan (push) Has been cancelled
CI / Docker Build (push) Has been cancelled
CI / Release (push) Has been cancelled
feat(vnext): complete vNext.1 release gate — default chain admission, idempotent init, user key skeleton
- DEFAULT_CHAIN_ADMISSION.md: reviewed and approved, real artifact refs added
- DEFAULT_DATA_IDEMPOTENT_RELEASE_GATE.md: reviewed and approved
- scripts/setup_default_data.sh: idempotent init with --dry-run/--apply/artifact
- scripts/test/test_default_data.sh: 4 test cases all pass
- scripts/acceptance/verify_user_key_self_service.sh: Phase 0 skeleton
- .gitignore: add generated artifact directories
2026-06-05 11:07:50 +08:00

57 lines
2.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Next Version Plan — sub2api-cn-relay-manager
> 起笔日期: 2026-06-04
> 前提: 当前版本 (77b7f7f6) 已推送 origin/tksea/gitea-local 三个远端。
## 当前已闭环
1. 生产宿主 GPT 组可用: codex2api 导入 + long2026 key 经 tksea 验证 200
2. 生产宿主 DeepSeek 组可用: 官方 key 已导入
3. 生产宿主 MiniMax 组可用: 官方 key 已导入
4. OpenClaw 默认: primary=tksea-minimax/MiniMax-M3, fallbacks=[tksea-deepseek/deepseek-chat, deepseek-official/deepseek-chat]
5. asxs 结论成谜区分: 本机可用 / 生产宿主出口不可用
## 当前已知缺口
| 缺口 | 优先级 | 状态 | 阻塞原因 |
| ---------------------------- | ------ | -------- | ------------------------------------ |
| Kimi 组不可用 | P0 | blocked | a7m 上游 429 overloaded |
| GLM 智谱未导入 | P0 | blocked | 无 upstream key |
| asxs 生产宿主不可用 | P1 | known | remote43 出口被 Cloudflare 1010 拦截 |
| channel_pricing_intervals 空 | P2 | accepted | 不影响路由 |
| 幂等部署脚本 | P2 | planned | SQL 型步骤未封装 |
| OpenClaw CLI 版本漂移 | P3 | known | 2026.5.12 旧版, backup 已保留 |
## Phase 1 — 供应链收口
**目标**: 所有 4 个国产模型分组 (GPT/DeepSeek/MiniMax/Kimi) 经过生产宿主验收可用
1. Kimi 组启动: 确认 a7m 或备选 Kimi 上游本机 chat=200 后导入
2. Kimi 组验收: long2026 key → tksea → /v1/chat/completions 200
3. GLM 组导入: 用户提供 key 后走完供应链验收链路
4. 规范脚本化: scripts/setup_default_data.sh (幂等)
## Phase 2 — 生产运维
**目标**: 可重复部署、可监控、无已知运维缺口
1. channel_pricing_intervals 补填 (不影响路由但影响计费展示)
2. OpenClaw CLI 升级 (2026.5.12 → 最新)
3. 生产宿主健康巡检脚本
4. asxs 出口 1010 排查 (远程代理 / 白名单 / VPN)
## Phase 3 — 扩展
**目标**: 完整国产模型矩阵 (五小龙) + 生产链路可选
1. GLM 写入 OpenClaw 链路
2. Kimi 写入 OpenClaw 链路
3. asxs 写入 tksea GPT 组 (解决 1010 后)
4. 多 provider 健康切换 E2E 验证
## 最短闭环路径 (Next 3 actions)
E1 我继续问: "你要先处理 Kimi (拿到可用上游) 还是先处理 GLM (提供 key)"
E2 或者: "要不要先把 scripts/setup_default_data.sh 写完,让下次重建不再手动拼 SQL"
E3 或者: "直接选一个方向继续执行"