docs(portal): record p4-t5 remote verification
This commit is contained in:
@@ -755,6 +755,81 @@
|
||||
- 普通用户页已经开始直接告诉用户“这个逻辑分组适合什么、推荐先用哪个模型、下一步该做什么”
|
||||
- 逻辑分组产品层不再只是目录和权限展示,而是开始承接用户接入指引
|
||||
- 如果继续产品化,下一步更适合进入逻辑分组级套餐、购买/升级入口或可用性说明的更细粒度运营配置
|
||||
- 2026-05-30 已完成 Phase 4 / `P4-T5 logical group guidance config`
|
||||
- 提交:`3bfd4cfc feat(portal): add logical group guidance config`
|
||||
- 本轮后端与前端改造范围:
|
||||
- 新 migration:`internal/store/migrations/0013_logical_group_guidance.sql`
|
||||
- `logical_groups` 新增字段:
|
||||
- `usage_scenario`
|
||||
- `recommendation`
|
||||
- `next_step_hint`
|
||||
- 管理 API:
|
||||
- `POST /api/logical-groups`
|
||||
- `PUT /api/logical-groups/{group_id}`
|
||||
- `GET /api/logical-groups`
|
||||
- `GET /api/logical-groups/{group_id}`
|
||||
- 现已同时读写上述 3 个运营配置字段
|
||||
- 公网聚合 API:
|
||||
- `GET /api/portal/logical-groups`
|
||||
- `GET /api/portal/logical-groups/{group_id}`
|
||||
- 现已向普通用户侧暴露上述 3 个字段
|
||||
- 管理页:
|
||||
- `deploy/tksea-portal/admin/logical-groups.html`
|
||||
- 新增 `usage_scenario / recommendation / next_step_hint` 配置项
|
||||
- 普通用户页:
|
||||
- `deploy/tksea-portal/index.html`
|
||||
- `renderUsageGuides()` 现已优先消费逻辑分组运营配置,只有空值时才回退到 `LEGACY_MODEL_GUIDANCE`
|
||||
- 本地门禁已通过:
|
||||
- `gofmt -l .`
|
||||
- `go vet ./...`
|
||||
- `go test -cover ./internal/...`
|
||||
- `go test ./tests/integration/... -count=1`
|
||||
- `bash ./scripts/test/test_tksea_portal_assets.sh`
|
||||
- `bash ./scripts/test/test_real_host_scripts.sh`
|
||||
- remote43 已完成 CRM + Portal 升级:
|
||||
- `repo HEAD = 3bfd4cfc`
|
||||
- `GET http://127.0.0.1:18173/healthz` 返回 `ok`
|
||||
- 18173 当前活跃 CRM PID:`1651657`
|
||||
- portal 静态资源已重新发布,`nginx -t` 与 reload 成功
|
||||
- 本轮远端部署还顺手修正了一个真实问题:
|
||||
- 首次重启时按绝对路径 `pgrep` 未命中实际以 `./sub2api-cn-relay-manager-server` 运行的旧进程
|
||||
- 结果是 fixed checkout 和磁盘二进制虽然已更新,但 18173 仍由旧进程持有,表现为 `usage_scenario` 被旧 API 视为未知字段
|
||||
- 随后已改为按监听 PID 定向 kill 并重启,新字段真验恢复正常
|
||||
- remote43 / 公网真实验证已通过:
|
||||
- 管理页源码回读已确认包含:
|
||||
- `usage_scenario`
|
||||
- `recommendation`
|
||||
- `next_step_hint`
|
||||
- 普通用户页源码回读已确认包含:
|
||||
- `LEGACY_MODEL_GUIDANCE`
|
||||
- `renderUsageGuides`
|
||||
- `group.usage_scenario`
|
||||
- `group.recommendation`
|
||||
- `group.next_step_hint`
|
||||
- 远端原位临时创建样本:
|
||||
- `logical_group_id=p4t4-config-1780108991`
|
||||
- `route_id=primary-1780108991`
|
||||
- `public_model=gpt-5.4`
|
||||
- 创建结果:
|
||||
- `POST /api/logical-groups` 返回 `201`
|
||||
- 返回字段包含:
|
||||
- `usage_scenario=适合高质量推理、复杂编排和统一 GPT 产品入口。`
|
||||
- `recommendation=优先使用 gpt-5.4 作为主模型。`
|
||||
- `next_step_hint=先创建测试 Key,再按推荐模型发起第一次请求。`
|
||||
- 公网聚合回读:
|
||||
- `GET https://sub.tksea.top/portal-admin-api/api/portal/logical-groups/p4t4-config-1780108991`
|
||||
- 返回 `usage_scenario / recommendation / next_step_hint`
|
||||
- `route_count=1`
|
||||
- `active_route_count=1`
|
||||
- `GET https://sub.tksea.top/portal-admin-api/api/portal/logical-groups`
|
||||
- 列表包含 `logical_group_id=p4t4-config-1780108991`
|
||||
- 验证结束后已删除临时样本:
|
||||
- `DELETE /api/logical-groups/p4t4-config-1780108991`
|
||||
- 公网列表回读已确认该样本不再出现
|
||||
- 当前结论:
|
||||
- “逻辑分组级使用建议”已经不再是前端写死常量,而是后端可配置运营数据
|
||||
- 普通用户 Portal 现在具备了“目录 -> 权限 -> 接入建议 -> 下一步”的完整逻辑分组产品链路
|
||||
- 如果继续产品化,下一步最合适的是把这套运营配置继续扩展到套餐、购买/升级与可见性控制
|
||||
- 2026-05-28 已完成 Phase 1 / `P1-T1 SQLite schema foundation`
|
||||
- 提交:`7f75d8a6 feat(routing): add logical group schema foundation`
|
||||
- 新 migration:`internal/store/migrations/0010_logical_groups_and_routes.sql`
|
||||
|
||||
Reference in New Issue
Block a user