fix: propagate consultation evidence before audit
Staging Backend Quality Gate / validate (push) Successful in 12m37s
Staging Backend Quality Gate / publish (push) Successful in 8m25s

This commit is contained in:
Jesse_Chen
2026-08-10 19:39:52 +08:00
parent 2697d16ef1
commit b637528f14
5 changed files with 91 additions and 13 deletions
+16
View File
@@ -2696,3 +2696,19 @@
- 相关记录:ERR-011、ERR-014、ERR-078
- 复发自:无
- 修复版本:本次同步提交
## BUG-159 | consultation 报告漏挂 Ashtakavarga/KP 且 VedAstro raw response 晚于证据包生成
- 状态:resolvedlocal candidate,待 staging gate/deployment
- 首次发现:2026-08-10
- 最近更新:2026-08-10
- 影响面:个人报告 consultation workflow、Technique Audit、VedAstro official evidence、`modules.ashtakavarga``modules.kp_cusps`
- 用户现象:Technique Audit 将 Ashtakavarga、KP cusp 和官方 VedAstro 标成 blocked;即使已配置 API key,当前报告仍提示官方外部引擎未验证或不可用。
- 触发条件:报告通过 consultation workflow 生成 machine evidence packet;本地排盘已有 planets/ascendant,或 VedAstro gateway 本次返回 official raw response。
- 根因:consultation 本地补充层只挂入 Varga、Arudha 与 Narayana,未调用仓库已有的 Ashtakavarga/KP 计算;同时 VedAstro gateway 在 machine evidence packet 冻结后才执行,导致本次 raw response 无法进入报告审计。API key 只满足凭据配置,不证明本次调用、响应与证据传播成功。
- 修复:复用现有 `_compute_ashtakavarga``_normalized_planets_from_body``_compute_kp`,把结果挂入既有 modules;将 gateway 调用提前到 evidence packet 生成前,仅在 `official_verified` 且存在本次 raw response 时合并 official evidence,缺 raw 时继续失败闭合。
- 验证:consultation consumer/API 聚焦回归锁定 Ashtakavarga SAV、12 个 KP houses、两项 audit 为 used,以及 VedAstro raw response 传播至 `official_verified`;相关聚焦测试 34 passed,开工预检通过。
- 防复发:本地计算器存在不等于已进入报告 modulesmachine evidence packet 不得在 official gateway 完成本次调用前冻结;`official_verified` 必须同时具备 closure state 与 raw response。
- 相关记录:ERR-020、ERR-021、ERR-022、ERR-024、ERR-025、ERR-026、ERR-104
- 复发自:无
- 修复版本:待提交
+6
View File
@@ -263,3 +263,9 @@ Prevention: retry fetch and `git ls-remote` before any push or release action, c
手工 Release Gate Run `1638``xiaoxin` 上通过 Docker Engine 检查后进入完整测试,但该 runner 不支持 `docker compose``--project-name``--env-file` 被 Docker 顶层 CLI 判为 unknown flag,导致 17 个 PostgreSQL、备份、身份和权限集成测试级联失败。候选 staging SHA、旧生产、Supabase 与 DNS 未被改变。
Prevention: 将该门禁运行在已验证 Docker Compose v2 的 `manman-linux`,并在安装依赖前以 `docker compose version --short` 强制 v2;不得把 `docker version` 当作 Compose 能力证明。新 SHA 必须重新完成 staging gate、公网 staging 身份和手工 Release Gate,失败 run 不得授权生产 migration、deploy 或维护停写。
## ERR-104 | Consultation evidence packet can freeze before gateway evidence and omit existing local modules | mitigated 2026-08-10
The consultation workflow built its machine evidence packet before invoking the VedAstro gateway, so a configured credential and even a successful official raw response could not affect the current report. The same workflow also failed to attach the repository's existing Ashtakavarga and KP calculators to `chart.modules`, leaving both Technique Audit rows blocked despite valid local chart inputs.
Prevention: invoke the official gateway before freezing the evidence packet; require `official_verified` plus a non-empty raw response before promoting official evidence; attach existing local calculator outputs through the shared consultation layer and keep KP values `observation_only` until an external worked-example parity gate closes. Regression tests must lock both raw-response propagation and module presence.