Files
blog/.spec/specs/2026-10-24_add-blog-infra/evidence/new-api-check.json
T
wait4xandGLM-5.3 d8f5ecfbf5 chore(spec): T1/T2 证据落库——备份三件套验证通过,翻译引擎缺口记录
- T1: pg_dump(halo_db) 237K 可恢复 + halo2 目录归档 404M/3577 项,verify_backup.sh 实跑通过
- T2: new-api 网关鉴权/模型端点可用;通用 chat 模型缺渠道(GLM 禁用、
  OpenRouter 仅特殊别名),需用户控制台启用,不阻塞 Phase 0

验证: bash .spec/specs/2026-10-24_add-blog-infra/evidence/verify_backup.sh
      (输出 backup verified: dump readable, tar entries=3577)

Co-authored-by: GLM-5.3
2026-10-24 21:58:07 +08:00

12 lines
861 B
JSON
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.
{
"gateway": "http://127.0.0.1:3000 (new-api, docker: new-api)",
"checked_at": "2026-10-24T14:05+08:00",
"result": "PARTIAL",
"ok": ["鉴权可用(Bearer sk-,token: legion/lan-share, group=default)",
"/v1/models 与 /api/status 端点正常", "sqlite 直读 tokens/channels 表正常"],
"blocked": ["chat/completions 无可用通用模型:GLM 渠道(type14) status=2 禁用中;OpenRouter 渠道仅挂 typesafe/jev-router 与 stealth/space-bunny-alpha 两个特殊用途别名(决策协议/stealth),不供普通对话",
"/v1/models 偶发 404(重试可过),疑与渠道探测缓存有关"],
"user_action": "在 new-api 控制台启用 GLM 渠道或为 default 组补一个通用对话模型渠道;完成后 Phase 3 翻译管线即可用",
"phase3_impact": "不阻塞 Phase 0;Phase 3 前置依赖已记录"
}