docs(real-host): calibrate acceptance truth surfaces

This commit is contained in:
phamnazage-jpg
2026-05-21 13:37:49 +08:00
parent 49d00e7f05
commit d077786565
6 changed files with 548 additions and 3 deletions

View File

@@ -14,6 +14,7 @@
- MiniMax 上游 `/chat/completions` = `HTTP 403 insufficient_user_quota`,因此当前验证 key 本身不具备真实 completion 流量能力。
- 汇总证据:`artifacts/real-host-acceptance/20260521_064910_completion_smoke_calibration.md`
- 调通细节与经验沉淀:`docs/REAL_HOST_ACCEPTANCE_LEARNINGS.md`
- 代码门禁与本地运行态已于 2026-05-21 再次独立复跑:`gofmt -l .``go vet ./...``go test ./... -count=1``go test -race ./... -count=1``go test -cover ./internal/... -count=1``go test ./tests/integration/... -count=1` 全通过;本机 CRM(18100) 的 `GET /healthz` / 带 token 的 `GET /api/hosts` = `200`,另起 fresh smoke 实例 `127.0.0.1:18101` 也成功返回 `GET /healthz = ok``GET /api/hosts = {"hosts":[]}`
## 本轮已完成
@@ -65,11 +66,13 @@
- `internal/provision`: `74.6%`
- `internal/store/sqlite`: `61.3%`
- `go test ./tests/integration/... -count=1`
- `bash ./scripts/test_real_host_scripts.sh`
## 本轮真实宿主复验结果
0. `ca1d448` latest-head stale-process 阻断已关闭2026-05-21
- 本地 CRM(18100) 新进程启动时间:`2026-05-21 01:08`
- 当前 18100 使用的真实 DB`/tmp/sub2api-relay-manager-realhost-18100.db`
- fresh remote43 证据目录:
- `artifacts/real-host-acceptance/20260521_011544_remote43_minimax_key_import`
- `artifacts/real-host-acceptance/20260521_011717_remote43_deepseek_key_import`
@@ -78,6 +81,8 @@
- 宿主 admin 侧直接复核:
- `GET /api/v1/admin/channels/5`MiniMax已含非空 `model_pricing``model_mapping`
- `GET /api/v1/admin/channels/4`DeepSeek已含非空 `model_pricing``model_mapping`
- 旧现象的根因时间线已确认:`artifacts/real-host-acceptance/20260520_222713_crm18100_live_model_mapping_validation/summary.json` 中 MiniMax channel 5 仍是 `model_pricing=[]`,且 `created_at=updated_at=2026-05-20T20:39:23Z`,说明它是旧 CRM 进程创建出的半成品 channel而不是 current-code rerun 后依然未纠偏
- 当前 live host 上同一 channel 5 的 `updated_at=2026-05-21T06:45:00Z`,且 `model_pricing` 已非空,证明新进程已真正执行 `UpdateChannel` 纠偏
- 结论:`ca1d448` 对 channel pricing / hosted access 的修正已在真实宿主 fresh rerun 上落地,之前“旧 CRM 进程导致 MiniMax channel 仍空 pricing”的阻断已消失
1. `self_service`(最新 fresh redeploy 复验)