docs: record sync8 acceptance, BUG-1390/1391 and the ERR-110 refreeze
Independent Staging Quality Gate / validate (push) Successful in 15m2s
Independent Staging Quality Gate / publish (push) Successful in 4m10s

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HwMNZEzdzmrbPhuRNmZe3C
This commit is contained in:
Jesse_Chen
2026-10-18 18:57:02 +08:00
co-authored by Claude Opus 5.5
parent 79f6ac5297
commit 0d92f586b6
4 changed files with 51 additions and 1 deletions
+2
View File
@@ -453,6 +453,8 @@ Prevention: 引擎/打分路径的性能任务书开工前先查这两份清单
2026-10-14:校正打分提速(BUG-1323~1325、BUG-1345)改了 `event_probes.py`、`dasha_transition_proximity.py`、`active_rectification_event_engine.py`、`api_service.py`。与 `ephemeris_nutation_2026_10_08` 对照输出不变后,另存标签 `scoring_perf_2026_10_13`。nutation 那四份文件没有改。
2026-10-18:上游同步第八轮(BUG-1380~1390)改了 `ashtakavarga.py`、`dasha_analyzer.py`、`narayana_dasha.py`,三者都在 dataset `frozen_scoring.files` 里。任务书没预见到,写了「不得自行重新冻结」,执行方照做停下,冻结身份测试 8 条红。执行方与验收方各自重跑,封存 20 / 偏移 900 逐项相同,产品同意后另存标签 `upstream_sync8_2026_10_18`。教训:动引擎计算的任务书开工前就要对照两份清单,把「输出不变则按 ERR-110 重冻」写进任务分解,而不是笼统禁止。
## ERR-111 | Shadbala 特征指纹随 PYTHONHASHSEED 变化,同一输入跨进程 `feature_hash` 不同 | observed 2026-09-26
同一台机器、同一份代码、同一虚构请求连跑两次 `score_candidates`:`candidate_feature_snapshot.features[*].fingerprints.shadbala` / `static` 与 `feature_hash` 每次都不同;固定 `PYTHONHASHSEED=0` 后两次逐字节一致。说明 Shadbala 结果里有依赖集合 / 哈希顺序的结构进入了指纹。打分分数本身未见变化(未系统核对)。